Bug#574990: nscd crashes after moderate use
Am Mittwoch, den 28.07.2010, 23:20 -0400 schrieb Moritz Muehlenhoff:
> On Mon, Mar 22, 2010 at 06:55:00PM +0100, Lukas Kolbe wrote:
> > Package: nscd
> > Version: 2.7-18lenny2
> > Severity: grave
> >
> > Hi,
> >
> > on all (?) our servers we see repeated crashes of nscd:
> >
> > [ 3687.306397] nscd[3340]: segfault at 10 ip 00007f6b22ce3685 sp 00007fffc977bb60 error 6 in nscd[7f6b22cdd000+1c000]
> >
> > This happens mostly between 3000 and 6000 seconds after starting. We
> > have 3003 users in our LDAP, so we increased the 'suggested-size' to a
> > high prime number 99991, removed the dbs and restarted nscd. The crashes
> > happen nevertheless, rendering nscd completely unusable on our systems.
> > I'd like to provide more debugging information, but I don't really know
> > how at the moment ...
>
> I'm currently setting up a similar test environment with Lenny
> and Squeeze to see if I can reproduce it.
>
> nscd has configuration options to force a continuous restart, see
> the options "paranoia" and "restart-interval" in nscd.conf. Does
> nscd keep up if you set it to something like 600?
>
> You should probably use this in conjunction with the "persistent"
> settings.
Sorry, I forgot to mention that - of course we set paranoia mode on, but
that doesn't help at all. I'll set the restart-interval down to 600 to
see if it helps. Here's our default configuration for reference:
debug-level 0
paranoia yes
enable-cache passwd yes
positive-time-to-live passwd 600
negative-time-to-live passwd 20
suggested-size passwd 99991
check-files passwd yes
persistent passwd yes
shared passwd yes
max-db-size passwd 134217728
auto-propagate passwd yes
enable-cache group yes
positive-time-to-live group 3600
negative-time-to-live group 60
suggested-size group 99991
check-files group yes
persistent group yes
shared group yes
max-db-size group 134217728
auto-propagate group yes
enable-cache hosts no
positive-time-to-live hosts 3600
negative-time-to-live hosts 20
suggested-size hosts 99991
check-files hosts yes
persistent hosts yes
shared hosts yes
max-db-size hosts 134217728
enable-cache services yes
positive-time-to-live services 28800
negative-time-to-live services 20
suggested-size services 99991
check-files services yes
persistent services yes
shared services yes
max-db-size services 134217728
As soon as we test our first fileserver with Squeeze (which will take a
few more months probably), I hope to report this bug is non-existant
there ;)
Thanks for your help!
--
Lukas
Reply to: