Bacula backup failed: ERR=Connection timed out



Infrastructure & Operations
MOC: Problems
3 years ago
3 years ago


(Reporter: w0ts0n, Assigned: w0ts0n)





3 years ago
We got the error to the MOC this morning:
2015-04-22 JobId 6860: Warning: bsock.c:222 Could not connect to Client: on ERR=Connection timed out
Retrying ...

:sheeri, did anyone change any firewall configs?
rwatson@w0ts0n:~$  nc -w1 -vz 9102
nc: connectx to port 9102 (tcp) failed: Operation timed out

I logged into the box, restarted the Bacula service, same issue. 

I then opened the port inbound/outbound on the local firewall and restarted the service:
rwatson@w0ts0n:~$  nc -w1 -vz 9102
found 0 associations
found 1 connections:
     1:	flags=82<CONNECTED,PREFERRED>
	outif tun0
	src port 58155
	dst port 9102
	rank info not available
	TCP aux info available

Connection to port 9102 [tcp/bacula-fd] succeeded!

Just waiting on rtucker to confirm it's working.


3 years ago
Assignee: nobody → rwatson

Comment 1

3 years ago
Just to clarify. I added an inbound/outbound rule using the title "Bacula" on the local Windows firewall to allow port 9102.

Comment 2

3 years ago
Confirmed backup has completed.

Comment 3

3 years ago
Well, Sheeri was unaware that backups were being done. Well now she knows, so it's win-win
Last Resolved: 3 years ago
Resolution: --- → FIXED
That's actually good news, because we are backing up Tableau to C:\tableau-backups, so bacula gives us an off-machine copy.
Do you want to cease backing up to C:\tableau-backups or should I exclude that directory from being backed up?
Flags: needinfo?(scabral)
It would be great to keep it backed up, that way we have an off-site copy.
Flags: needinfo?(scabral)
You need to log in before you can comment on or make changes to this bug.