Hello, This seems to be the same issue related to Fedora bug but I've no prelink or readahead packages installed on my nodes. libgcrypt11 is at version 1.4.5-2 on my configuration.
Tina -- rakotoarivelo_t...@yahoo.fr ________________________________ De : Arthur de Jong <adej...@debian.org> À : rakotoarivelo tina <rakotoarivelo_t...@yahoo.fr>; 643...@bugs.debian.org Cc : libgcryp...@packages.debian.org Envoyé le : Dimanche 2 Octobre 2011 17h24 Objet : Re: Bug#643948: nslcd: daemon hang during machine boot process reassign 643948 libgcrypt11 1.5.0-3 thanks On Sat, 2011-10-01 at 01:33 +0100, rakotoarivelo tina wrote: > *** Please type your report below this line *** > nslcd hang during machine boot process with the following errors: > > Sep 30 18:50:14 node-30 nslcd[1797]: version 0.7.13 starting > Sep 30 18:50:14 node-30 nslcd[1797]: accepting connections > Sep 30 18:50:14 node-30 /usr/sbin/cron[1852]: (CRON) INFO (pidfile fd = 3) > Sep 30 18:50:14 node-30 /usr/sbin/cron[1853]: (CRON) STARTUP (fork ok) > Sep 30 18:50:14 node-30 /usr/sbin/cron[1853]: (CRON) INFO (Running @reboot > jobs) > Sep 30 18:50:15 node-30 postfix/master[1958]: daemon started -- version > 2.7.1, configuration /etc/postfix > Sep 30 18:50:15 node-30 nslcd[1797]: Libgcrypt notice: state transition > Power-On => Fatal-Error > Sep 30 18:50:15 node-30 nslcd[1797]: Libgcrypt error: fatal error in file > visibility.c, line 1250, function gcry_create_nonce: called in > non-operational state > Sep 30 18:50:15 node-30 nslcd[1797]: Libgcrypt terminated the application > > > This is a random issue. > Sometimes nslcd is started during boot process without problem. I believe this is an issue in libgcrypt11, not in nslcd. nslcd doesn't do any calls to libgcrypt, it uses libldap-2.4-2 to do LDAP queries and when using ldaps:// or StartTLS it uses and SSL library. rakotoarivelo tina, do you use prelinking (do you have any of the readahead packages installed)? There is a Fedora bug similar to this one related to readahead (https://bugzilla.redhat.com/506796). Can you also indicate which version of libgcrypt11 you have installed? Btw, it seems to be pretty bad for a library to abort the whole application when it's state is inconsistent. -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong --
