Hello,

I have problem with a client initiated backup job, where the client can connect 
to the Director, but seemingly cannot connect to the storage deamon on the same 
machine. 

We use bareos 16.2.4. The dir/sd server is in a DMZ with most clients, working 
just fine, but some are outside. Those outside have a working connection to the 
director, I can view their status from bconsole for example. But everytime I 
run a backup, it fails:

####
22-May 18:49 mybareosserver-dir JobId 16338: No prior Full backup Job record 
found.
22-May 18:49 mybareosserver-dir JobId 16338: No prior or suitable Full backup 
found in catalog. Doing FULL backup.
22-May 18:49 mybareosserver-dir JobId 16338: Start Backup JobId 16338, 
Job=myclient-job.2018-05-22_18.49.33_04
22-May 18:49 mybareosserver-dir JobId 16338: Using Device "FileStorage" to 
write.
22-May 18:49 mybareosserver-dir JobId 16338: Using Client Initiated Connection 
(myclient).
22-May 18:49 grzostkbkp01-sd JobId 16338: Volume "Bkup0119" previously written, 
moving to end of data.
22-May 18:49 grzostkbkp01-sd JobId 16338: Warning: For Volume "Bkup0119":
The sizes do not match! Volume=9460554318 Catalog=9460489806
Correcting Catalog
*m
22-May 19:05 myclient JobId 16338: Error: bsock_tcp.c:405 Write error sending 
65536 bytes to Storage daemon:mybareosserver.mynetwork:9103: ERR=Connection 
timed out
22-May 19:05 myclient JobId 16338: Fatal error: backup.c:1019 Network send 
error to SD. ERR=Connection timed out
22-May 19:05 mybareosserver-dir JobId 16338: Error: Director's comm line to SD 
dropped.
22-May 19:05 mybareosserver-dir JobId 16338: Error: Bareos mybareosserver-dir 
16.2.4 (01Jul16):
  Build OS:               x86_64-redhat-linux-gnu redhat Red Hat Enterprise 
Linux Server release 6.5 (Santiago)
  JobId:                  16338
  Job:                    myclient-job.2018-05-22_18.49.33_04
  Backup Level:           Full (upgraded from Incremental)
  Client:                 "myclient" 16.2.4 (01Jul16) 
x86_64-redhat-linux-gnu,redhat,CentOS release 6.6 (Final),CentOS_6,x86_64
  FileSet:                "LinuxAll" 2018-05-17 21:00:01
  Pool:                   "File" (From Job resource)
  Catalog:                "MyCatalog" (From Client resource)
  Storage:                "File" (From Job resource)
  Scheduled time:         22-May-2018 18:49:31
  Start time:             22-May-2018 18:49:35
  End time:               22-May-2018 19:05:01
  Elapsed time:           15 mins 26 secs
  Priority:               10
  FD Files Written:       13
  SD Files Written:       0
  FD Bytes Written:       178,554 (178.5 KB)
  SD Bytes Written:       1,212 (1.212 KB)
  Rate:                   0.2 KB/s
  Software Compression:   26.8 %
  VSS:                    no
  Encryption:             no
  Accurate:               yes
  Volume name(s):         
  Volume Session Id:      1
  Volume Session Time:    1527007642
  Last Volume Bytes:      0 (0 B)
  Non-fatal FD errors:    2
  SD Errors:              0
  FD termination status:  Fatal Error
  SD termination status:  Error
  Termination:            *** Backup Error ***

22-May 19:05 mybareosserver-dir JobId 16338: Rescheduled Job 
myclient-job.2018-05-22_18.49.33_04 at 22-May-2018 19:05 to re-run in 1800 
seconds (22-May-2018 19:35).
22-May 19:05 mybareosserver-dir JobId 16339: Job 
myclient-job.2018-05-22_19.05.01_06 waiting 1800 seconds for scheduled start 
time.
/####

The volume sizes do not match because of the prior failed job with the same 
client.
The client log shows this:

####
22-May 19:05 myclient JobId 16338: Error: bsock_tcp.c:405 Write error sending 
65536 bytes to Storage daemon:mybareosserver.mynetwork:9103: ERR=Connection 
timed out
22-May 19:05 myclient JobId 16338: Fatal error: backup.c:1019 Network send 
error to SD. ERR=Connection timed out
22-May 19:05 myclient JobId 16338: Error: bsock_tcp.c:434 Socket has errors=1 
on call to Storage daemon:mybareosserver.mynetwork:9103
/####

I was very careful not to use localhost or 127.0.0.1 anywhere in the 
configfiles.
Also, to make matters more confusing, I have another client in another network 
with the completely same configuration copied over (only client name, address 
and job name changed), which is working fine. Both can access the server over 
ports 9101 and 9103 (also 9102 but that shouldn't matter), but the server 
cannot access either of the clients because of the DMZ. So since they have an 
identical configuration and the same open network ports, I don't know why one 
is working and the other one is not. Does anybody have any Ideas?

Regards,
Jacob

-- 
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.

Reply via email to