[Bacula-users] Finding (and killing) Phanton job IDs

Hello,

We have a working bacula (5.0.3) instance with a MySQL backend. A few weeks ago we had a power outage that caused the server to shut down and restart abruptly. The jobs are running successfully but now there is a complete set of phantom jobs running in parallel that fail.

Bconsole only shows the successful JobIds. If I do a status of a client only the successful job IDs show up. The failed job IDs increment just as one would expect if they were valid jobs. An example of the successful job IDs are 730, 731, 732. An example of the phantom/failing job IDs are 900, 901, 902. As you can see they are not in the same sequence. The successful job IDs follow the previously successful job IDs (prior to the crash).

I looked around in the database but I was unable to determine where they are stored so that I could remove them. I have confirmed that there is only one instance of bacula running on the server.

Any pointers as to where I might look would be appreciated,

Karyn

Karyn Stump

IT Administrator

FastSoft, Inc

karyn AT fastsoft DOT com

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

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