Jim,
Thanks for the great trouble shooting tips! It was a firewall issue! The
telnet test showed the problem.
Still getting use to CentOS 7, it uses firewalld instead of/with, (not
sure which), iptables. Did a little googling and found this at bacula.us:
1. firewall-cmd --permanent --zone=p
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?
Hi,
On Tue, May 2, 2017 at 8:29 PM, Tom Plancon wrote:
> 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!
>
If you don't want to use the RHEL/CentOS provided packages pleas
The sd resolv the client name ? (/etc/hosts or dns)
J.
2017-05-02 20:29 GMT+02:00 Tom Plancon :
> 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 1
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 B