On Tue, 24 May 2016, Richard Savage wrote:
There seems to be a bug on loading prefixes from other neighbors and
bgp will crash at the same point everytime:
BGP: Received signal 10 at 1464125380 (si_addr 0x80143aa62); aborting...
Backtrace for 5 stack frames:
0x80091465d <zlog_backtrace_sigsafe+0x3d> at /usr/local/lib/libzebra.so.0
0x800913dc5 <zlog_signal+0x515> at /usr/local/lib/libzebra.so.0
0x80091f7a8 <signal_init+0x308> at /usr/local/lib/libzebra.so.0
0x801b71b37 <pthread_sigmask+0x507> at /lib/libthr.so.3
0x801b7122c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
in thread bgp_read scheduled from bgp_packet.c:2472
There are also a lot of messages in the logs regarding the following:
2016/05/24 22:29:40 BGP: unknown afi/safi (0/0)
2016/05/24 22:29:40 BGP: xxx.xxx.xxx.xxx[Info] UPDATE with unsupported AFI/SAFI
0/0
Has the above crash been looked at as a bug and is there a new release
due soon that might fix this?
Likely my fault, what ever it is.
There is this:
http://patchwork.quagga.net/patch/1921/
Though, it should only affect generation of a log message, I thought.
Can you get a better backtrace? It's the stuff past pthread_getspecific
I'd be interested in.
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
The [Ford Foundation] is a large body of money completely surrounded by
people who want some.
-- Dwight MacDonald
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
