Hide Forgot
Description of problem: After about 48 hours stable work of bgpd process, we got something like this: 2011/05/02 20:00:53 BGP: SLOW THREAD: task bgp_read (7fe1665c8f40) ran for 7866ms (cpu time 7ms) 2011/05/02 20:01:02 BGP: Import timer expired. 2011/05/02 20:01:21 BGP: Performing BGP general scanning 2011/05/02 20:13:38 BGP: scanning IPv4 Unicast routing tables 2011/05/02 20:13:39 BGP: scanning IPv6 Unicast routing tables 2011/05/02 20:13:39 BGP: SLOW THREAD: task bgp_scan_timer (7fe1665d3fd0) ran for 738072ms (cpu time 4753ms) 2011/05/02 20:13:41 BGP: [Event] BGP connection from host 213.135.44.166 2011/05/02 20:13:41 BGP: [Event] Make dummy peer structure until read Open packet 2011/05/02 20:13:41 BGP: [Event] BGP connection from host 2001:1a68:0:c::1 2011/05/02 20:13:41 BGP: [Event] Make dummy peer structure until read Open packet 2011/05/02 20:13:42 BGP: [Event] BGP connection from host 193.219.28.69 2011/05/02 20:13:42 BGP: [Event] Make dummy peer structure until read Open packet 2011/05/02 20:13:42 BGP: [Event] BGP connection from host 2001:1a68:a:3000::133 2011/05/02 20:13:42 BGP: [Event] Make dummy peer structure until read Open packet 2011/05/02 20:13:42 BGP: [Event] BGP connection from host 193.111.37.105 2011/05/02 20:13:42 BGP: [Event] Make dummy peer structure until read Open packet 2011/05/02 20:13:42 BGP: [Event] BGP connection from host 2001:1a68:a:3000::130 2011/05/02 20:13:42 BGP: [Event] Make dummy peer structure until read Open packet 2011/05/02 20:13:43 BGP: 213.135.44.166 [Event] BGP connection closed fd 18 2011/05/02 20:13:43 BGP: [Event] BGP connection from host 213.135.44.133 2011/05/02 20:13:43 BGP: [Event] Make dummy peer structure until read Open packet 2011/05/02 20:13:43 BGP: [Event] BGP connection from host 2001:1a68:0:c::1 2011/05/02 20:13:43 BGP: [Event] Make dummy peer structure until read Open packet 2011/05/02 20:13:43 BGP: 213.135.44.134 [Event] BGP connection closed fd 21 2011/05/02 20:13:43 BGP: 213.135.44.166 [Event] BGP connection closed fd 18 2011/05/02 20:13:44 BGP: 2001:1a68:a:3000::130 [Event] BGP connection closed fd 14 2011/05/02 20:13:44 BGP: 213.135.44.135 [Event] BGP connection closed fd 24 2011/05/02 20:13:44 BGP: 213.135.44.131 [Event] BGP connection closed fd 15 2011/05/02 20:13:44 BGP: 213.135.44.130 [Event] BGP connection closed fd 22 2011/05/02 20:13:44 BGP: 213.135.44.134 [Event] BGP connection closed fd 21 2011/05/02 20:13:44 BGP: 213.135.44.166 [Event] BGP connection closed fd 18 2011/05/02 20:13:44 BGP: 2001:1a68:a:3000::130 [Event] BGP connection closed fd 14 2011/05/02 20:13:44 BGP: 213.135.44.135 [Event] BGP connection closed fd 24 2011/05/02 20:13:44 BGP: 213.135.44.131 [Event] BGP connection closed fd 15 2011/05/02 20:13:44 BGP: 213.135.44.130 [Event] BGP connection closed fd 22 2011/05/02 20:13:44 BGP: 213.135.44.134 [Event] BGP connection closed fd 21 2011/05/02 20:13:44 BGP: 213.135.44.166 [Event] BGP connection closed fd 18 Version-Release number of selected component (if applicable): [root@cosmos log]# rpm -q quagga quagga-0.99.18-1.fc14.x86_64 quagga-0.99.18-1.fc14.i686 How reproducible: Install quagga from fedora 14 updates, make some ebgp session with full bgp feed Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Quagga from Fedora 13 worked well without any problem
I'd like to ask you about working version. You've mentioned that quagga of F13 worked. - which version of quagga of F13 worked - does quagga-0.99.18-1.f13 work - did you test quagga-0.99.18-1.fc14 as the first F14 version. What about downgraded version. Thanks, Jiri
I have just found reason [182496.068965] Out of memory: kill process 2383 (bgpd) score 7792 or a child [182496.070133] Killed process 2383 (bgpd) vsz:2337840kB, anon-rss:463864kB, file-rss:88kB It's look like FC14 (kernel, glibc) consumes/ need more RAM memory, anyway You can close this ticket.