After updating from bacula-5.2.10 to 5.2.11, I noticed segfaults with bacula-dir. Also bacula would only run the first job after being restarted. All jobs after the first one show up as "job xxx is waiting for execution". Downgrading to version 5.2.10 fixed the problems. I am using bacula on a x86 system with a SCSI tape library (DELL PV 124T). I can remember similar problems about 2 years ago. Bacula would only run the first job. After job completion, it could not send the notification email, and got stuck. Therefore only the first job after restart of bacula-dir was executed. Maybe this time it is a similar problem, that bacula-dir tries to complete a job and gets stuck there (sending an email, writing a log, etc.) Reproducible: Always Steps to Reproduce: 1. Restart bacula-dir after upgrading to version 5.2.11 2. First job finishes succesfully. 3. All other jobs get status "job xxx is waiting for execution".
Some more information: 1. It does not make any difference if you start the jobs manually on bconsole, or if the jobs are automatically scheduled for execution. 2. The bacula log does not contain any error messages. 3. Storage daemon works fine, communication to the clients is also working.
this version is not anymore in tree, please test 5.2.12
bacula-5.2.12 is working fine. Sorry for the trouble. Please close this bug.
