Hi Josip Am 04.11.2016 um 09:54 schrieb Josip Deanovic: > I am guessing that you have other jobs with higher priority that > got run before this job you are monitoring and at the time the > bacula was ready to run it, its scheduled time was already past > by more than 600 seconds (10 minutes) and the is configured to > fail in that case. > maybe you got me wrong :-) It's not the question why this job has been canceled. It's canceled because this is an hourly job and huge daily backups run around this time. So we decided to "kill" the hourly jobs quite fast, as an hour later will be the next run.
The question was more: why the job is not completely canceled by 02:10 (10min after scheduled starttime)? Why took it until 02:36 to cancel it, although bacula logged at 02:10 that the job is canceled 04-Nov 02:10 zabbix-dir JobId 571889: Fatal error: Max run time exceeded. Job canceled. 04-Nov 02:36 zabbix-dir JobId 571889: Fatal error: Job canceled because max start delay time exceeded. Cheers tobi ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
