[quagga-dev 4351] bug in bgpd?

Piotr Chytla pch at packetconsulting.pl
Mon Sep 11 10:00:12 BST 2006


Hi

This is quite strange , but from last friday our bgpd (0.99.4) have started crashing . 
(I works stable from 2 months or more)

Here are some stacktraces from quagga logs:

BGP: Received signal 11 at 1157887222 (si_addr 0x72206f8c, PC 0x805c47e); aborting...
Program counter: /usr/lib/quagga/bgpd(peer_sort+0x45)[0x805c47e]
Backtrace for 10 stack frames:
/usr/lib/libzebra.so.0(zlog_backtrace_sigsafe+0x28)[0xb7f2b767]
/usr/lib/libzebra.so.0(zlog_signal+0x230)[0xb7f2b737]
/usr/lib/libzebra.so.0[0xb7f32e8a]
/lib/tls/libc.so.6[0xb7da8a10]
/usr/lib/quagga/bgpd[0x807f90a]
/usr/lib/quagga/bgpd[0x807fa8d]
/usr/lib/libzebra.so.0(thread_call+0x6f)[0xb7f2124e]
/usr/lib/quagga/bgpd(main+0x251)[0x805ba0d]
/lib/tls/libc.so.6(__libc_start_main+0xf4)[0xb7d95974]
/usr/lib/quagga/bgpd[0x805b661]

BGP: Received signal 11 at 1157796716 (si_addr 0x10001, PC 0x512c1bbb); aborting...          
Program counter: /usr/lib/libzebra.so.0(work_queue_run+0x68)[0x512c1bbb]                     
Backtrace for 8 stack frames:                                                                
/usr/lib/libzebra.so.0(zlog_backtrace_sigsafe+0x28)[0x512b9767]                              
/usr/lib/libzebra.so.0(zlog_signal+0x230)[0x512b9737]                                        
/usr/lib/libzebra.so.0[0x512c0e8a]                                                           
/lib/tls/libc.so.6[0x51136a10]                                                               
/usr/lib/libzebra.so.0(thread_call+0x6f)[0x512af24e]                                         
/usr/lib/quagga/bgpd(main+0x251)[0x805ba0d]                                                  
/lib/tls/libc.so.6(__libc_start_main+0xf4)[0x51123974]                                       
/usr/lib/quagga/bgpd[0x805b661]                       

We have quite simple bgp config , 2 full transit (62.111.145.121,
62.233.250.101), 2 private peerings (62.233.179.162,62.233.179.163), and 
2 ibgp connections (87.99.32.1,87.99.32.34)

kaermorhen.2.core|vtysh# show ip bgp summary 
BGP router identifier 62.111.145.123, local AS number 38944
RIB entries 363189, using 22 MiB of memory
Peers 6, using 15 KiB of memory

Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down
State/PfxRcd
62.111.145.121  4 12968  155852    1563        0    0    0 05:17:56 194644
62.233.179.162  4 35586     781     782        0    0    0 12:58:57 3
62.233.179.163  4 64513     781     782        0    0    0 12:58:58 2
62.233.250.101  4 15833   46728    1561        0    0    0 12:58:59 15
87.99.32.1      4 38944    1945     781        0    0    0 12:58:58 1026
87.99.32.34     4 38944     780     782        0    0    0 12:59:00 0

Total number of neighbors 6

Everthing works great till friday when I add ibgp session to 87.99.32.34,
(accesslist 50 blocks everything, 10 pass only our network prefix)

 neighbor 87.99.32.34 remote-as 38944
 neighbor 87.99.32.34 description rtr-0.1.core
 neighbor 87.99.32.34 activate
 neighbor 87.99.32.34 next-hop-self
 neighbor 87.99.32.34 soft-reconfiguration inbound
 neighbor 87.99.32.34 distribute-list 50 in
 neighbor 87.99.32.34 distribute-list 10 out

I don' suppouse that the last session mess up becouse I've similar one
87.99.32.1 - config is fairly the same. 


Other question why , clear [session IP] stay in work queue ? 

kaermorhen.2.core|bgpd# show work-queues 
      List (ms)   Q. Runs       Cycle Counts   
P    Items  Hold    Total    Best  Gran.   Avg. Name
         0   500    44363   22500   7502   6459 process_main_queue
         0   500        0       0      1      0 process_rsclient_queue
         0    10       82    3280   1078   2372 clear 62.111.145.121


/pch

-- 
Dyslexia bug unpatched since 1977 ...
exploit has been leaked to the underground.



More information about the Quagga-dev mailing list