From owner-freebsd-isp Sat Aug 18 9: 7:14 2001 Delivered-To: freebsd-isp@freebsd.org Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by hub.freebsd.org (Postfix) with SMTP id 226A837B411 for ; Sat, 18 Aug 2001 09:07:07 -0700 (PDT) (envelope-from jan@digitaldaemon.com) Received: (qmail 23330 invoked from network); 18 Aug 2001 16:04:46 -0000 Received: from unknown (HELO digitaldaemon.com) (192.168.0.73) by digitaldaemon.com with SMTP; 18 Aug 2001 16:04:46 -0000 Message-ID: <3B7E9205.7010604@digitaldaemon.com> Date: Sat, 18 Aug 2001 12:04:21 -0400 From: Jan Knepper User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: FreeBSD ISP Subject: slashdotted: /kernel: xl0: no memory for rx list -- packet dropped! Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! Last Thursday one of the sites I host got slashdotted (http://www.slashdot.com/) and amazingly FreeBSD 4.3 on PIII 600 Mhz with 128 MB RAM took the load gracefully. I.e. until around 5 PM EST when I got messages like: /kernel: xl0: no memory for rx list -- packet dropped! at the console... So what I did is, I terminated some of the daemon's that were not really used as a couple of httpd server, etc. This seemed to solve the problem, however... When I run a netstat -na right now I get the impression that there is still some garbadge in memory from this experience: As: tcp4 0 15360 63.105.9.61.20 217.80.179.220.2822 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.219.43.81.2591 LAST_ACK tcp4 0 15360 63.105.9.61.20 200.11.220.5.2535 LAST_ACK tcp4 0 15360 63.105.9.61.20 200.11.220.5.1736 LAST_ACK tcp4 0 15360 63.105.9.61.20 200.11.220.5.1735 LAST_ACK tcp4 0 15360 63.105.9.61.20 202.133.131.44.3651 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.4486 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.4338 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.3452 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.3449 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.1825 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.2922 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.2390 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.2310 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.1598 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.1597 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.1556 LAST_ACK tcp4 0 15360 63.105.9.61.20 193.124.148.213.1553 LAST_ACK tcp4 0 15360 63.105.9.61.20 203.195.181.4.1440 LAST_ACK I am sure this has been in there the last at least 24 hours and I can see nothing is happening. I suspect that this is because of the no memory for rx list, but I am not quite sure. I was kinda a cool feeling though that FreeBSD didn't give up, but still runs!!! Is there anyway to clean this up without having to reboot the system? Thanks! Jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message