Hello, I am using bacula 2.0.3 on OpenSuse 10.2
I had my backup running during the weekend. On Monday I found the following hanging jobs: Running Jobs: JobId Level Name Status ====================================================================== 200 Full lupo.2007-07-13_20.00.23 is waiting on Storage File 203 Increme fiat.2007-07-13_20.00.26 is running 210 Full BackupCatalog.2007-07-13_23.10.00 is waiting for higher priority jobs to finish 234 Full lupo.2007-07-14_20.00.23 is waiting on Storage File 237 Increme fiat.2007-07-14_20.00.26 is running 243 Full BackupCatalog.2007-07-14_23.10.00 is waiting execution 267 Full lupo.2007-07-15_20.00.23 is waiting on max Client jobs 270 Differe fiat.2007-07-15_20.00.26 is waiting on max Client jobs 276 Full BackupCatalog.2007-07-15_23.10.00 is waiting execution ==== The client lupo was not switched on at all. After I canceled the jobs for lupo, the other jobs progressed. So this one job hold every other job up. Why doesn't bacula give me a timeout for the reason 'can not connect to....' for lupo or 'maximum run time exceeded' for fiat? >From what I found in the docu, the default time out is 30 minutes. Does this apply here? I haven't set any 'FD Connect Timeout' or 'SD Connect Timeout' in the config file. Thank you Wolfgang ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
