From owner-freebsd-isp Sat Aug 18 17: 7:17 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 5FE0037B408 for ; Sat, 18 Aug 2001 17:06:57 -0700 (PDT) (envelope-from jan@digitaldaemon.com) Received: (qmail 40051 invoked from network); 19 Aug 2001 00:04:41 -0000 Received: from unknown (HELO digitaldaemon.com) (192.168.0.73) by digitaldaemon.com with SMTP; 19 Aug 2001 00:04:41 -0000 Message-ID: <3B7F0291.8040708@digitaldaemon.com> Date: Sat, 18 Aug 2001 20:04:33 -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: "Forrest W. Christian" Cc: Tom Samplonius , FreeBSD ISP Subject: Re: slashdotted: /kernel: xl0: no memory for rx list -- packet dropped! References: Content-Type: multipart/alternative; boundary="------------060306000004090003030500" 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 --------------060306000004090003030500 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Forrest W. Christian wrote: >On Sat, 18 Aug 2001, Jan Knepper wrote: > >>>You need more mbufs. Use "netstat -m". >>> >> 603 mbufs allocated to data >> 38 mbufs allocated to packet headers >>601/1024/1024 mbuf clusters in use (current/peak/max) >> > >Yep, definately more mbufs. See the tuning man page on how to increase >this... > I'll get more memory first and than on the next upgrade to 4.4 take care of this... >>>>Is there anyway to clean this up without having to reboot the system? >>>> >>>Seems to be FTP connections. Try stopping and then starting your FTP >>>service. >>> >>Tried that... Didn't make any difference... >> > >Try doing a sockstat to see what owns it... > I don't think they show there... I must be blind... Jan sockstat | grep "63.105.9.61" http httpd 40029 16 tcp4 63.105.9.61:80 *:* news nnrpd 39747 0 tcp4 63.105.9.61:119 63.168.39.174:1431 news nnrpd 39747 1 tcp4 63.105.9.61:119 63.168.39.174:1431 news nnrpd 39747 2 tcp4 63.105.9.61:119 63.168.39.174:1431 news nnrpd 39746 0 tcp4 63.105.9.61:119 65.3.181.59:62907 news nnrpd 39746 1 tcp4 63.105.9.61:119 65.3.181.59:62907 news nnrpd 39746 2 tcp4 63.105.9.61:119 65.3.181.59:62907 news nnrpd 39623 0 tcp4 63.105.9.61:119 154.33.254.5:63743 news nnrpd 39623 1 tcp4 63.105.9.61:119 154.33.254.5:63743 news nnrpd 39623 2 tcp4 63.105.9.61:119 154.33.254.5:63743 news nnrpd 39326 0 tcp4 63.105.9.61:119 154.33.254.2:63741 news nnrpd 39326 1 tcp4 63.105.9.61:119 154.33.254.2:63741 news nnrpd 39326 2 tcp4 63.105.9.61:119 154.33.254.2:63741 http httpd 95822 16 tcp4 63.105.9.61:80 *:* http httpd 95818 3 tcp4 63.105.9.61:80 62.100.1.107:1386 http httpd 95818 16 tcp4 63.105.9.61:80 *:* http httpd 95814 3 tcp4 63.105.9.61:80 202.83.72.3:30317 http httpd 95814 16 tcp4 63.105.9.61:80 *:* http httpd 95811 16 tcp4 63.105.9.61:80 *:* news innd 878 4 tcp4 63.105.9.61:119 *:* root httpd 822 16 tcp4 63.105.9.61:80 *:* --------------060306000004090003030500 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Forrest W. Christian wrote:
On Sat, 18 Aug 2001, Jan Knepper wrote:

You need more mbufs.  Use "netstat -m".
        603 mbufs allocated to data
        38 mbufs allocated to packet headers
601/1024/1024 mbuf clusters in use (current/peak/max)

Yep, definately more mbufs.   See the tuning man page on how to increase
this...
I'll get more memory first and than on the next upgrade to 4.4 take care of this...
Is there anyway to clean this up without having to reboot the system?

Seems to be FTP connections.  Try stopping and then starting your FTP
service.

Tried that... Didn't make any difference...

Try doing a sockstat to see what owns it...
I don't think they show there... I must be blind...

Jan



sockstat | grep "63.105.9.61"
http     httpd    40029   16 tcp4   63.105.9.61:80        *:*
news     nnrpd    39747    0 tcp4   63.105.9.61:119       63.168.39.174:1431
news     nnrpd    39747    1 tcp4   63.105.9.61:119       63.168.39.174:1431
news     nnrpd    39747    2 tcp4   63.105.9.61:119       63.168.39.174:1431
news     nnrpd    39746    0 tcp4   63.105.9.61:119       65.3.181.59:62907
news     nnrpd    39746    1 tcp4   63.105.9.61:119       65.3.181.59:62907
news     nnrpd    39746    2 tcp4   63.105.9.61:119       65.3.181.59:62907
news     nnrpd    39623    0 tcp4   63.105.9.61:119       154.33.254.5:63743
news     nnrpd    39623    1 tcp4   63.105.9.61:119       154.33.254.5:63743
news     nnrpd    39623    2 tcp4   63.105.9.61:119       154.33.254.5:63743
news     nnrpd    39326    0 tcp4   63.105.9.61:119       154.33.254.2:63741
news     nnrpd    39326    1 tcp4   63.105.9.61:119       154.33.254.2:63741
news     nnrpd    39326    2 tcp4   63.105.9.61:119       154.33.254.2:63741
http     httpd    95822   16 tcp4   63.105.9.61:80        *:*
http     httpd    95818    3 tcp4   63.105.9.61:80        62.100.1.107:1386
http     httpd    95818   16 tcp4   63.105.9.61:80        *:*
http     httpd    95814    3 tcp4   63.105.9.61:80        202.83.72.3:30317
http     httpd    95814   16 tcp4   63.105.9.61:80        *:*
http     httpd    95811   16 tcp4   63.105.9.61:80        *:*
news     innd       878    4 tcp4   63.105.9.61:119       *:*
root     httpd      822   16 tcp4   63.105.9.61:80        *:*

--------------060306000004090003030500-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message