https://bugzilla.novell.com/show_bug.cgi?id=387202 User mmarek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c1 --- Comment #1 from Michal Marek <mmarek@novell.com> 2008-05-06 07:27:19 MST --- Created an attachment (id=212695) --> (https://bugzilla.novell.com/attachment.cgi?id=212695) nscd log log output from the last run. I did rm /var/run/nscd/* /usr/sbin/nscd -d 2>&1 | tee log-nscd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c5 Petr Baudis <pbaudis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mmarek@novell.com --- Comment #5 from Petr Baudis <pbaudis@novell.com> 2008-06-25 17:30:38 MDT --- Hmm, do you still encounter this with the 11.0 nscd? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User mmarek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c8 --- Comment #8 from Michal Marek <mmarek@novell.com> 2008-06-26 06:16:34 MDT --- $ rpm -q nscd nscd-2.8-15 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User R.Vickers@cs.rhul.ac.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c10 --- Comment #10 from Bob Vickers <R.Vickers@cs.rhul.ac.uk> 2008-07-03 05:08:09 MDT --- Created an attachment (id=225788) --> (https://bugzilla.novell.com/attachment.cgi?id=225788) nscd core file I too am seeing many nscd crashes, sometimes every few minutes, and this stops Thunderbird working. I have attached a core file: is there any other information that would be useful? I am also happy to test any fixes that might be available. nscd is version 2.8-14.1 running on Opensuse 11.0 x86_64. Bob -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 Marton Balint <cus@fazekas.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |266219 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 Michal Marek <mmarek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Found By|--- |Development -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User james.faulkner@yale.edu added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c14 --- Comment #14 from James Faulkner <james.faulkner@yale.edu> 2008-08-18 10:39:26 MDT --- Created an attachment (id=233951) --> (https://bugzilla.novell.com/attachment.cgi?id=233951) NSCD debug log 2 the 2nd system's NSCD debug log. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User jpschewe@mtu.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c16 --- Comment #16 from Jon Schewe <jpschewe@mtu.net> 2008-08-22 10:49:47 MDT --- I too am having the same problem. I'm using LDAP for account information and kerberos for passwords. I'm seeing nscd crash on all of my servers at least every 15 minutes (I've got a script setup to restart every 5 if it's dead). I'm having this problem both in dom0 and in domU on xen as well as at home on my non-xen systems. I installed libnscd-debuginfo and then ran nscd -d in gdb and got the following: .. 6685: Reloading "103" in password cache! 6685: Reloading "13" in password cache! 6685: Reloading "100" in password cache! 6685: remove GETPWBYUID entry "0" 6685: remove GETPWBYNAME entry "root" nscd: mem.c:399: gc: Assertion `next_hash == &he[db->head->nentries]' failed. Program received signal SIGABRT, Aborted. [Switching to Thread 0x4103f950 (LWP 6688)] 0x00007fe6907ce5c5 in raise () from /lib64/libc.so.6 (gdb) where #0 0x00007fe6907ce5c5 in raise () from /lib64/libc.so.6 #1 0x00007fe6907cfbb3 in abort () from /lib64/libc.so.6 #2 0x00007fe6907c71e9 in __assert_fail () from /lib64/libc.so.6 #3 0x00007fe691362b68 in ?? () from /usr/sbin/nscd #4 0x00007fe691361494 in ?? () from /usr/sbin/nscd #5 0x00007fe6913582c6 in ?? () from /usr/sbin/nscd #6 0x00007fe690d14040 in start_thread () from /lib64/libpthread.so.0 #7 0x00007fe69086f0cd in clone () from /lib64/libc.so.6 (gdb) Unfortunately it doesn't appear there is a debuginfo package for nscd, so this doesn't help quite as much as I'd hoped. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User schuetzm@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c18 Marc Schütz <schuetzm@gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |schuetzm@gmx.net --- Comment #18 from Marc Schütz <schuetzm@gmx.net> 2008-09-25 06:39:18 MDT --- (In reply to comment #17 from Jon Schewe)

Which debuginfo packages would include the appropriate symbols to be able to get function names from the errors of nscd shown above?

glibc-debuginfo -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User kuenne@rentec.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c20 Karsten Kuenne <kuenne@rentec.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kuenne@rentec.com --- Comment #20 from Karsten Kuenne <kuenne@rentec.com> 2008-10-07 19:10:02 MDT --- Looks like Ubuntu has the same bug (#271423). But no solution there either. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User syseng@adnovum.ch added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c22 Bernd Nies <syseng@adnovum.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |syseng@adnovum.ch Priority|P5 - None |P2 - High --- Comment #22 from Bernd Nies <syseng@adnovum.ch> 2008-10-21 03:19:36 MDT --- We're having the same problem. OpenSUSE 11.0 (i386 and x86_64) with LDAP for authentication and NFS automount tables. It dies frequently within less than an hour. As result one cannot start Thunderbird (segfaults) and VMware Worstation 6.0.5 (freezes) as LDAP user after nscd has died. As local user it works. See also bug#157078 and http://bugs.gentoo.org/show_bug.cgi?id=223205. The only workaround for us is so far a watchdog daemon that restarts nscd every time it crashes. I can provide you a strace of nscd the next time it crashes. Best regards, Bernd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User grok@tnt.pl added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c24 Jaroslaw Zachwieja <grok@tnt.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grok@tnt.pl --- Comment #24 from Jaroslaw Zachwieja <grok@tnt.pl> 2008-10-22 06:36:53 MDT --- Created SRPM, minimal testing on 11.0: https://bugzilla.novell.com/show_bug.cgi?id=157078#c73 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User admin@fph.physik.uni-karlsruhe.de added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c25 Achim Mildenberger <admin@fph.physik.uni-karlsruhe.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |admin@fph.physik.uni-karlsruhe.de --- Comment #25 from Achim Mildenberger <admin@fph.physik.uni-karlsruhe.de> 2008-10-30 03:40:17 MDT --- Seems I ran into the same stability problem. I have 30 PCs running openSuSE 11.0 on 64 bit. I started logging of nscd now. A fix to the problem would be very welcome. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User R.Vickers@cs.rhul.ac.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c27 --- Comment #27 from Bob Vickers <R.Vickers@cs.rhul.ac.uk> 2008-10-30 04:37:32 MDT --- Luxury! I used the watchdog approach under SuSE 10.2, but under SuSE 11.0 I see nscd crashing every few minutes, or I did before I disabled it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User admin@fph.physik.uni-karlsruhe.de added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c29 --- Comment #29 from Achim Mildenberger <admin@fph.physik.uni-karlsruhe.de> 2008-10-31 07:08:07 MDT --- I employ now the watchdog-approach from Comment #26. Many Thanks for the code snippet! Just for statistical fun on Halloween: The avarage lifetime of nscd here is 144 minutes/SuSE-11.0-box. (average of crashes on 34 moderately loaded boxes during 14 hours). (Using NIS and DNS, openSuSE 11.0, x86-64, no ldap). Funny enough only in 11 (of 197) crashes there is a log from the kernel in syslog (mostly segfaults, sometimes "general protection"). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c31 --- Comment #31 from Petr Baudis <pbaudis@novell.com> 2008-11-03 05:51:48 MDT --- FWIW we are very strongly considering unscd for post-11.1, though nothing is decided yet. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c33 --- Comment #33 from Jon Nelson <jnelson-suse@jamponi.net> 2008-11-04 11:26:07 MST --- *If* you are going to try unscd *and* you are using apparmor, you'll need to edit /etc/apparmor.d/usr.sbin.nscd and right after capability net_bind_service, add: capability setgid, capability setuid, for it to work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c35 --- Comment #35 from Petr Baudis <pbaudis@novell.com> 2008-11-14 03:20:51 MST --- I'm planning to release packages at http://www.suse.de/~pbaudis/bug-387202 (will mirror out in an hour or two) as maintenance update for 11.0 in a short while. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c45 Petr Baudis <pbaudis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rickert@cs.niu.edu --- Comment #45 from Petr Baudis <pbaudis@novell.com> 2008-11-19 12:04:02 MST --- *** Bug 426396 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=426396 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c47 Petr Baudis <pbaudis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |x_pedro_x@hotmail.com --- Comment #47 from Petr Baudis <pbaudis@novell.com> 2008-11-19 12:25:48 MST --- *** Bug 426679 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=426679 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c49 Petr Baudis <pbaudis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jmatejek@novell.com --- Comment #49 from Petr Baudis <pbaudis@novell.com> 2008-12-04 11:19:50 MST --- *** Bug 157078 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=157078 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User walter.haidinger@gmx.at added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c51 Walter Haidinger <walter.haidinger@gmx.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |walter.haidinger@gmx.at --- Comment #51 from Walter Haidinger <walter.haidinger@gmx.at> 2008-12-05 00:32:47 MST --- Based on the severity and priority of this bug: How about adding the watchdog workaround as a patch into the current nscd package and release it as an update? That is, modify nscd to start a master process which monitors its child(ren), restart them automatically upon death (maybe with a log entry) and have it kill them upon exit. This patch should neither be that much to add nor too difficult. Of course this is not a real fix and quite ugly, IMHO. However, it would be a _quick_ workaround for all 11.0 installations to make nscd more stable (from the users point of view), relieving the users from implementing a watchdog themselves. It would also buy some time until the real bug is found and squashed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User admin@fph.physik.uni-karlsruhe.de added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c53 --- Comment #53 from Achim Mildenberger <admin@fph.physik.uni-karlsruhe.de> 2008-12-05 04:48:56 MST --- I also switched to unscd about 4 weeks ago on a pool of 34 machines. I haven't encountered any problem since. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User walter.haidinger@gmx.at added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c55 --- Comment #55 from Walter Haidinger <walter.haidinger@gmx.at> 2008-12-07 05:48:38 MST --- I see. So, I guess OpenSUSE 12.0 will scrap all those useless scripts in /etc/init.d and start everything from /etc/inittab, right? Nice. Maybe I need to clarify this: comment #51 _was_ meant seriously, no joke intended! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User walter.haidinger@gmx.at added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c57 --- Comment #57 from Walter Haidinger <walter.haidinger@gmx.at> 2008-12-08 06:00:21 MST --- Nice script but because of comment #54 quite obsolete, isn't it? :-\ No, seriously, if such a wrapper would be implemented in nscd itself _all_ SUSE users would benefit, even those not capable of writing a wrapper themselves or even those not be able to find (say being aware of) this bugzilla entry. Again, this could be quickly released as an nscd update until the real fix is done (which we're waiting for since when? two years?). The required patch would only need to do the following (in pseudo-code): /* signal handler to kill spawned nscd child */ signal(SIGTERM, { kill(child_pid); } ); /* core loop to (re)spawn nscd child */ for (;;) { child_pid = fork(); if (child_pid == 0) { nscd_main(); /* run nscd main() */ } else { wait(); /* wait for nscd child to exit/die */ log("restarting nscd child"); } } Would that be too difficult? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User walter.haidinger@gmx.at added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c59 --- Comment #59 from Walter Haidinger <walter.haidinger@gmx.at> 2008-12-08 06:56:21 MST --- Then add a sleep() to wait a couple of seconds after each wait() to throttle respawning. This should be usually good practice in watchdog wrappers anyways, so I left it out. I said it's only pseudo-code. Moreover, logging will make you notice the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User x_pedro_x@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c61 --- Comment #61 from Pedro Oliveira <x_pedro_x@hotmail.com> 2008-12-09 06:00:08 MST --- Sorry, I forgot the second scrip to make the previous one start automatically from RC. Just create this executable file: /etc/init.d/nscd_check #!/bin/sh ### BEGIN INIT INFO # Provides: nscd_check # Required-Start: nscd # Should-Start: # Required-Stop: # Should-Stop: # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Short-Description: check for nscd # Description: check if nscd is running and restarts it if not ### END INIT INFO # /etc/rc.status # Reset status of this service rc_reset case "$1" in start) echo -n "Starting nscd_check" nohup /sbin/nscd_check >> /var/log/messages & rc_status -v ;; stop) echo -n "Shutting down nscd_check" pkill nscd_check rc_status -v ;; restart) $0 stop $0 start rc_status ;; *) echo "Usage: $0 {start|stop}" exit 1 ;; esac rc_exit ##################################### after this just type: insserv nscd_check hope it helps. ---------------------------------------------------------------------------------------------------------- Pedro Oliveira IT Consultant Email: pmsoliveira@gmail.com URL: http://pedro.linux-geex.com Telefone: +351 96 5867227 ---------------------------------------------------------------------------------------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c63 --- Comment #63 from Jon Nelson <jnelson-suse@jamponi.net> 2008-12-29 10:03:38 MST --- nscd remains crashy for me, too (opensuse 11.1) /me back to using unscd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User R.Vickers@cs.rhul.ac.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c65 --- Comment #65 from Bob Vickers <R.Vickers@cs.rhul.ac.uk> 2009-01-05 06:51:18 MST --- nscd still crashes every hour or so after updating to nscd-2.8-14.2 on SuSE 11.0. I will reinstate unscd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c67 Petr Baudis <pbaudis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Basesystem Product|openSUSE 11.0 |openSUSE 11.1 --- Comment #67 from Petr Baudis <pbaudis@novell.com> 2009-01-05 09:55:17 MST --- Egbert König: I plan to package unscd nicely in buildservice in the future, I'm just not sure when will I get to it. To clarify, there are two bugs: bug 387202 against 11.0 and bug 446233 against 11.1. Since nscd is basically the same in 11.0 and 11.1 by now and I will continue to keep them in sync, I'm going to mark 446233 dupe of this one and bump this one to 11.1; further nscd updates will be released for both 11.0 and 11.1. Both of these bugs are in fact many different bugs in nscd, (un)fortunately the unfixed ones trigger only rarely so they aren't as easy to debug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c69 --- Comment #69 from Jon Nelson <jnelson-suse@jamponi.net> 2009-01-05 10:24:45 MST --- If anybody cares, I *have* packaged it (although the packaging needs some work) by using bits from the nscd package. home:jnelson-suse if you like. I *have* seen unscd crash, but not the latest version (0.36), which has been very slightly patched to unlink the pidfile and sockets. I actively solicit improvements. I'M NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User R.Vickers@cs.rhul.ac.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c71 --- Comment #71 from Bob Vickers <R.Vickers@cs.rhul.ac.uk> 2009-01-06 04:51:45 MST --- (In reply to comment #66 from Petr Baudis)

If nscd still crashes for you, please:

(i) Set persistent to 0 for all databases in your /etc/nscd.conf (ii) /etc/init.d/nscd stop and run ulimit -c unlimited; nscd -d (iii) When nscd crashes, please post a core here, compress it if it is larger than 1M or so. (iv) Also post your /etc/nsswitch.conf with the core.

Without this information, I cannot fix any crashes; nscd on 11.0 crashed only once for me so far after this fix, and I don't have quite enough data to debug it yet, it seems.

Thanks!

I managed to get another crash, and will attach the requested info. nscd is version 2.8-14.2, running on SuSE 11.0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User syseng@adnovum.ch added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c73 --- Comment #73 from Bernd Nies <syseng@adnovum.ch> 2009-01-07 02:57:20 MST --- Hi, Some good news while everybody is complaining: I installed all Suse 11.0 updates with "zypper update" and rebooted system two days ago and since then nscd keeps running. Before that it crashed every few hours and was restarted with my watchdog daemon. adnws001:~ # rpm -qa | egrep 'nscd|glibc' libnscd-2.0.2-81.1 nscd-2.8-14.2 glibc-2.8-14.2 glibc-locale-2.8-14.2 glibc-devel-2.8-14.2 glibc-info-2.8-14.2 adnws001:~ # uname -a Linux adnws001 2.6.25.18-0.2-pae #1 SMP 2008-10-21 16:30:26 +0200 i686 i686 i386 GNU/Linux Thanks a lot! Bye, Bernd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c75 Petr Baudis <pbaudis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz@novell.com --- Comment #75 from Petr Baudis <pbaudis@novell.com> 2009-01-20 17:35:02 MST --- *** Bug 467393 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=467393 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c77 --- Comment #77 from Petr Baudis <pbaudis@novell.com> 2009-01-21 15:57:13 MST --- Actually, I have just prepared a new round of nscd updates for 11.0 and 11.1, at http://www.suse.de/~pbaudis/bug-387202-2/ I'm sorry to those who I told before 11.1 and 11.0 nscd is identical, it turns out that the 11.1 glibc update I prepared last did not actually make it to 11.1. :-( So 11.0 should actually have much more stable nscd than 11.1 now. I will try to trigger another round of updates now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c81 --- Comment #81 from Carlos Robinson <robin.listas@telefonica.net> 2009-01-23 17:54:26 MST --- Yet another watchdog. root's crontab entry: -0,*/5 * * * 1-7 /root/bin/watchdog_nscd > /dev/null script: #!/bin/bash # watchdog para reiniciar el servicio nscd # idea del case en "307:rc" /usr/sbin/rcnscd status start; status=$? echo "Status= "$status case $status in [1-47]) echo "failed" /bin/logger -p user.warn -t watchdog \ "nscd is not running, restarting. -- Bugzilla 387202; "\ "see root's crontab to disable this wd" /usr/sbin/rcnscd restart ;; [56]) echo "skipped" ;; 0|*) echo "Nothing to do" ;; esac I believe you should create some kind of watchdog and push it via YOU to systems, till this problem is really solved. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User hpj@urpla.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c83 --- Comment #83 from Hans-Peter Jansen <hpj@urpla.net> 2009-01-25 14:38:00 MST --- Petr, for what it worth, since I installed http://www.suse.de/~pbaudis/bug-387202-2/ nscd didn't crashed. A yast compatible repo structure for this dir would ease testing greatly, though. (Well, I use createrepo internally..). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User swamp@suse.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c85 Swamp Script User <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:11.0:21210 |maint:released:11.0:21210 |maint:running:22192 |maint:running:22192 | |maint:released:11.0:22204 --- Comment #85 from Swamp Script User <swamp@suse.com> 2009-02-02 04:16:48 MST --- Update released for: nscd Products: openSUSE 11.0 (i386, ppc, x86_64) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c87 Petr Baudis <pbaudis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |robin.listas@telefonica.net --- Comment #87 from Petr Baudis <pbaudis@novell.com> 2009-02-03 12:14:00 MST --- Carlos, can you please follow the reporting guidelines I outlined in comment 66? Thank you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User bernet@physik.unizh.ch added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c89 Roland Bernet <bernet@physik.unizh.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernet@physik.unizh.ch --- Comment #89 from Roland Bernet <bernet@physik.unizh.ch> 2009-02-03 12:52:59 MST --- Hi Petr, Tried several times with ulimit -c unlimited; nscd -d and nscd does crash, but I never get a core dump ... Tried with a small script dividing by 0 and it writes a core. Any ideas how to get a core dump of a nscd crash? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c91 --- Comment #91 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-03 19:01:35 MST --- (In reply to comment #90)

Roland, Carlos please keep the ulimit -c unlimited; nscd -d running in a terminal, and be sure, that rcnscd is not running.

Well, I have done just that, but I still need clarification on "persistent" configuration, as per #88 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c93 --- Comment #93 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-03 20:53:21 MST --- I forgot: cer@nimrodel:~> cat /etc/nsswitch.conf | egrep -v "^[[:space:]]*$|^#" passwd: compat group: compat hosts: files mdns4_minimal [NOTFOUND=return] dns networks: files dns services: files protocols: files rpc: files ethers: files netmasks: files netgroup: files nis publickey: files bootparams: files automount: files nis aliases: files cer@nimrodel:~> And to avoid confusions, I'm on 11.0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c95 --- Comment #95 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-04 16:54:25 MST --- One more: 15414: handle_request: request received (Version = 2) from PID 17943 15414: GETFDGR 15414: provide access to FD 6, for group 15414: remove GETPWBYUID entry "1000" 15414: remove GETPWBYNAME entry "cer" 15414: handle_request: request received (Version = 2) from PID 7657 15414: GETAI (www.os-translation.com.ar) 15414: remove GETPWBYNAME entry "lp" 15414: remove GETPWBYUID entry "4" nscd: mem.c:368: gc: Assertion `off_allocend <= db->head->first_free' failed. Aborted Another: 21408: GETFDPW 21408: provide access to FD 4, for passwd 21408: handle_request: request received (Version = 2) from PID 1113 21408: GETFDPW 21408: provide access to FD 4, for passwd 21408: remove GETPWBYUID entry "101" 21408: remove GETPWBYNAME entry "messagebus" nscd: mem.c:368: gc: Assertion `off_allocend <= db->head->first_free' failed. Aborted -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User hpj@urpla.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c97 --- Comment #97 from Hans-Peter Jansen <hpj@urpla.net> 2009-02-05 05:28:09 MST ---

Well, as I see no comments on how to produce that core file, and it keeps crashing, I'm restarting the "normal" service with automatic watchdog restarting the service, instead of "nscd -d" in a terminal. I will not comment further unless I get feedback to the contrary, I see no point.

You truely have a point here, Carlos. FWIW, your crashes nicely sum up, what I see very sporadic here. Petr, I really wonder, why you don't provide the nscd debug packages (see #77). Otherwise, similar to Carlos, I see no point in running nscd via gdb... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User swamp@suse.com added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c99 Swamp Script User <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:11.0:21210 |maint:released:11.0:21210 |maint:running:22192 |maint:running:22192 |maint:released:11.0:22204 |maint:released:11.0:22204 | |maint:released:11.1:22237 --- Comment #99 from Swamp Script User <swamp@suse.com> 2009-02-05 07:44:46 MST --- Update released for: glibc, glibc-debuginfo, glibc-debugsource, glibc-devel, glibc-html, glibc-i18ndata, glibc-info, glibc-locale, glibc-obsolete, glibc-profile, nscd Products: openSUSE 11.1 (debug, i586, i686, ppc, ppc64, x86_64) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c100 --- Comment #100 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-05 07:58:42 MST --- (In reply to comment #98)

The debuginfo packages are right there where Petr said in comment #77. Maybe you are confused that there's no nscd-debug{info,source}? That's because debug packages don't exist for subpacks (and nscd is one of glibc), you need to install glibc-debuginfo (-debugsource).

Well, if you want me to install something in order to produce the coredump, tell me what exactly do I install.

Also, Carlos: you didn't yet follow the guidelines of comment #66. You still use persistent databases. Yes, the comment talks about setting it to "0". Of course instead you should use "no" for all databases you have in nscd.conf. See nscd.conf(5).

No, I didn't, I said in #88 and #91 that I needed clarification. I still do. Do you mean I should use: persistent whatever no

But indeed, more logs are not necessary I think, we see the assertions that cause nscd to exit. core file would be a bit more usefull. They aren't placed into the current pwd, but into the working dir of nscd, which usually is '/' (nscd chdir's into that one as daemon). You probably have some lying around there.

One of the crashes was not an assertion but a segfault. No, there is no core on /. I can run an "updatedb; locate corewhatever", but I need to know the exact name to search for, because it yields up of 5713 entries. Or alternatively, an exact "find" command to find it. As far as I can see, there is no core in: / /tmp /var/run/nscd /root/Bugzilla/Bug_387202 <-- pwd where I run "nscd -d" /root /home/cer Note: the "nscd -d" command runs on an xterm where I did "su -" to root, in order to keep an eye on it. The xterm is under gnome. I remember some mention years ago of X blocking coredumps. But somebody here said he managed to produce coredumps with a code dividing by zero, so it must be nscd which impedes them :-? Suggestion: search for all assertions in the code and replace/add logger calls. In my programming days, an assertion was the last resource to use, and never in production code. It was used instead of proper code to find an unexpected situation, never as error handling code. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User bernet@physik.unizh.ch added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c102 --- Comment #102 from Roland Bernet <bernet@physik.unizh.ch> 2009-02-06 01:32:05 MST --- Created an attachment (id=270688) --> (https://bugzilla.novell.com/attachment.cgi?id=270688) nscd backtrace nscd crashed again on my openSUSE 11.0 with nscd-2.8-14.4. Still no core dump, but this time a backtrace: 23851: provide access to FD 6, for group 23851: Reloading "20915" in group cache! *** glibc detected *** nscd: corrupted double-linked list: 0xb7f8d6e0 *** ======= Backtrace: ========= /lib/libc.so.6[0xb7de3fc4] /lib/libc.so.6[0xb7de4264] . . full output in the attached tar.gz file. It also includes my /etc/nscd.conf and /etc/nsswitch.conf files. Hope it helps ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User hpj@urpla.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c104 --- Comment #104 from Hans-Peter Jansen <hpj@urpla.net> 2009-02-06 08:28:35 MST --- Michael, not here, unfortunately: xrated:/# export LANG=C xrated:/# cat /etc/SuSE-release openSUSE 11.1 (i586) VERSION = 11.1 xrated:/# ulimit -c unlimited xrated:/# nscd -d & [1] 8139 xrated:/# kill -SEGV $! xrated:/# pwd; ls -l core* / ls: cannot access core*: No such file or directory [1]+ Segmentation fault nscd -d xrated:/# nscd xrated:/# pidof nscd 8206 xrated:/# kill -SEGV $(pidof nscd) xrated:/# ls -l core* ls: cannot access core*: No such file or directory xrated:/# uname -a Linux xrated 2.6.27.7-9-pae #1 SMP 2008-12-04 18:10:04 +0100 i686 athlon i386 GNU/Linux Do you remember any further details, which may prevent core dumping? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User hpj@urpla.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c106 --- Comment #106 from Hans-Peter Jansen <hpj@urpla.net> 2009-02-06 08:37:54 MST --- No. xrated:/# /sbin/sysctl -a | grep kernel.core kernel.core_uses_pid = 0 kernel.core_pattern = core -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c108 --- Comment #108 from Jon Nelson <jnelson-suse@jamponi.net> 2009-02-06 09:40:48 MST --- apparmor may be getting in the way here, too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User bernet@physik.unizh.ch added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c110 --- Comment #110 from Roland Bernet <bernet@physik.unizh.ch> 2009-02-10 03:34:29 MST --- Created an attachment (id=271484) --> (https://bugzilla.novell.com/attachment.cgi?id=271484) nscd core, nscd.conf, nsswitch.conf nscd core dump from a openSUSE 11.0 system. I have in addition added to the tar file /etc/nscd.conf, /etc/nsswitch.conf and the standard output. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User harbaugh@ncifcrf.gov added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c114 Toni Harbaugh-Blackford <harbaugh@ncifcrf.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |harbaugh@ncifcrf.gov --- Comment #114 from Toni Harbaugh-Blackford <harbaugh@ncifcrf.gov> 2009-02-27 04:59:49 MST --- This bug is marked NEEDINFO, but what info is needed? I've lost track. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c116 --- Comment #116 from Carlos Robinson <robin.listas@telefonica.net> 2009-03-24 09:04:41 MST --- (In reply to comment #115)

Removing bogus NEEDINFO; there are some new crashes to look at, but I'm decreasing priority and severity since they seem to happen much more rarely.

It crashes several times per day here - see some of my last watchdog entries - I have seen it crash four times in an hour: Mar 21 03:35:02 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 21 06:45:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 21 14:20:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 21 16:40:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 21 17:55:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 21 22:55:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 22 04:45:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 22 06:40:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 22 12:45:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 22 13:20:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 22 14:45:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 22 17:05:02 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 22 20:45:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 22 22:45:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 23 00:05:02 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 23 03:20:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 23 03:25:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 23 03:30:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 23 03:35:02 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 23 03:45:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 23 05:45:02 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 23 13:50:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 23 23:05:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd Mar 24 02:20:01 nimrodel watchdog: nscd is not running, restarting. -- Bugzilla 387202; see root's crontab to disable this wd You should clear all asserts from the C code: they are not logged to syslog, only to console. Not all crashes are segfaults - see the kernel log for the same period: Mar 21 03:34:27 nimrodel kernel: nscd[3461]: segfault at bffe0178 ip b7e8e32e sp afe1d034 error 6 in libc-2.8.so[b7e20000+13d000] Mar 21 22:51:12 nimrodel kernel: nscd[19438]: segfault at b8000012 ip b7f66825 sp addbee6c error 4 in nscd[b7f56000+1c000] Mar 22 06:37:28 nimrodel kernel: nscd[31545]: segfault at bfffe44c ip b7fe4822 sp ade3ceec error 4 in nscd[b7fd4000+1c000] Mar 22 20:41:34 nimrodel kernel: nscd[10540]: segfault at bfff66bc ip b80bc825 sp adf14f5c error 4 in nscd[b80ac000+1c000] Mar 23 03:19:59 nimrodel kernel: nscd[17683]: segfault at fff1518c ip b7e42450 sp ade070b8 error 4 in libc-2.8.so[b7dd5000+13d000] cer@nimrodel:~> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=387202 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c118 --- Comment #118 from Carlos Robinson <robin.listas@telefonica.net> 2009-03-25 17:16:06 MST --- Of course. Clearing an assert doesn't mean comment it out, just handle the error condition cleanly. Once an assert triggers, it means that a situation thought impossible by the programmer has in fact happened, and thus, the code has to be changed to avoid that situation happening. On the other hand, an assert in such a daemon just kills the daemon silently, without any message to the user/admin. An assert is intended as a message from the dead to the creator of the program, so that the creator can reprogram the cylon. This is not happening. Those asserts are useless. Instead the assert message should be sent to syslog with "warn" or "critical" level, and then the program halted - after logging the situation -. At best, the assert could be used to restart or reinit the daemon (the idea of dividing nscd into a parent and child is not so bad). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.