On Mon, Apr 05, 2010 at 12:46:25PM +0200, Harald Schmalzbauer wrote:

> Absurdly canceled job 47:
> Fatal error: Max run time exceeded. Job canceled.
> Scheduled time:         04-Apr-2010 21:01:03
>  Start time:             04-Apr-2010 21:39:41
>  End time:               04-Apr-2010 21:39:41
>  Elapsed time:           0 secs

Hm, yeah, not much sense. Was that incremental job or ? 
It looks like it has 'Incremental Max Run Sched Time' 
instead of 'Incremental Max Run Time'... 
Did you try increasing it to see if that's really what is causing 
problems ? All other timeouts are bigger than one hour so really
shouldn't be the problem.

> Here's my conf regarding max times:
> Max Start Delay = 14400 # 4h to wait after scheduled start
> Max Run Time = 1800 # Half an hour to run after beeing really started
> Incremental Max Run Time = 900 # 15 Minutes for incrementals after  
> beeing started
> Max Run Sched Time = 36000 # 10 hours to wait to start job as planned
> Max Wait Time = 7200 # 2h to wait for resources after job really started

Which version of bacula is that ? There were bugs not too far ago
where 'Max Wait Time' wrongly acted like 'Max Run Time'; maybe it had
similar problems with other related directives too.

See http://www.bacula.org/en/dev-manual/New_Features.html

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users