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

Bug#339350: marked as done (nscd fails to start when logfile is too big)

Your message dated Tue, 6 Feb 2007 11:00:18 +0100
with message-id <20070206100018.GA29637@mad.intersec.eu>
and subject line nscd fails to start when logfile is too big
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)
--- Begin Message --- 
Package: nscd
Version: 2.3.5-8
Severity: important


When the logfile of nscd reaches a 2GB limit, nscd will no longer start
without any hint whatsoever. It will run in the -d mode, but not as a
daemon. 

Strace in that case looks like:
pid 23058] write(3, "23052: handle_request: request r"..., 69) = -1
EFBIG (File too large)
[pid 23058] --- SIGXFSZ (File size limit exceeded) @ 0 (0) ---

/var/log# ls -al nscd.log
[..] 2147483647 Nov 14 17:56 nscd.log

I can imagen it is a problem, but i would prefer continueing without
logfile and printing something in syslog   or   giving a hint at startup
or a hint from the init.d script. 

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages nscd depends on:
ii  libc6                         2.3.5-8    GNU C Library: Shared libraries an

nscd recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Tue, Nov 15, 2005 at 06:56:56PM +0100, Tom Albers wrote:
> Package: nscd
> Version: 2.3.5-8
> Severity: important
> 
> 
> When the logfile of nscd reaches a 2GB limit, nscd will no longer start
> without any hint whatsoever. It will run in the -d mode, but not as a
> daemon. 
> 
> Strace in that case looks like:
> pid 23058] write(3, "23052: handle_request: request r"..., 69) = -1
> EFBIG (File too large)
> [pid 23058] --- SIGXFSZ (File size limit exceeded) @ 0 (0) ---
> 
> /var/log# ls -al nscd.log
> [..] 2147483647 Nov 14 17:56 nscd.log
> 
> I can imagen it is a problem, but i would prefer continueing without
> logfile and printing something in syslog   or   giving a hint at startup
> or a hint from the init.d script. 

  well the problem here is because the user nscd runs under has some
kind of rlimit for its max file size set (apparently) to 2Go. So nscd is
killed by a SIGXFSZ signal.

  As it's not a common setup, I don't see why nscd should deal with it
specifically: when you set specifically ulimits for a user, well, you have
to get used to some daemons be killed randomly.

  Also note that by default nscd uses the syslog, so there is no
logrotate file for /var/log/nscd.log, you have to write one yourself.
Here lies the real problem IMHO (as a 2Go log file per day seems
completely irrational to me).

  Hence, I'm closing the bug report as invalid.

Cheers,
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: pgpHQJMnEohNv.pgp
Description: PGP signature


--- End Message ---
Reply to: