<JOB> is waiting for Client <CLIENT> to connect to Storage <STORAGE>
Stefan Müller
I need help. Last week we ported our working bacula 5.2 installation to a bareos 13.2.2 one.
Here we've followed the manual http://www.bareos.org/en/HOWTO/articles/upgrade_bacula_bareos.html without any problem.
I've rewritten the configs, removed the PID dir and included some new features like LZ4 compression. But mainly they are the same configs as under bacula.
Now to my problem. All linux clients working fine but my two windows clients won't start a backup.
If I start a job via `bconsole` then for about 20 minutes the job "stand still". The command `status dir` show something like this:
*status dir
linux01-dir Version: 13.2.2 (12 November 2013) x86_64-pc-linux-gnu debian Debian GNU/Linux 7.0 (wheezy)
Daemon started 24-Aug-14 10:20. Jobs: run=3, running=1 mode=0
Heap: heap=507,904 smbytes=222,694 max_bytes=223,066 bufs=913 max_bufs=935
No Scheduled Jobs.
====
Running Jobs:
Console connected at 24-Aug-14 10:50
JobId Level Name Status
======================================================================
1516 Full Windows_Server_Backup_server02.2014-08-24_10.50.14_10 is waiting for Client server02-fd to connect to Storage c0
====
Terminated Jobs:
JobId Level Files Bytes Status Finished Name
====================================================================
1514 Full 0 0 Cancel 24-Aug-14 08:20 Windows_Server_Backup_server02
1515 Full 0 0 Cancel 24-Aug-14 08:21 Windows_Server_Backup_server-0
The job fails then, after 30 minutes, with that description:
24-Aug 10:50 linux01-dir JobId 1516: Start Backup JobId 1516, Job=Windows_Server_Backup_server02.2014-08-24_10.50.14_10
24-Aug 10:50 linux01-dir JobId 1516: Using Device "usb-changer-drive-0" to write.
24-Aug 10:50 linux01-fd JobId 1516: Created 28 wildcard excludes from FilesNotToBackup Registry key
24-Aug 10:50 linux01-fd JobId 1516: Warning: lib/bsock_tcp.c:170 Could not connect to Storage daemon on linux01.gaswarnanlagen.lan:9103. ERR=Der Vorgang wurde erfolgreich beendet.
Retrying ...
24-Aug 10:56 linux01-fd JobId 1516: Warning: lib/bsock_tcp.c:170 Could not connect to Storage daemon on linux01.gaswarnanlagen.lan:9103. ERR=Der Vorgang wurde erfolgreich beendet.
Retrying ...
24-Aug 11:01 linux01-fd JobId 1516: Warning: lib/bsock_tcp.c:170 Could not connect to Storage daemon on linux01.gaswarnanlagen.lan:9103. ERR=Der Vorgang wurde erfolgreich beendet.
Retrying ...
24-Aug 11:07 linux01-fd JobId 1516: Warning: lib/bsock_tcp.c:170 Could not connect to Storage daemon on linux01.gaswarnanlagen.lan:9103. ERR=Der Vorgang wurde erfolgreich beendet.
Retrying ...
24-Aug 11:13 linux01-fd JobId 1516: Warning: lib/bsock_tcp.c:170 Could not connect to Storage daemon on linux01.gaswarnanlagen.lan:9103. ERR=Der Vorgang wurde erfolgreich beendet.
Retrying ...
24-Aug 11:18 linux01-fd JobId 1516: Warning: lib/bsock_tcp.c:170 Could not connect to Storage daemon on linux01.gaswarnanlagen.lan:9103. ERR=Der Vorgang wurde erfolgreich beendet.
Retrying ...
24-Aug 11:20 linux01-fd JobId 1516: Fatal error: lib/bsock_tcp.c:176 Unable to connect to Storage daemon on linux01.gaswarnanlagen.lan:9103. ERR=Der Vorgang wurde erfolgreich beendet.
24-Aug 11:20 linux01-fd JobId 1516: Fatal error: Failed to connect to Storage daemon: linux01.gaswarnanlagen.lan:9103
24-Aug 11:20 linux01-dir JobId 1516: Fatal error: Bad response to Storage command: wanted 2000 OK storage
, got 2902 Bad storage
24-Aug 11:20 linux01-dir JobId 1516: Error: Bareos linux01-dir 13.2.2 (12Nov13):
Build OS: x86_64-pc-linux-gnu debian Debian GNU/Linux 7.0 (wheezy)
JobId: 1516
Job: Windows_Server_Backup_server02.2014-08-24_10.50.14_10
Backup Level: Full
Client: "server02-fd" 14.3.0 (24Jul14) Microsoft Windows 7 Professional Service Pack 1 (build 7601), 64-bit,Cross-compile,Win64
FileSet: "Windows Server" 2014-02-02 11:05:00
Pool: "default" (From Job resource)
Catalog: "MyCatalog" (From Client resource)
Storage: "c0" (From Pool resource)
Scheduled time: 24-Aug-2014 10:50:14
Start time: 24-Aug-2014 10:50:16
End time: 24-Aug-2014 11:20:25
Elapsed time: 30 mins 9 secs
Priority: 10
FD Files Written: 0
SD Files Written: 0
FD Bytes Written: 0 (0 B)
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s
Software Compression: None
VSS: no
Encryption: no
Accurate: no
Volume name(s):
Volume Session Id: 4
Volume Session Time: 1408868461
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 2
SD Errors: 0
FD termination status: Error
SD termination status: Waiting on FD
Termination: *** Backup Error ***
What I've done so far:
- check IP and DNS configuration -> all fine, it's the same it was with bacula
- check passwords and names -> all fine
- check TCP/IP ports with telnet -> all fine and open
Does anybody see here a solution?
c mu
Hi,
sometimes, when I changed a password or client IP, I get a similar message. I restart the director deamon to solve this.
Philipp Storz
you could also try out "passive mode" for the clients in question.
Whatever your problem is, it at least reverses the setup of the connection between sd and fd:
See here how that can be configured:
http://www.bareos.org/en/HOWTO/articles/new-in-version-1320.html
"Reverse data channel initialization aka passive clients"
Mit freundlichen Grüßen
Philipp Storz philip...@bareos.com
Bareos GmbH & Co. KG Phone: Phone: +49221630693-92
http://www.bareos.com Fax: +49221630693-10
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Geschäftsführer: Stephan Dühr, M. Außendorf,
J. Steffens, P. Storz, M. v. Wieringen
Bruno Friedmann
>
> What I've done so far:
> - check IP and DNS configuration -> all fine, it's the same it was with bacula
> - check passwords and names -> all fine
> - check TCP/IP ports with telnet -> all fine and open
>
> Does anybody see here a solution?
>
>
When a job is running check which real ip the windows server want to connect by using netstat on windows.
If you linux & your windows are both recent, perhaps you have ipv6 enable.
Bareos or Bacula work well on ipv6 only or ipv4 only but not on both.
The worse scenario I've seen is director resolving ipv4 client, then prepare sd to receive a connection for this one.
but client resolve storage as ipv6 and try to goes there ... sd doing nothing
To avoid this kind of trouble (since I've still not yet correctly reported the bug and all aspect of it)
I choose to use bareos on either only ipv4 or only ipv6
in dir,sd,client conf
uncomment the protocol you want to use
*Addresses = {
# ipv6 = { addr = :: ; port = 9102 }
# ipv4 = { addr = 0.0.0.0 ; port = 9102}
}
For sure whatever you choose, you have to have correct ip/names resolution which can be tricky with ipv6
(due to auto-configuration, temp_addr etc )
--
Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch
------------------------
/ openSUSE Member & Board \
/ GPG KEY : D5C9B751C4653227 \
\ irc: tigerfoot /
\ /
------------------------
\
/@ --~-.
\/ __ .- |
// // @
zzeroo
> you could also try out "passive mode" for the clients in question.
>
Thank you Philipp,
with "Passive = yes" the job runs fine. I think the problem occurred because of the IPv4 / IPv6 configuration of my linux/ windows hosts. I'll investigate this more deeply even with Bruno's hint in mind.
Thanks to all for the quick reply.