I could see plenty of Bacula traffic on port 9102 using tcpdump. Same for port 9103 on the backup server. The eventual death of the backup job must be blamed on the client's problems. (Fedora Core 3, old server hardware -- hard to say which is to blame without further testing)
So, thanks anyway.
Jason Byrns wrote:
Can anyone help me troubleshoot a single client that won't back up?
Here's what the errors look like:
28-Apr 12:05 backups-dir: Intranet_Server.2005-04-28_11.52.58 Fatal error: Network error with FD during Backup: ERR=Connection reset by peer
28-Apr 12:05 backups-dir: Intranet_Server.2005-04-28_11.52.58 Fatal error: No Job status returned from FD.
28-Apr 12:05 backups-dir: Intranet_Server.2005-04-28_11.52.58 Error: Bacula 1.36.3 (22Apr05): 28-Apr-2005 12:05:31
-- Jason Byrns Production Manager System Administrator http://www.MicroLnk.com/ 402-328-8600 ext. 653
------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
