View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001241bareos-corestorage daemonpublic2020-05-14 13:402023-12-13 15:31
Reporteranuroop989 Assigned Tobruno-at-bareos  
PriorityimmediateSeveritymajorReproducibilityalways
Status closedResolutionduplicate 
PlatformLinuxOSCentOSOS Version7
Product Version18.2.5 
Summary0001241: backup failed :: bareos-sd: ERROR in backends/droplet_device.cc:109 error: src/conn.c:316: do_connect: Timed out connection
DescriptionHello,
I recently installed BareOS server and client and the droplet plugin to send data to AWS S3. Tested the backup to S3 with Selftest as the Fileset and it works without any issue.
But when trying a full backup with fileset "LINUXALL" the backup fails with below error.

"backends/droplet_device.cc:109 error: src/httpreply.c:382: dpl_read_http_reply_buffered: Timed out waiting to read from server mc-bareos-test.s3.amazonaws.com:80"

Note : Full backup with fileset called SelfTest works fine

Following is my error.
-------------------------------------------------
14-May 13:58 bareos-sd JobId 43: Volume "Full-0022" previously written, moving to end of data.
14-May 13:58 bareos-sd JobId 43: Error: Unable to position to end of data on device "AWS_S3_1-00" (AWS S3 Storage): ERR=stored/dev.cc:850 lseek error on "AWS_S3_1-00" (AWS S3 Storage). ERR=Success.
14-May 13:58 bareos-sd JobId 43: Marking Volume "Full-0022" in Error in Catalog.
14-May 13:58 bareos-dir JobId 43: Created new Volume "Full-0023" in catalog.
14-May 13:58 bareos-sd JobId 43: Labeled new Volume "Full-0023" on device "AWS_S3_1-00" (AWS S3 Storage).
14-May 13:58 bareos-sd JobId 43: Wrote label to prelabeled Volume "Full-0023" on device "AWS_S3_1-00" (AWS S3 Storage)
14-May 14:01 bareos-sd: ERROR in backends/droplet_device.cc:109 error: src/conn.c:316: do_connect: Timed out connecting to server 52.219.47.153:80 after 5 seconds
14-May 14:03 anuroop-prakash-fd JobId 43: Disallowed filesystem. Will not descend from / into /dev
14-May 14:03 anuroop-prakash-fd JobId 43: Disallowed filesystem. Will not descend from / into /run
14-May 14:03 anuroop-prakash-fd JobId 43: Disallowed filesystem. Will not descend from / into /sys
14-May 14:06 bareos-sd: ERROR in backends/droplet_device.cc:109 error: src/conn.c:316: do_connect: Timed out connecting to server 52.219.47.85:80 after 5 seconds
14-May 14:11 bareos-sd: ERROR in backends/droplet_device.cc:109 error: src/httpreply.c:382: dpl_read_http_reply_buffered: Timed out waiting to read from server mc-bareos-test.s3.amazonaws.com:80
14-May 14:12 bareos-sd JobId 43: Error: stored/block.cc:771 Write error at 0:419392685 on device "AWS_S3_1-00" (AWS S3 Storage). ERR=Input/output error.
14-May 14:12 bareos-sd JobId 43: Error: stored/block.cc:785 Write error on fd=0 at file:blk 0:419392685 on device "AWS_S3_1-00" (AWS S3 Storage). ERR=Input/output error.
14-May 14:12 bareos-sd JobId 43: End of medium on Volume "Full-0023" Bytes=419,392,686 Blocks=6,501 at 14-May-2020 14:12.
14-May 14:12 bareos-dir JobId 43: Created new Volume "Full-0024" in catalog.
14-May 14:12 bareos-sd JobId 43: Labeled new Volume "Full-0024" on device "AWS_S3_1-00" (AWS S3 Storage).
14-May 14:12 bareos-sd JobId 43: Wrote label to prelabeled Volume "Full-0024" on device "AWS_S3_1-00" (AWS S3 Storage)
14-May 14:12 bareos-sd JobId 43: New volume "Full-0024" mounted on device "AWS_S3_1-00" (AWS S3 Storage) at 14-May-2020 14:12.
14-May 14:12 bareos-sd: ERROR in backends/droplet_device.cc:109 error: src/conn.c:316: do_connect: Timed out connecting to server 52.219.72.242:80 after 5 seconds
14-May 14:27 anuroop-prakash-fd JobId 43: Disallowed filesystem. Will not descend from / into /var/lib/nfs/rpc_pipefs
14-May 14:42 bareos-sd: ERROR in backends/droplet_device.cc:109 error: src/httpreply.c:382: dpl_read_http_reply_buffered: Timed out waiting to read from server mc-bareos-test.s3.amazonaws.com:80
14-May 14:42 bareos-sd JobId 43: Error: stored/block.cc:771 Write error at 0:419392652 on device "AWS_S3_1-00" (AWS S3 Storage). ERR=Input/output error.
14-May 14:42 bareos-sd JobId 43: Error: stored/block.cc:785 Write error on fd=0 at file:blk 0:419392652 on device "AWS_S3_1-00" (AWS S3 Storage). ERR=Input/output error.
14-May 14:42 bareos-sd JobId 43: End of medium on Volume "Full-0024" Bytes=419,392,653 Blocks=6,501 at 14-May-2020 14:42.
14-May 14:42 bareos-dir JobId 43: Created new Volume "Full-0025" in catalog.
14-May 14:42 bareos-sd JobId 43: Labeled new Volume "Full-0025" on device "AWS_S3_1-00" (AWS S3 Storage).
14-May 14:42 bareos-sd JobId 43: Wrote label to prelabeled Volume "Full-0025" on device "AWS_S3_1-00" (AWS S3 Storage)
14-May 14:42 bareos-sd JobId 43: New volume "Full-0025" mounted on device "AWS_S3_1-00" (AWS S3 Storage) at 14-May-2020 14:42.
14-May 15:15 bareos-sd: ERROR in backends/droplet_device.cc:109 error: src/httpreply.c:382: dpl_read_http_reply_buffered: Timed out waiting to read from server mc-bareos-test.s3.amazonaws.com:80
14-May 15:15 bareos-sd JobId 43: Error: stored/block.cc:771 Write error at 0:419392709 on device "AWS_S3_1-00" (AWS S3 Storage). ERR=Input/output error.
14-May 15:15 bareos-sd JobId 43: Error: stored/block.cc:785 Write error on fd=0 at file:blk 0:419392709 on device "AWS_S3_1-00" (AWS S3 Storage). ERR=Input/output error.
14-May 15:15 bareos-sd JobId 43: End of medium on Volume "Full-0025" Bytes=419,392,710 Blocks=6,501 at 14-May-2020 15:15.
14-May 15:15 bareos-dir JobId 43: Created new Volume "Full-0026" in catalog.
14-May 15:15 bareos-sd JobId 43: Labeled new Volume "Full-0026" on device "AWS_S3_1-00" (AWS S3 Storage).
14-May 15:15 bareos-sd JobId 43: Wrote label to prelabeled Volume "Full-0026" on device "AWS_S3_1-00" (AWS S3 Storage)
14-May 15:15 bareos-sd JobId 43: New volume "Full-0026" mounted on device "AWS_S3_1-00" (AWS S3 Storage) at 14-May-2020 15:15.
-------------------------------------------------


Is there anything to do more on config to get rid of this issue. Could anyone please look into it and suggest
Additional InformationMain configurations
---------------------------------
Device {
  Name = "AWS_S3_1-00"
  Media Type = "S3_Object1"
  Archive Device = "AWS S3 Storage"
  Device Type = droplet
  Device Options = "profile=/etc/bareos/bareos-sd.d/device/droplet/aws.profile,bucket=mc-bareos-test,chunksize=100M,iothreads=0,retries=0"
  Label Media = yes
  Random Access = yes
  Automatic Mount = yes
  Removable Media = no
  Always Open = no
  Description = "S3 device"
  Maximum Concurrent Jobs = 1

-------------------------------------------------
host = s3.amazonaws.com:443
use_https = true
backend = s3
aws_region = eu-central-1
aws_auth_sign_version = 4
pricing_dir = ""

-------------------------------------------------

FileSet {
  Name = "LinuxAll"
  Description = "Backup all regular filesystems, determined by filesystem type."
  Include {
    Options {
      Signature = MD5 # calculate md5 checksum per file
      One FS = No # change into other filessytems
      FS Type = btrfs
      FS Type = ext2 # filesystems of given types will be backed up
      FS Type = ext3 # others will be ignored
      FS Type = ext4
      FS Type = reiserfs
      FS Type = jfs
      FS Type = xfs
      FS Type = zfs
    }
    File = /
  }
  # Things that usually have to be excluded
  # You have to exclude /var/lib/bareos/storage
  # on your bareos server
  Exclude {
    File = /var/lib/bareos
    File = /var/lib/bareos/storage
    File = /proc
    File = /tmp
    File = /var/tmp
    File = /.journal
    File = /.fsck
  }
}
-------------------------------------------------
Tags"libdroplet"

Relationships

duplicate of 0001553 closedarogge S3 (droplet) returns an error on Exoscale S3 service 
has duplicate 0001242 closedbruno-at-bareos backup to s3 error :: bareos-sd: ERROR in backends/droplet_device.cc:109 error: src/conn.c:316: do_connect: Timed out connecting 

Activities

bruno-at-bareos

bruno-at-bareos

2023-12-13 15:31

manager   ~0005635

consolidating droplet issues

Issue History

Date Modified Username Field Change
2020-05-14 13:40 anuroop989 New Issue
2023-12-12 17:25 bruno-at-bareos Tag Attached: "libdroplet"
2023-12-12 17:26 bruno-at-bareos Relationship added related to 0001242
2023-12-12 17:27 bruno-at-bareos Relationship replaced has duplicate 0001242
2023-12-13 15:31 bruno-at-bareos Assigned To => bruno-at-bareos
2023-12-13 15:31 bruno-at-bareos Status new => closed
2023-12-13 15:31 bruno-at-bareos Resolution open => duplicate
2023-12-13 15:31 bruno-at-bareos Note Added: 0005635
2023-12-13 15:31 bruno-at-bareos Relationship added duplicate of 0001553