Please examine the forwarded message and send the traceback and other
information they are asking for. Ideally you could post it directly to
the BTS at http://bugs.bacula.org/view.php?id=1098
--- Begin Message ---
A NOTE has been added to this issue.
======================================================================
http://bugs.bacula.org/view.php?id=1098
======================================================================
Reported By: jgoerzen
Assigned To:
======================================================================
Project: bacula
Issue ID: 1098
Category: Storage Daemon
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 06-13-2008 20:24 BST
Last Modified: 06-13-2008 20:50 BST
======================================================================
Summary: Storage Daemon dies
Description:
This bug was received by Debian at http://bugs.debian.org/486131
I think after the last update bacula-sd crashes spontaneously. I can
reproduce it, but don't know the exact cause.
Here is the strace of the bacula-sd process before it crashes.
You can get the whole strace here: http://cccmz.de/~xt3/storage
The reporter's bacula-sd.conf is included in the bug log at the above
URL.
He also states that the bacula log has nothing other than a message about
being unable to connect to the storage daemon.
======================================================================
----------------------------------------------------------------------
ebollengier - 06-13-08 20:50
----------------------------------------------------------------------
One thing that we can see in this giant log, is that bacula try to send a
backtrace to the administrator. And we need it. See /usr/sbin/btraceback to
know who have received the mail.
I think that the binary is stripped, so it might be useless.
Running the storage daemon in debug 200 (or more) is mandatory to have
information. (edit /etc/init.d/bacula-sd, set OPTIONS= to "-d200" and
redirect daemon output to a log file)
This line seems to indicate that the storage daemon have stopped with a
ASSERT().
> write(1, "13-Jun 14:23 bacula-sd: ABORTING"..., 128)
Issue History
Date Modified Username Field Change
======================================================================
06-13-08 20:24 jgoerzen New Issue
06-13-08 20:25 jgoerzen Issue Monitored: jgoerzen
06-13-08 20:50 ebollengier Note Added: 0003366
======================================================================
--- End Message ---
