Harald Schmalzbauer schrieb am 08.04.2010 20:18 (localtime):
Am 08.04.2010 14:20, schrieb Matija Nalis: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
...
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 startedIncremental Max Run Time = 900 # 15 Minutes for incrementals after beeing startedMax 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 startedWhich 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.I'm running 5.0.1. First job took longer than 30 minutes, so it was canceled. Second job took 9 minutes, so start time of third job is 39minutes after scheduled. There's no other time limit which could fit, "Max Wait Time" is 2 hours.
Hello, this weekend the same thing happened again.I intentionally set the "Max Run Time" to 30 mins, but it is not working. It hoses all other subsequent jobs but the one following.
Again to visualize my timetable: at 21:00h: startjob1 - startjob2 - startjob3 - startjob4 - startjob5 ---------------------------------------------------------- runing waiting waiting waiting waiting ---------------------------------------------------------- > 30 mins canceled running waiting waiting waiting ---------------------------------------------------------- - finisehd canceled ok (8min) (0s runtime) waiting waiting ---------------------------------------------------------- - - - canceled (0s runtime) waiting ---------------------------------------------------------- - - - - canceled (0s runtime) Why do job 3-5 get cancelled with 0s runtime? How can I file a bug report? Another thing:The canceled (due to runtime longer than 30mins) job reports 0 Bytes written, but in fact it should have been writing for 30 minutes. Which seems to be tha case if I compare Volume Bytes:
At last volume usage: 162,598,409,235 (162.5 GB) Canceled Job reports: Elapsed time: 30 mins 22 secs Priority: 10 FD Files Written: 0 SD Files Written: 0 FD Bytes Written: 0 (0 B) SD Bytes Written: 0 (0 B) Rate: 0.0 KB/s Software Compression: None VSS: no Encryption: no Accurate: no Volume name(s): MonthA Volume Session Id: 73 Volume Session Time: 1270146159 Last Volume Bytes: 174,597,640,742 (174.5 GB) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Non-fatal FD errors: 0 SD Errors: 0 FD termination status: Error SD termination status: Running Termination: Backup CanceledSo it has written 12GB. Are the reports only valid for correctly terminated jobs? I think even for canceled or other error termination it should report as many correct values as possible.
Thanks, -Harry
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users