job is waiting for Client to connect to Storage-sd error

8 views
Skip to first unread message

Study It

unread,
Oct 2, 2024, 8:15:39 AMOct 2
to bacularis
Hello community

I had struggled for the past 2 days with this annoying issue. I added a new client to the Bacularis Server, and mirrored the configuration as the other Windows machines already configured on the server.

Installed the bacula client on the target machine, enabled 9101-9103 ports on the firewall, configured the bacula-fd.conf on ther client to match the server and checked the client status from Bacularis Server. All seemed just fine.

Cloned the existing jobs full+incremental that are running just fine on the other existing machines and waited for the schedule to launch and finish the jobs.Jobs were launched, but never finished.

The error i receive is job myfulljob is waiting for Client  to connect to Storage-sd.

What i did: 

restarted all services 
 checked the bacula.dir with bacula-dir -t c- bacula-dir.conf and the other conf. files. ALL OK
checked telnet connectivity from the server to the client on port 9103, ok

firewall rule is ok, according to the network engineer.

So, what i am doing wrong here?

Marcin Haba

unread,
Oct 2, 2024, 8:32:13 AMOct 2
to Study It, bacularis
Hello Study It,

It looks like a problem in communication between:

Client => Storage

It is good that you checked the communication to the client. What I
would advise to check else is the communication from FD to SD.

To do that please look at the Storage resource in the Director
configuration. I mean this Storage resource that is used in running
job. Then please take the Address directive value from this Storage
resource and then run on the Bacula Client host:

telnet THIS_STORAGE_ADDRESS 9103

This way we will see if this Client sees this SD.

Please let us know about this test result.

Good luck.

Best regards,
Marcin Haba (gani)

Study It

unread,
Oct 3, 2024, 4:46:45 AMOct 3
to bacularis
Hello

Things is, that sometimes the most overlooked detail is the one giving you the most headache. 
The host has 3 NICs, each one with a different subnet and gateway, and the traffic was routed so that the host never reached the Bacula server from the IP declared on the FD.
Added a route rule and now the traffic is flowing acordingly and the backup task is running.

Thanks

Marcin Haba

unread,
Oct 3, 2024, 5:09:24 AMOct 3
to Study It, bacularis
On Thu, 3 Oct 2024 at 10:46, Study It <study.i...@gmail.com> wrote:
>
> Hello
>
> Things is, that sometimes the most overlooked detail is the one giving you the most headache.
> The host has 3 NICs, each one with a different subnet and gateway, and the traffic was routed so that the host never reached the Bacula server from the IP declared on the FD.
> Added a route rule and now the traffic is flowing acordingly and the backup task is running.
>
> Thanks

Hello Study It,

Super! Thanks for sharing with us this solution.
Reply all
Reply to author
Forward
0 new messages