On Wednesday 23 June 2010 19:41:24 Martin Simmons wrote:
> >>>>> On Wed, 23 Jun 2010 08:42:25 -0600, Robert LeBlanc said:
> >
> > My SD has been crashing every night and I finally got a backtrace. I
> > don't know what all this means, but I could sure use some help to figure
> > out why it keeps crashing and how to stop it so that I can get some
> > back-ups done.
> >
> > ...
> >
> > Program received signal SIGUSR2, User defined signal 2.
>
> SIGUSR2 is probably benign (and hence not the cause of the original crash).
>
> I suggest ignoring it in gdb by using the command
>
> handle SIGUSR2 nostop noprint pass
>
> before running bacula-sd.
>

Yes, as Martin says, SIGUSR2 is something that should be ignored.  We use it 
internally to signal between threads, and when you are running the debugger 
on Bacula, you need to tell the debugger to ignore it -- as Martin indicates, 
or most often, when I am manually debugging, I start it with "run -s -f ...".  
For more information, see the Kaboom chapter of the "Problems" manual.

Of course, if Bacula sent you the traceback (or put it in your working 
directory), you should open a bug report and post it there, and we will look 
at it.

Regards,

Kern

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users