[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#75856: marked as done (nscd runs itself out of fd's, makes all name resolutions fail)



Your message dated Tue, 15 Jun 2004 07:47:23 +0200
with message-id <1087278442.3619.574.camel@thanatos>
and subject line Bug#75856: Still a problem?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 29 Oct 2000 17:35:43 +0000
>From brianr@osiris.978.org Sun Oct 29 11:35:43 2000
Return-path: <brianr@osiris.978.org>
Received: from bluebox.ne.mediaone.net (osiris.978.org) [::ffff:24.168.164.38] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 13pwMx-0005mt-00; Sun, 29 Oct 2000 11:35:43 -0600
Received: (qmail 13291 invoked by uid 1000); 29 Oct 2000 17:35:39 -0000
Date: Sun, 29 Oct 2000 12:35:39 -0500
From: Brian Ristuccia <brian@ristuccia.com>
To: submit@bugs.debian.org
Subject: nscd runs itself out of fd's, makes all name resolutions fail
Message-ID: <20001029123539.W26232@osiris.978.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Delivered-To: submit@bugs.debian.org

Package: nscd
Version: 2.1.95-1
Severity: critical 

Somehow nscd is leaking fd's. It eventually uses every one it can allocate
and then the system enters a state where all nscd queries return immediately
with no data. ls and ps entries return with a numeric instead of a username,
it becomes impossible to log in or use su, etc. 

Leading up to the problem, you'll see:

Oct 28 13:11:16 osiris nscd: 27946: while accepting connection: Too many open files

intermittantly in the logs for a few days until it eventually hoses itself:

Oct 29 12:23:20 osiris nscd: 27946: while accepting connection: Bad file descriptor
Oct 29 12:23:20 osiris last message repeated 98 times

-- 
Brian Ristuccia
brian@ristuccia.com
bristucc@cs.uml.edu

---------------------------------------
Received: (at 75856-done) by bugs.debian.org; 15 Jun 2004 05:47:34 +0000
>From jdthood@aglu.demon.nl Mon Jun 14 22:47:34 2004
Return-path: <jdthood@aglu.demon.nl>
Received: from post-20.mail.nl.demon.net [194.159.73.1] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1Ba6nG-0007L0-00; Mon, 14 Jun 2004 22:47:34 -0700
Received: from [82.161.38.140] (helo=localhost)
	by post-20.mail.nl.demon.net with esmtp (Exim 3.36 #2)
	id 1Ba6nE-000Mvn-00
	for 75856-done@bugs.debian.org; Tue, 15 Jun 2004 05:47:32 +0000
Received: from localhost (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP id F194912D221
	for <75856-done@bugs.debian.org>; Tue, 15 Jun 2004 07:47:24 +0200 (CEST)
Subject: Re: Bug#75856: Still a problem?
From: Thomas Hood <jdthood@aglu.demon.nl>
To: 75856-done@bugs.debian.org
In-Reply-To: <20040614212801.GQ12011@osiris.978.org>
References: <1087246062.3619.520.camel@thanatos>
	 <20040614212801.GQ12011@osiris.978.org>
Content-Type: text/plain
Message-Id: <1087278442.3619.574.camel@thanatos>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Tue, 15 Jun 2004 07:47:23 +0200
Content-Transfer-Encoding: 7bit
Delivered-To: 75856-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

On Mon, 2004-06-14 at 23:28, Brian Ristuccia wrote:
> I'm now running 2.2.5-11.5 at a pretty large site with dozens of machines,
> and I haven't seen it get hosed like this in a long while. I suppose it's
> safe to mark this bug done even if none of the changelogs specificly claim
> it's fixed.

OK, let's hope it got fixed along the way somewhere.

--
Thomas



Reply to: