I have added a gdb-backtrace of the last segfault.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in ubuntu.
https://bugs.launchpad.net/bugs/622742
Title:
Bacula Storage-daemon dies with segfault if a File-daemon can’t be
** Attachment added: bacula segfault gdb backtrace
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/622742/+attachment/1891858/+files/bacula_segfault.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in ubuntu.
I have added a gdb-backtrace of the last segfault.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/622742
Title:
Bacula Storage-daemon dies with segfault if a File-daemon can’t be
contacted
--
** Attachment added: bacula segfault gdb backtrace
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/622742/+attachment/1891858/+files/bacula_segfault.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: bacula
Error message in daemon.log:
bacula-sd: Bacula interrupted by signal 11: Segmentation violation
Error messages given by the bacula-director:
Not accessible clients:
17-Aug 04:37 cxl05010-dir JobId 869: Warning: bsock.c:129 Could not connect to
Public bug reported:
Binary package hint: bacula
Error message in daemon.log:
bacula-sd: Bacula interrupted by signal 11: Segmentation violation
Error messages given by the bacula-director:
Not accessible clients:
17-Aug 04:37 cxl05010-dir JobId 869: Warning: bsock.c:129 Could not connect to
