Just to add a little more to this, this last time it crashed, the
director.conmsg
file had this:
--snip--
19-Oct 07:38 storage: Committing spooled data to Volume. Despooling
1,936,073,855 bytes ...
19-Oct 07:39 mx7: mx7.2005-10-19_05.00.06 Fatal error: job.c:1662 Comm error
with SD. bad response
Can anybody tell me what this message means?
My director process died a the same time?
Any thoughts?
Thanks,
Mike
[Switching to LWP 100632]
0x68120353 in pthread_testcancel () from /usr/lib/libpthread.so.1
---
This SF.Net email is spon
You will probably need to do two things to get a usable traceback.
1. Build Bacula with debug turned on, and ensure it is not stripped during the
installation process.
2. Run the Director under the debugger as indicated in the Kaboom chapter of
the manual, and when it crashes, submit the comman
Here's a crash I get almost every day...
Bacula 1.36, CentOS 4
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 25, 2005 6:30 PM
To: [EMAIL PROTECTED]
Subject: Bacula GDB traceback of bacula-dir
Using host libthread_db library "/lib/libthrea
