Hi everybody, "Max Wait Time" has been corrected in 2.3.18 but I still have problems using it.
I set it up to 5 min because I want my jobs to fail if they have to wait for something unusual or abnormal such as a mount request. Here is my setup : =========== bacula-dir.conf : Max Wait Time = 5 min Job report : 25-May 01:34 fft-dir JobId 17551: Fatal error: Max wait time exceeded. Job canceled. 25-May 02:23 fft-dir JobId 17551: Bacula XXX-dir 5.0.2 (28Apr10): 25-May-2011 02:23:09 Build OS: i486-pc-linux-gnu debian 5.0.4 JobId: 17551 Job: BackupCatalog.2011-05-24_20.05.00_54 Backup Level: Full Client: "scratchy" 5.0.2 (28Apr10) i486-pc-linux-gnu,debian,5.0.4 FileSet: "Catalog" 2009-09-01 09:31:28 Pool: "OUTSIDE2" (From User input) Catalog: "MyCatalog" (From Client resource) Storage: "LTO2" (From Pool resource) Scheduled time: 24-May-2011 20:05:00 Start time: 25-May-2011 02:23:05 End time: 25-May-2011 02:23:09 Elapsed time: 4 secs Priority: 4 =========== In this run, the job has to wait to start because of job concurrency. Since "Max Wait Time" counts from when the job starts (and not when scheduled), I thing this job shouldn't have been canceled. Source : http://www.bacula.org/5.0.x-manuals/en/main/main/Configuring_Director.html#6941 Your opinion ? Best regards, Fabrice. ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
