i have set   FD Connect Timeout = 2min in the director config

if the fd ist stopped and the client-system is running, i get :

> 22-Aug 12:13 backup-dir: thomasws2.2007-08-22_12.11.28 Fatal error: 
> bsock.c:129 Unabl
> e to connect to File daemon on thomasws2:9102. ERR=Connection refused
> 22-Aug 12:13 backup-dir: thomasws2.2007-08-22_12.11.28 Error: Bacula 
> backup-dir 2.2.0
>  (08Aug07): 22-Aug-2007 12:13:35
....
>   Start time:             22-Aug-2007 12:11:30
>   End time:               22-Aug-2007 12:13:35
>   Elapsed time:           2 mins 5 secs

if the client is unreachable (NIC cable removed) i get

> 22-Aug 12:16 backup-dir: thomasws2.2007-08-22_12.14.17 Fatal error: 
> bsock.c:129 Unable to connect to File daemon on thomasws2:9102. 
> ERR=Interrupted system call
> 22-Aug 12:16 backup-dir: thomasws2.2007-08-22_12.14.17 Error: Bacula 
> backup-dir 2.2.0 (08Aug07): 22-Aug-2007 12:16:34
...
>   Start time:             22-Aug-2007 12:14:19
>   End time:               22-Aug-2007 12:16:34
>   Elapsed time:           2 mins 15 secs


booth works as expected.


Regards

Thomas

Ivan Adzhubey schrieb:
> 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

-- 
[:O]###[O:]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to