From owner-freebsd-hackers Fri Sep 18 05:33:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19358 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 05:33:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19341 for ; Fri, 18 Sep 1998 05:32:46 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.8/8.6.9) id OAA17792 for ; Fri, 18 Sep 1998 14:39:53 +0200 (SAST) Received: by citadel via recvmail id 17790; Fri Sep 18 14:39:06 1998 From: Graham Wheeler Message-Id: <199809181237.OAA03132@cdsec.com> Subject: FreeBSD hanging/rebooting To: hackers@FreeBSD.ORG Date: Fri, 18 Sep 1998 14:37:40 +0200 (SAT) X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks We have a couple of clients are complaining about their systems hanging or rebooting. Usually this is preceded by some `fork: resource temporarily unavailable' log messages, or failed calls to socket() (usually by named). There are also occasional log messages generated by inetd, of the form: `realloc: junk pointer (too low to make sense)'. The obvious explanation is that the file descriptor table is too small. I have built a new kernel, with MAXUSERS set to 100, and a modified param.c which sets NPROC to (64+16*MAXUSERS) (i.e. 1664) and maxfiles to (NPROC*10) (i.e. 16640). Unfortunately, this hasn't solved the problem. I have got a client to send me the output of `top' and `lsof' when the log messages start appearing, and it appears to occur when there are typically 100-200 processes running, and about 500-600 open files, with less than 50% of the swap space used, and a load average of about 2. The system should hardly be breaking sweat, from all appearances, but there are at least four separate systems on which this is occuring. These are all running FreeBSD 2.2.2; we are about to upgrade them to 2.2.7 but I'm not sure that will solve the problem. At the moment I can't seem to be able to access www.freebsd.org (even though I can ping it), so I haven't been able to search the site for clues. But if anyone can suggest anything else worth trying, I would appreciate it. TIA gram -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message