From owner-freebsd-questions Thu May 24 17: 6:45 2001 Delivered-To: freebsd-questions@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id BBF5737B422 for ; Thu, 24 May 2001 17:06:42 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (rgnout.regenstrief.org [134.68.31.38]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f4P09PX08053; Thu, 24 May 2001 19:09:26 -0500 Message-ID: <3B0DA20D.3B9D0525@aurora.regenstrief.org> Date: Fri, 25 May 2001 00:06:37 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jakub Kruszona-Zawadzki Cc: freebsd-questions@FreeBSD.ORG Subject: Re: how to configure FreeBSD for big traffic References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jakub Kruszona-Zawadzki wrote: > > FreeBSD 4.2 > > We have very big www trafic. (about 13 hits/sec on peek - yes 15mln/month) > netstat -n | wc -l , gives numbers about 1500 > > kernel was compiled with option MAXUSERS=512 > and ... > after about a month our server suddenly started to behave a little bit > crazy. First one, then more machines from our LAN lost ability to see > our server. > > my /var/log/messages : > > May 22 18:08:27 szafa1 /kernel: arplookup 192.168.1.72 failed: could not > allocate llinfo > May 22 18:08:27 szafa1 /kernel: arpresolve: can't allocate llinfo for > 192.168.1.72rt > (...) > May 22 18:49:38 szafa1 /kernel: arplookup 192.168.1.1 failed: could not > allocate llinfo > > arp -a wrote nothing: > > su-2.04# arp -a > su-2.04# > > ifconfig -a wrote nothing too: > > su-2.04# ifconfig -a > su-2.04# > > after reboot server works good. > it happened two times. where is the problem ?, how to patch it - static > arps ? or what ? This smells awfully like routing problem. You do firewall/NAT stuff as I can tell from your 192.168.0.0/16 addresses. This can be one cause of problem. Does arp -d -a clear the problem? I have seen the llinfo issue before and this was fixed by straightening out the routes. But I may be wrong. -Gunther -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message