Re: [CentOS] rt_cache leak in 2.6.18
On Wednesday 11 February 2009, Hector Herrera wrote: ... After about 2-3 days, the kernel complains about dst cache overflow and even thought it hasn't crashed, the network is un-responsive. All IP forwarding stops and the server cannot be reached from any network interfaces. ... According to http://linux.derkeiler.com/Mailing-Lists/Fedora/2005-07/1175.html this is a known bug that was fixed in 2.6.11, however, I'm running 2.6.18 (as updated with `yum update`) I downloaded the kernel sources, and indeed, the kernel source contains the bug fix in the above article. Therefore ... I'm at a loss as to where to go from here. Certainly rebooting the server every day is not an option, and increasing the max_size will just delay it. Suggestions? Have a look around the upstream (rh) bugzilla to see if there is a fix in the pipe. If not then you'll have to either run a newer kernel or add the patch to the centos-kernel and rebuild it (both ways are quite messy). /Peter Thank you, Hector signature.asc Description: This is a digitally signed message part. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rt_cache leak in 2.6.18
According to http://linux.derkeiler.com/Mailing-Lists/Fedora/2005-07/1175.html this is a known bug that was fixed in 2.6.11, however, I'm running 2.6.18 (as updated with `yum update`) It could be something new. I got dst cache overflows before and it was a while before they finally identified the bug for the one I saw. Some references below. All I remember was that the chap who finally paid some attention really had to dig through the code before he found it and informed Dave Miller. http://oss.sgi.com/cgi-bin/extract-mesg.cgi?a=netdevm=2004-06i=40CF3A35.3070906%40outblaze.com http://marc.info/?l=linux-netdevm=109953032629224w=2 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rt_cache leak in 2.6.18
Hector Herrera wrote: Hello, This is a CentOS 5.2 box configured as a router for a network handling about 200-300 Mbps, routing traffic to/from the internet for about 6,000 IPs. Therefore ... I'm at a loss as to where to go from here. Certainly rebooting the server every day is not an option, and increasing the max_size will just delay it. Suggestions? Use a real router or L3 switch to do the job instead of a PC? Or run the newer patched kernel on the system. 300mbit is trivial. Even modern good gigabit L3 switches can forward over 100 million packets per second, which is tens of gigs of data. (not talking cisco gear, it's astonishing how poor performing most cisco gear is given their prices). nate ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
