[quagga-dev 10232] Quagga SEGV (possibly due to logrotate SIGUSR1)

Jeroen Massar jeroen at massar.ch
Fri Jan 25 08:07:05 GMT 2013


Package: quagga
Severity: high

High severity as quagga gets killed, which it should not be doing...

Stack trace below.

I guess the below (and thus quagga dying) comes from the logrotate
script, which sends a kill -SIGUSR1 every once in a while.

/etc/logrotate.d/quagga has:
 kill -USR1 `cat /var/run/quagga/$i.pid`

USR1 is 10 though, SIGSEGV is the 11 listed below

It does not happen all the time, but it does happen often enough to be
quite annoying.

Hence having a /etc/cron.d/quagga_restarter with
8<------------------
# /etc/cron.d/quagga_restarter: restart Quagga if is dead

*/1 * * * * root  [ ! -e /var/run/quagga/bgpd.pid ] || [ ! -f /proc/`cat
/var/run/quagga/bgpd.pid`/exe ] && /etc/init.d/quagga restart
------------------->8

to restart bgpd when it dies...

Greets,
 Jeroen

--

BGP: Received signal 11 at 1359074051 (si_addr 0x0); aborting...
Backtrace for 13 stack frames:
/usr/lib/libzebra.so.0(zlog_backtrace_sigsafe+0x3e)[0x7fccd8082b07]
/usr/lib/libzebra.so.0(zlog_signal+0x234)[0x7fccd8083081]
/usr/lib/libzebra.so.0(+0x364c9)[0x7fccd808b4c9]
/lib/libc.so.6(+0x32230)[0x7fccd7460230]
/usr/lib/libzebra.so.0(sockunion_cmp+0x1)[0x7fccd807683b]
/usr/lib/quagga/bgpd(+0x442da)[0x7fccd85152da]
/usr/lib/quagga/bgpd(+0x4473e)[0x7fccd851573e]
/usr/lib/quagga/bgpd(+0x44a77)[0x7fccd8515a77]
/usr/lib/libzebra.so.0(work_queue_run+0xb5)[0x7fccd808beec]
/usr/lib/libzebra.so.0(thread_call+0x67)[0x7fccd807880b]
/usr/lib/quagga/bgpd(main+0x3fc)[0x7fccd850192f]
/lib/libc.so.6(__libc_start_main+0xfd)[0x7fccd744cc8d]
/usr/lib/quagga/bgpd(+0x30985)[0x7fccd8501985]




More information about the Quagga-dev mailing list