Am 08.02.2014 12:34, schrieb Kern Sibbald:
> If there is no traceback, the manual explains how to get one
> by manually running the SD under the debugger.
Ok, I will check this all.
For your information, for older release I've use bug system
at debian.org:
https://bugs.debian.org/cgi-bin/bugreport
Hello,
A debug trace file is unlikely to help much in resolving SD crashes.
Far more useful is a stack trace, which Bacula calls a traceback.
If your SD was installed correctly, you are running it as root,
you have gdb on your system, and you have setup a proper
email, you should get the traceback
Hello,
it looks like an old issue already known on 5.0 release is still in 5.2.6.
If a backup job starts to a client which is not available because a user has
shut down the system the bacula-sd crashes. In the past on the old release
which I used in Squeeze this problem was known and I should upg
