Hi,
Just upgraded from 1.36.1 to 1.38.11 (last binaries a could found for our old
RedHat 8.0 box), now I am fighting with this dreadful infinite client timeout
bug (err..., feature). One thing I can't understand: when client is
unavailable, that's what I see in director's log after initial attempt to
start a job:
21-Aug 14:06 ros-dir: Vaio.2007-08-21_14.00.00 Warning: bnet.c:853 Could not
connect to File daemon on xxx.xxx.xxx.148:9102. ERR=Connection timed out
Retrying ...
Why is it retrying??? I have client connect timeout set to 5 minutes in
director config but it keeps retrying for up to 12 hours! There is nothing to
be found in documentation. Here's my job resources:
Job {
Name = "Vaio"
JobDefs = "DefaultJob"
Client = Vaio
FileSet="VaioSet"
Schedule = "VaioSchedule"
}
JobDefs {
Name = "DefaultJob"
Type = Backup
Level = Incremental
Client = Roz
FileSet = "Full Set"
Storage = RLS
Messages = Standard
Pool = GenePool
SpoolData = yes
Priority = 10
}
These sections does not mention anything about retrying or rescheduling failed
jobs, so what's going on?
Thanks,
Ivan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
