07-Jul 22:15 backup-dir JobId 542: Fatal error: Max wait time exceeded. Job canceled.
07-Jul 22:19 backup-dir JobId 542: Bacula backup-dir 5.2.6 (21Feb12):
  Build OS:               x86_64-pc-linux-gnu debian jessie/sid
  JobId:                  542
  Job:                    Pollux_OS_Backup.2015-07-07_22.05.05_02
  Backup Level:           Incremental, since=2015-07-06 22:16:45
  Client:                 "pollux-fd" 5.0.2 (28Apr10) x86_64-pc-linux-gnu,debian,6.0.6
  FileSet:                "Pollux OS Full Set" 2015-06-08 17:00:43
  Pool:                   "Pollux Daily" (From Job IncPool override)
  Catalog:                "MyCatalog" (From Client resource)
  Storage:                "File" (From Job resource)
  Scheduled time:         07-Jul-2015 22:05:05
  Start time:             07-Jul-2015 22:19:14
  End time:               07-Jul-2015 22:19:14
  Elapsed time:           0 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):         
  Volume Session Id:      0
  Volume Session Time:    0
  Last Volume Bytes:      0 (0 B)
  Non-fatal FD errors:    1
  SD Errors:              0
  FD termination status:  
  SD termination status:  
  Termination:            Backup Canceled


07-Jul 22:21 backup-dir JobId 544: Fatal error: Max wait time exceeded. Job canceled.
07-Jul 22:21 backup-dir JobId 544: Bacula backup-dir 5.2.6 (21Feb12):
  Build OS:               x86_64-pc-linux-gnu debian jessie/sid
  JobId:                  544
  Job:                    Frodo_Backup.2015-07-07_22.10.00_04
  Backup Level:           Incremental, since=2015-07-06 22:24:32
  Client:                 "frodo-fd" 5.2.6 (21Feb12) Microsoft Windows Server 2008 Standard Edition Service Pack 2 (build 6002), 32-bit,Cross-compile,Win32
  FileSet:                "Frodo Full Set" 2015-06-13 19:20:11
  Pool:                   "Frodo Daily" (From Job IncPool override)
  Catalog:                "MyCatalog" (From Client resource)
  Storage:                "File" (From Job resource)
  Scheduled time:         07-Jul-2015 22:10:00
  Start time:             07-Jul-2015 22:21:55
  End time:               07-Jul-2015 22:21:55
  Elapsed time:           0 secs
  Priority:               11
  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):         
  Volume Session Id:      0
  Volume Session Time:    0
  Last Volume Bytes:      0 (0 B)
  Non-fatal FD errors:    1
  SD Errors:              0
  FD termination status:  
  SD termination status:  
  Termination:            Backup Canceled

Hello Brendan,

On Wed, Jul 8, 2015 at 12:27 PM, Brendan Martin <brendan AT physics.tamu DOT edu> wrote:

I have a Bacula Director 5.2.6 running on Debian 8.1.

To avoid an excessive delay in the backup schedule in the event of
insufficient volumes, I added a Max Wait Time value of 600 (seconds) in
the JobDefs for a couple of clients.  Jobs for those clients
subsequently were cancelled immediately upon starting, even though the
documentation indicates that the countdown for this setting begins when
a job actually starts, rather than when it is scheduled.

​The documentation​ says that the countdown for this setting begins when the job asks for a volume mount. And this time is a slightly different time than the time that the jobs starts. But it should be used to avoid that a job stucks waiting for a volume as you want.  Also, it is working as expected in version 5.2.6 (i have been using this version for a long time). Are you having issues with this? Could you send to the list your log files for this jobs/issues?

 

This appears to be exactly the same issue described in bug report 1586,
which was never satisfactorily resolved.

Has anyone else encountered this and been able to get the setting to
work as documented?

Thanks,
Brendan

​ Best regards,

Ana ​