Hi,

I have setup all my clients with "SDConnectTimeout = 2 minute" and I  
still have the problem that some jobs block others. In this particular  
case the storage daemon didn't respond:

Running Jobs:
JobId Level   Name                       Status
======================================================================
  1120 Increme  system_d01-webhost-xxx_vserver.2008-06-01_02.43.53 is  
waiting on Storage File-ext
  1136 Full    system_d01-webhost-aaa.2008-06-01_02.43.09 is running
  1137 Full    system_d01-webhost-aaa_vserver.2008-06-01_02.43.10 is  
waiting on max Client jobs
  1158 Full    data_bacularchiv_d01-webhost-xxx.2008-06-01_05.09.31 is  
waiting on max Client jobs
  1169 Full    data_bacularchiv_d01-webhost-aaa.2008-06-01_05.09.42 is  
waiting on max Client jobs
  1178 Full    BackupCatalog.2008-06-01_23.10.51 is waiting for higher  
priority jobs to finish
  1180 Full    conf_dnshost.2008-06-02_00.01.53 is waiting on Storage  
File-ext

Shouldn't the Bacula client cancel the job if the storage daemon takes  
longer than 2 minutes (in my case) to connect? Could it be just a  
stupid syntax error in "SDConnect Timeout = 2 minute" - I am not sure  
here about "minute" or "minutes".
After I restartet the storage daemon (that holds the definitions to  
"Storage File" and "Storage File-ext" all jobs waiting on "File-ext"  
failed an the backup process moved on.


Thanks

Stefan

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