Hello,
I recently installed BareOS 18.2.5 on a single CentOS 7 machine (DIR + SD) and 
installed droplet plugin to send data to AWS S3.
The configuration looks fine as bconsole tells me storage status is ok:

Device status:

Device "AWS_S3_Object_Storage" (AWS S3 Storage) is not open.
Backend connection is working.
Inflight chunks: 0
No pending IO flush requests.
==
====


However, when launching a FULL backup job, after 15 minutes it fails with the 
following error:

27-Mar 11:03 rabbit-1-fd JobId 3: Error: lib/bsock_tcp.cc:417 Wrote 9611 bytes 
to Storage daemon:172.17.0.60:9103, but only 0 accepted.
27-Mar 11:03 rabbit-1-fd JobId 3: Fatal error: filed/backup.cc:1033 Network 
send error to SD. ERR=Connection timed out
27-Mar 11:03 backup-1 JobId 3: Fatal error: Director's comm line to SD dropped.
27-Mar 11:03 backup-1 JobId 3: Error: Bareos backup-1 18.2.5 (30Jan19):
  Build OS: Linux-4.4.92-6.18-default redhat CentOS Linux release 7.6.1810 
(Core)
  JobId: 3
  Job: backup-rabbit-1.2019-03-27_10.34.06_14
  Backup Level: Full
  Client: "rabbit-1-fd" 18.2.5 (30Jan19) 
Linux-4.4.92-6.18-default,redhat,CentOS Linux release 7.6.1810 (Core) 
,CentOS_7,x86_64
  FileSet: "RabbitMQFileSet" 2019-03-27 09:42:15
  Pool: "Full" (From command line)
  Catalog: "MyCatalog" (From Client resource)
  Storage: "S3_Object" (From Job resource)
  Scheduled time: 27-Mar-2019 10:34:06
  Start time: 27-Mar-2019 10:48:17
  End time: 27-Mar-2019 11:03:51
  Elapsed time: 15 mins 34 secs
  Priority: 10
  FD Files Written: 24
  SD Files Written: 0
  FD Bytes Written: 95,320 (95.32 KB)
  SD Bytes Written: 691 (691 B)
  Rate: 0.1 KB/s
  Software Compression: 24.3 % (lz4)
  VSS: no
  Encryption: no
  Accurate: no
  Volume name(s):
  Volume Session Id: 2
  Volume Session Time: 1553682684
  Last Volume Bytes: 0 (0 B)
  Non-fatal FD errors: 1
  SD Errors: 0
  FD termination status: Fatal Error
  SD termination status: Error
  Bareos binary info: bareos.org build: Get official binaries and vendor 
support on bareos.com
  Termination: *** Backup Error ***


The connection between FD on backup client and BareOS server looks fine, I can 
telnet ports 9101 and 9103 to DIR and SD correctly.


Steps To Reproduce      Install bareos stack 18.2.5 and try to perform a FULL 
backup job, sending data to S3


Additional Information  DIR config:

Client {
  Name = rabbit-1-fd
  Address = 172.17.0.170
  Password = ****
  Heartbeat Interval = 60
  File Retention = 30 days
  Job Retention = 6 months
  AutoPrune = yes
}

Job {
  Name = "backup-rabbit-1"
  Client = rabbit-1-fd
  JobDefs = "RabbitMQJobDef"
}

JobDefs {
  Name = "RabbitMQJobDef"
  Type = Backup
  Level = Incremental

  Client = bareos-fd

  FileSet = "RabbitMQFileSet"
  Schedule = "RabbitMQCycle"
  Storage = S3_Object

  Messages = Standard

  Pool = Incremental

  Priority = 10
  Write Bootstrap = "/var/lib/bareos/%c.bsr"

  Full Backup Pool = Full
  Differential Backup Pool = Differential
  Incremental Backup Pool = Incremental
}

Storage {
  Name = S3_Object
  Address = 172.17.0.60
  Password = ****
  Device = AWS_S3_Object_Storage
  Media Type = S3_Object1
  Heartbeat Interval = 60
}

SD config:

Device {
  Name = "AWS_S3_Object_Storage"
  Media Type = "S3_Object1"
  Archive Device = "AWS S3 Storage"
  Device Type = droplet
  Device Options = 
"profile=/etc/bareos/bareos-sd.d/device/droplet/aws.droplet.profile,bucket=bucket,location=eu-central-1,chunksize=100M,iothreads=10,retries=0"
  LabelMedia = yes
  Random Access = yes
  AutomaticMount = yes
  RemovableMedia = no
  AlwaysOpen = no
  Maximum Concurrent Jobs = 10
  Maximum File Size = 500M
  Maximum Spool Size = 15000M
}

use_https = true
host = s3.eu-central-1.amazonaws.com
access_key = <access_key>
secret_key = <secret_key>
pricing_dir = ""
backend = s3
aws_region = eu-central-1
aws_auth_sign_version = 4


A part from the configuration snippets, I can also attach a trace took from one 
job I run a while ago. I copy-pasted this issue from BareOS bug tracker where, 
unfortunately, I couldn't get help.
Thank you,
Stefano

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Attachment: backup-1.trace
Description: Binary data

Reply via email to