[Bacula-users] Bacula 5.0.x Max Wait Time

Hi,

I wonder if the MaxWaitTime problem is still unsolved in Bacula 5.0.x
It was discussed/bug reported several times in earlier years, and 
again and again promised to be solved in the next release.  

There is a chart in the bacula manual (in the Job section of director
configuration), showing the relations between 

Max Run Sched Time
Max Start Delay
Max Run Time
Max Wait Time

This illustration implies that MaxWaitTime is unaffected by the span
of time between schedule and start.  Due to the chart, MaxWaitTime 
begins to count _after_ the job has started, when a blocking situation
is given.  This is also the meaning of the textual definition there:

»Max Wait Time = time
    The time specifies the maximum allowed time that a job may block waiting 
for a resource (such as waiting for a tape to be mounted, or waiting for the 
storage or file daemons to perform their duties), counted from the when the job 
starts, (not 
necessarily the same as when the job was scheduled). This directive works as 
expected since bacula 2.3.18. «

De facto, this isn't the case.  I've got this job definiton:

...
        MaxStartDelay = 6 hours
        MaxRunTime = 2 hours
        MaxWaitTime = 1 hour
...

According to the chart in the manual, it should be ok if the job has 
to wait for start for up to 6 hours after it was scheduled (f.i. if 
jobs with a higher priority still keeb on running)  Once started, it 
may run for up to 2 hours, within this span of time, it may be 
interrupted for up to 1 hour.

But, again and again, I get this job cancelled with this log:

23-May 00:15 bup-serv-dir JobId 140008: Fatal error: Max wait time exceeded. 
Job canceled.
...
  Scheduled time:         22-May-2013 23:15:00
  Start time:             23-May-2013 04:07:05
  End time:               23-May-2013 04:07:05
  Elapsed time:           0 secs

This is, the job is _scheduled_ at 23:15, and cancelled due to exceeded
MaxWaitTime after 1 hour, at 00:15, when it wasn't started at all.  
Obviously, MaxWaitTime is counted from when the job is SCHEDULED, 
and NOT from when the job STARTS.

Thus, either the manual is wrong (text + chart), or this is a bug.  


I'm right? 


Best regards,

        Robert


----------------------------------------------------------------
+++    German Research Center for Artificial Intelligence    +++
----------------------------------------------------------------
Dipl.-Inform. Robert V. Wirth, Campus D3_2, D-66123 Saarbruecken
@office: +49-681-85775-5078 / -5572 +++ @fax: +49-681-85775-5020
mailto:Robert.Wirth AT dfki DOT de ++++++++++ http://www.dfki.de/~wirth
----------------------------------------------------------------


------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users