Date: Mon, 4 Dec 2000 13:42:44 -0800 From: David Kirchner <dpk@parodius.com> To: freebsd-questions@freebsd.org Subject: route table growth, never expiring Message-ID: <20001204134244.T37639@parodius.com>
next in thread | raw e-mail | index | archive | help
Hi, We're running a 4.1-RELEASE web server that is serving a whole-lotta-traffic. At one point, the route table grew to the maximum it was allowed, 64260K. According to route monitor, there were a lot of "RTM_MISS"s - I don't know what that means exactly. Anyways, after doing a "route flush" and then re-adding the default route, the route table started from scratch and is continuing to grow, now at 92361 entries (12.9 megs). It's going to get 64MB again, and it's going to start dropping incoming connections. This problem generates many errors per second in the Apache error_log: [Mon Dec 4 13:41:38 2000] [error] (54)Connection reset by peer: getsockname [Mon Dec 4 13:41:38 2000] [error] (54)Connection reset by peer: getsockname [Mon Dec 4 13:41:38 2000] [error] (54)Connection reset by peer: getsockname [Mon Dec 4 13:41:38 2000] [error] (54)Connection reset by peer: getsockname [Mon Dec 4 13:41:38 2000] [error] (54)Connection reset by peer: getsockname [Mon Dec 4 13:41:38 2000] [error] (54)Connection reset by peer: getsockname Has anyone else seen this problem? Could the radix tree be getting too full for the route expiration process to function properly? - dpk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001204134244.T37639>