Hi group, I've been using bacula succesfully for many months, coming from version 1.3x and now at 2.2.6. Ofcourse I have been upgrading and changing my config during this period.
Now I'm facing an annoying problem: now and then, my storage daemon seems to crash without an obvious reason. The director says something like : JobId 7728: Fatal error: <stored: bad response to Job command: No data available Then, a "Bacula GDB traceback of bacula-sd" is emailed to me. This behaviour seems to be random in time, it doesn't matter if bacula has been running for a while already or if I just restarted. I've already tried to downgrade to 2.2.5, maybe I can try to downgrade to 2.2.4. But ofcourse, I've changed things in time: adding clients, adding ClientRunBeforeJobs (for mysql backups), etc. I know I almost don't have any usefull input, but does anybody has an idea what I can do to diagnose this problem, or where to begin to search ? Thanks! K. ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
