Just to followup on this in case others have this issue. I was able to
rebuild bacula with the -g compiler option to get some debugging
information. The scenario that causes the SD to crash with a SEGFAULT
is not consistently reproducible which makes me think of some kind of
race condition.
Hi,
We've been seeing our Bacula Storage Daemon die with a segmentation
fault when a client can't be reached for backup. We have two servers
and have observed this behavior on both of them. Some searching has
revealed that others seem to have (or had) this same issue.
On Fri, 02 Sep 2011 10:19:40 -0400, Thomas Lohman said:
Hi,
We've been seeing our Bacula Storage Daemon die with a segmentation
fault when a client can't be reached for backup. We have two servers
and have observed this behavior on both of them. Some searching has
revealed that
I'm wondering if anyone else here has experienced this problem
and/or has any pointers to a work around. While things can be set up to
automatically restart the storage daemon if it dies, the main problem is
that any backups Bacula was in the middle of doing end with an error and
have to be
On 9/2/2011 10:50 AM, John Drescher wrote:
I'm wondering if anyone else here has experienced this problem
and/or has any pointers to a work around. While things can be set up to
automatically restart the storage daemon if it dies, the main problem is
that any backups Bacula was in the
Thanks John for your reply, can I ask if you use SSL to encrypt between the
client and the server?
No. I do not use any encryption at all.
Also, when you say the clients are not connected
when they are scheduled, does that also imply that their jobs fail i.e. when
it comes around to run the
