From owner-freebsd-isp Tue Apr 7 00:54:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13415 for freebsd-isp-outgoing; Tue, 7 Apr 1998 00:54:19 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13410 for ; Tue, 7 Apr 1998 00:54:17 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id AAA07571; Tue, 7 Apr 1998 00:53:04 -0700 (PDT) Message-Id: <199804070753.AAA07571@implode.root.com> To: R Ricci cc: freebsd-isp@FreeBSD.ORG Subject: Re: VERY strange network(?) problem In-reply-to: Your message of "Tue, 07 Apr 1998 01:17:38 MDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 07 Apr 1998 00:53:04 -0700 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I'm having a very strange problem with our web/mail server (running >2.2.1), and I'd appreciate any pointers any of you could give me. Part of >my problem is that I'm not sure exaclty what methods I can use for >tracking down the source of my difficulties. > >Often, during TCP connections to the server, the connection will "stall", >ie. I get no data for several seconds/minutes. This causes huge problems, >of course, when it comes to checking mail, retrieving web pages, etc. At >frist, I suspected disk problems, but experimentation has pretty much >ruled this out. Doing a 'ps' on the server while one of these stalls is >occuring reveals that the offending process is just in state S or I, not >waiting on the disk. > >The only clue I have (and it may not be relevant) is the following >message, which keeps showing up in /var/log/messages/ : > >arplookup 207.201.65.2 failed: host is not on local network > >This IP is on our gateway. It's another interface on that gateway, but not >on our local network. (Our server sees the gateway as 207.201.125.65). I'm >not sure what I need to do do fix this. > >Any help, and/or suggestions of additional things to try will be very >welcome! Sounds like you might be running out of mbuf clusters. Have you specified an amount with the NMBCLUSTERS kernel option? If not, what do you have maxusers set to in your config file? Also, about how many simultaneous TCP connections do you expect have at any time? A rough number of http hits/day might also be useful in calculating an appropriate number of buffers. To confirm this is the cause, you might also look for the message "Out of mbuf clusters" in your /var/log/messages file. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message