Hi list, I don't know how or why, but for some reason two disabled jobs ran, twice even after disabling them. The reason they were disabled was that the run after script had a major bug that would sooner or later screw up the client. Well, unfortunately that's exactly what happened.
I'm kind of out of ideas about how or why that happened. I'm absolutely positive that I disabled the jobs last week on Wednesday. Luckily did I define system jobs that backed up the operating system so that I can restore the box and have it back up and running in no time. But I'm still absolutely clueless as how or why bacula would even trigger a job that's been disabled. We performed an upgrade to 2.4.4 today which went smoothly and everything is up and running. Until yesterday we had 2.4.3 up which seemed to be working good too. However skimming through the logs and double checking with the currently enabled and disabled jobs I have just noticed other candidates which exposed the same behaviour. Any clues as if to what might be happening are greatly appreciated. This will give me a bad nights sleep. I stop the client daemons on the clients now, just to be sure. Best regards Ronald -- Mit freundlichen Grüßen Ronald Buder Dipl-Ing.(BA) Profi.Com AG Büro Dresden Stresemannplatz 3 D-01309 Dresden Tel.: +49 (351) 440080 Fax.: +49 (351) 4400818 Mobil: +49 179 321 83 66 mail: rbu...@proficom-ag.de ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
