Tom try the following
Can the console connect to the client?
# bconsole
status
3 for client
your client number
Does gannet
resolve on the client?
The bacula-dir.conf storage resource address must resolve to the same IP that your bacula-sd
daemon is bound to.
Has the FD bound to the 9102 port?
netstat -na | grep 9102 && netstat -na | grep bacula-fd
You will see something like 0.0.0.0:9102 or 0.0.0.0:bacula-fd
Do you have a firewall issue?
iptables -L
iptables -L | grep 9102 && iptables -L | grep bacula-fd
cat /etc/bacula/bacula-sd
I am only interested in the top “Storage” section specifically if you have and Address value. If you don’t Bacula will bind to 0.0.0.0 if you do it will bind to that address only
Can you telnet from the client to the IP/Port of the fd?
Can you do it by name telnet
gannet 9102 ?
Let me know how that works out.
From: Tom Plancon [mailto:tplancon AT bkaarchs DOT com]
Sent: Tuesday, May 2, 2017 1:29 PM
To: bacula-users AT lists.sourceforge DOT net
Subject: [Bacula-users] SD cannot connect to FD
Hello All,
I'm getting the following error when trying to back up a remote client:
01-May 17:59 pequod-fd JobId 53: Fatal error: Failed to connect to Storage daemon: gannet:9103
01-May 17:59 bacula-dir JobId 53: Fatal error: Bad response to Storage command: wanted 2000 OK storage
, got 2902 Bad storage
I have Bacula director and storage 7.0.5 installed on a CentOS 7 machine from yum. I am able to connect to the sd from bconsole, check status and label volumes successfully I'm able to connect to the fd on a CentOS 6.8 machine from bconsole and get the status
etc. However trying to run a backup on the 6.8 machine gives the above error after about 30min.
Initially the client on the 6.8 machine was bacula 5.0 so I thought that was the issue. I built a 7.0.5 client from source on the 6.8 machine but still the same error!
Any suggestions greatly appreciated! Thanks!