Can someone explain why the job is canceled.
I use Max Wait Time = 10 minutes

Output of the log-file:
03-Jan 23:27 itshas-sv11-dir JobId 1317: Start Backup JobId 1317, 
Job=BCK-itshas-sv041.2009-01-03_23.23.09
03-Jan 23:27 itshas-sv11-dir JobId 1317: Using Device "lto4drive"
03-Jan 23:27 itshas-sv11-sd JobId 1317: Volume "Week4" previously written, 
moving to end of data.
03-Jan 23:27 itshas-sv11-sd JobId 1317: Ready to append to end of Volume 
"Week4" at file=6.
itshas-sv041-fd JobId 1317:      /dev is a different filesystem. Will not 
descend from / into /dev
itshas-sv041-fd JobId 1317:      /home is a different filesystem. Will not 
descend from / into /home
03-Jan 23:37 itshas-sv11-dir JobId 1317: Fatal error: Max wait time exceeded. 
Job canceled.

...

Scheduled time:         03-Jan-2009 23:23:00
Start time:             03-Jan-2009 23:27:01
End time:               03-Jan-2009 23:38:10

...

"Ready to append to end of Volume Week4 ... " means the write-action is ready 
to start. At that moment there is no blocking of a resource. So why is the job 
canceled ?

additional info:
I also use Maximum Concurrent Jobs = 1
I have scheduled 4 jobs at 23:23. The first one is OK al the others are 
canceled. 
Running Bacula  2.4.3 on CentOS 5.2




------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users