On Fri, Nov 04, 2016 at 12:37:42PM +0100, Josip Deanovic wrote: > On Friday 2016-11-04 10:33:03 jahlives wrote: > > Hi Josip > > > > 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. > > Because according to the report you got from the bacula the job didn't > start at 02:00, it started at 02:36. > And what bacula actually did (according to its report): > > Scheduled time: 04-Nov-2016 02:00:00 > > Start time: 04-Nov-2016 02:36:34 > > End time: 04-Nov-2016 02:36:34
Just to add my 2 cents: it looks like Bacula is unable to cancel a scheduled job. Scheduled job have to go into "running" state before it can be cancelled. I would interpret your log lines as follow: at 2:00 job enters "Scheduled" state, but something prevents it from running. At 2:10 Bacula issues a "cancellation order", but as job is not "running" yet nothing happens. Job finally gets a chance to run at 2:36, but because there is a outstanding "cancellation order" on the job it gets terminated straight away. Misha -- Vanush "Misha" Paturyan Senior Technical Officer Room 120 Computer Science Department Eolas Bulding Maynooth University Maynooth ext: 4539 ------------------------------------------------------------------------------ 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 Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
