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 7f6b22ce3685 sp > > 7fffc977bb60 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 1, 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 paranoiayes enable-cachepasswd yes positive-time-to-live passwd 600 negative-time-to-live passwd 20 suggested-size passwd 1 check-files passwd yes persistent passwd yes shared passwd yes max-db-size passwd 134217728 auto-propagate passwd yes enable-cachegroup yes positive-time-to-live group 3600 negative-time-to-live group 60 suggested-size group 1 check-files group yes persistent group yes shared group yes max-db-size group 134217728 auto-propagate group yes enable-cachehosts no positive-time-to-live hosts 3600 negative-time-to-live hosts 20 suggested-size hosts 1 check-files hosts yes persistent hosts yes shared hosts yes max-db-size hosts 134217728 enable-cacheservicesyes positive-time-to-live services28800 negative-time-to-live services20 suggested-size services1 check-files servicesyes persistent servicesyes shared servicesyes max-db-size services134217728 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 -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1280390063.5114.4.ca...@larosa.fritz.box
Bug#574990: nscd crashes after moderate use
Hi again, > 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. Hm, even after setting restart-interval to 600 nscd keeps crashing: Jul 29 10:06:42 niska kernel: [29035521.984129] nscd[24114]: segfault at 10 ip 7fa46659b685 sp 7fffec52f6b0 error 6 in nscd[7fa466595000+1c000] -- Lukas -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1280392251.5114.6.ca...@larosa.fritz.box
Bug#574990: nscd crashes after restart after sshd hangs
Hello, with libnss-ldap and nscd on lenny latest from time to time we have unresolved bug #552431, which makes sshd hanging due to suddenly unresolvable "sshd" system user. Today nscd crashed after sshd hanging and login was possible. I set "paranoia yes" in nscd.conf without setting "restart-interval" so it should be default 3600. Now nscd crashed, probably while restarting itself: Jul 29 11:00:43 quadopt3 kernel: [3616361.904197] nscd[6891]: segfault at 10 ip 7f587be30685 sp 7fffd960 error 6 in nscd[7f587be2a000+1c000] Set "persistent no" now and restarted nscd. Current config is below. Any help for solving this and #552431 is most welcome ! Thanks, Hermann nscd.conf: debug-level 0 # reload-count5 paranoiayes # restart-interval3600 enable-cachepasswd yes positive-time-to-live passwd 600 negative-time-to-live passwd 20 suggested-size passwd 211 check-files passwd yes persistent passwd no shared passwd yes max-db-size passwd 33554432 auto-propagate passwd yes enable-cachegroup yes positive-time-to-live group 3600 negative-time-to-live group 60 suggested-size group 211 check-files group yes persistent group no shared group yes max-db-size group 33554432 auto-propagate group yes # hosts caching is broken with gethostby* calls, hence is now disabled # per default. See /usr/share/doc/nscd/NEWS.Debian. enable-cachehosts no positive-time-to-live hosts 3600 negative-time-to-live hosts 20 suggested-size hosts 211 check-files hosts yes persistent hosts no shared hosts yes max-db-size hosts 33554432 enable-cacheservicesyes positive-time-to-live services28800 negative-time-to-live services20 suggested-size services211 check-files servicesyes persistent servicesno shared servicesyes max-db-size services33554432 -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100729100446.gb8...@lemon.iwr.uni-heidelberg.de
Bug#413934: Bug appears to be fixed in squeeze glibc
I've tested minicom in a squeeze chroot using the byte sequence I provided earlier. I could not reproduce the problem. Minicom displays a strange character (as would be expected) but does not assert. I tested with: ii libc6 2.11.2-2 Embedded GNU C Library: Shared libraries ii minicom2.4-2 friendly menu driven serial communication program So, I think we can call this fixed in squeeze. Thanks. Mike. -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100729113028.ga32...@mcrowe.com
Bug#574990: nscd crashes after moderate use
On Thu, Jul 29, 2010 at 10:30:51AM +0200, Lukas Kolbe wrote: > Hi again, > > > 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. > > Hm, even after setting restart-interval to 600 nscd keeps crashing: > > Jul 29 10:06:42 niska kernel: [29035521.984129] nscd[24114]: segfault at 10 > ip 7fa46659b685 sp 7fffec52f6b0 error 6 in nscd[7fa466595000+1c000] Could you please run an additional test: If you set the cache-size to a really small value, does is crash faster? I have the suspicion that the crash might occur the first time a cache slot is replaced. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100730010027.gb8...@galadriel.inutil.org
