Am Donnerstag, den 29.07.2010, 21:00 -0400 schrieb Moritz Muehlenhoff: > 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 00007fa46659b685 sp 00007fffec52f6b0 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.
I have set suggested-size to 11, rm /var/cache/nscd/* and a few minutes later it crashed: Jul 30 10:11:32 niska kernel: [29122212.408089] nscd[27240]: segfault at 10 ip 00007f1acbd48685 sp 00007fff24972820 error 6 in nscd[7f1acbd42000+1c000] Also setting the max-db-size to 11416 (the sizes of the files in /var/cache/nscd) didn't change the behaviour. FYI: niska:~# getent passwd | wc -l 3074 This alone doesn't trigger the crash, it happens only a few minutes afterwards. I've now set debug-level to 99, maybe it helps ... -- Lukas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
