From owner-freebsd-bugs Wed Jan 15 05:50:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA02677 for bugs-outgoing; Wed, 15 Jan 1997 05:50:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA02670; Wed, 15 Jan 1997 05:50:01 -0800 (PST) Resent-Date: Wed, 15 Jan 1997 05:50:01 -0800 (PST) Resent-Message-Id: <199701151350.FAA02670@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.FAA02583;Wed; (8.8.4/8.8.4);, 15 Jan 1997 05:48:55.-0800 (PST) Message-Id: <199701151348.FAA02583@freefall.freebsd.org> Date: Wed, 15 Jan 1997 05:48:55 -0800 (PST) From: rob@ugh.net.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: kern/2501: too many open files Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2501 >Category: kern >Synopsis: too many open files >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 15 05:50:00 PST 1997 >Last-Modified: >Originator: Rob Wise >Organization: >Release: 2.2-BETA_A >Environment: FreeBSD WonK.hobart.TASed.EDU.AU 2.2-BETA_A >Description: Jan 16 00:32:12 WonK last message repeated 3 times Jan 16 00:32:12 WonK /kernel: file: table is full Jan 16 00:32:12 WonK syslogd: /var/run/utmp: Too many open files in system Jan 16 00:32:12 WonK last message repeated 3 times Jan 16 00:32:12 WonK /kernel: file: table is full Jan 16 00:32:13 WonK last message repeated 174 times This is after a few days uptime on my home machine. The only processes running apart from the basic system daemons are 1 pine, 1 ppp, 1 pppd and a few ssh client sessions, its not a heavily loaded machine. The problem didn't happen with the same config file under 2.1.5-RELEASE. It would appear that fd's aren't being closed properly somewhere because sendmail dies with similar errors every now and then. >How-To-Repeat: Leave the system up for a few days with some logging activity. >Fix: >Audit-Trail: >Unformatted: