>>>>> On Sun, 13 Oct 2013 18:25:07 -0700, David Newman said:
> 
> On 10/9/13 4:41 PM, David Newman wrote:
> > FreeBSD 9.2-RELEASE, bacula-client-5.2.12_3 installed from ports
> > 
> > Ever since upgrading this host to FreeBSD 9.2, bacula-fd crashes as soon
> > as bacula-dir starts a backup job. The entry in /var/log/messages is:
> > 
> > Oct  9 16:25:50 o bacula-fd: Bacula interrupted by signal 0: UNKNOWN SIGNAL
> > 
> > Backups worked fine on this host running FreeBSD 9.1 and other hosts
> > upgraded to FreeBSD 9.2 run backups OK.
> > 
> > I've done the uninstall/reinstall thing with the bacula-client port, but
> > that made no difference.
> > 
> > Thanks in advance for troubleshooting clues.
> > 
> > dn
> 
> Is there a Wireshark decode for Bacula?
> 
> I'm still stuck on this problem, and need more info on what's causing
> that UNKNOWN SIGNAL error. Wireshark 1.8.6 just shows strings of bytes
> for the Bacula stuff.
> 
> Thanks.
> 
> dn

A wireshark decode won't help much here because problems like this must be in
the fd itself.

Try attaching gdb to the bacula-fd process and see if it catches the
mysterious signal (see
http://www.bacula.org/5.2.x-manuals/en/problems/problems/What_Do_When_Bacula.html#SECTION00640000000000000000).

If that doesn't catch it, then try the gdb command

break signal_handler

(signal_handler prints the "Bacula interrupted by signal" message).

__Martin

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users