From owner-freebsd-current@FreeBSD.ORG Tue Nov 18 11:37:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EAA916A4CE for ; Tue, 18 Nov 2003 11:37:51 -0800 (PST) Received: from web14107.mail.yahoo.com (web14107.mail.yahoo.com [216.136.172.137]) by mx1.FreeBSD.org (Postfix) with SMTP id 0FCBD43F93 for ; Tue, 18 Nov 2003 11:37:50 -0800 (PST) (envelope-from cguttesen@yahoo.dk) Message-ID: <20031118193749.22575.qmail@web14107.mail.yahoo.com> Received: from [194.248.174.33] by web14107.mail.yahoo.com via HTTP; Tue, 18 Nov 2003 20:37:49 CET Date: Tue, 18 Nov 2003 20:37:49 +0100 (CET) From: =?iso-8859-1?q?Claus=20Guttesen?= To: Scott Long In-Reply-To: <3FB71CC3.9060408@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: current@freebsd.org Subject: Re: FreeBSD current, apache and php4 woes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Nov 2003 19:37:51 -0000 Hi. > > > >>>panic: kmem_malloc(4096): kmem_map too small: > >>>275251200 total allocated cpuid = 0; lapic.id = > >>>00000000 > >> > You'll either want to raise the size of the kmem_map > pool or decrease the maximum number of vnodes allowed > (vnodes get allocated out of the kmem_map and are > likely depleating it > Add one of the two lines to /boot/loader.conf: > > kern.vn.kmem.size=350000000 > or > kern.maxvnodes=150000 > > The first one is probably the better choice for you > since > the very nature of what you are doing demands that > you touch a lot of vnodes. > > Scott It seems that your advice helpted cure the patient. I did two things: 1. added kern.vm.kmem.size=450000000 2. clean up tmp-files older than 4 hours every hour (previous was files older than 12 h.). Now the servers has been quite stable, no reboot in almost two days! My problem appears to be too many files in /tmp and /var/tmp (50.000 or more) which made the kernel puke. I guess this is a scenario which we will see more often. Would it be possible to output this situation to the message-log before the server simply reboots? I did install 4.9 but in my particular case the server would stop responding to web-request after a few hours, but would respond to ping. Console login was imposible. So 5.1 is more mature in my case. The last two weeks have been _very_ frustrating. ;-) Claus Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan