Package: nslcd Followup-For: Bug #759544 Hi,
I was hit by this issue on a server today as well (current jessie, systemd, physical hardware, /e/n/i, no network-manager). I tried to reproduce it booting the system about 30 times, but failed to do so. This is the log when it failed Jan 3 22:20:22 pgdb2 ifup[519]: Sending network state change signal to nslcd...done. Jan 3 22:20:22 pgdb2 nslcd[646]: Starting LDAP connection daemon: nslcdnslcd: unable to daemonize: Success Jan 3 22:20:22 pgdb2 nslcd[646]: failed! and this is the log when it works. Jan 3 23:07:28 pgdb2 nslcd[844]: version 0.9.4 starting Jan 3 23:07:28 pgdb2 nslcd[844]: accepting connections Jan 3 23:07:28 pgdb2 nslcd[643]: Starting LDAP connection daemon: nslcd. Jan 3 23:07:28 pgdb2 ifup[542]: Sending network state change signal to nslcd...done. Jan 3 23:07:28 pgdb2 nslcd[844]: caught signal SIGUSR1 (10), refresh retries I suspect that this indeed a race between nslcd starting up and /etc/network/if-up.d/nslcd sending SIGUSR1 to the process. This sounds like http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=1d3b19b1ecd3b10f36e8925e8a752a28e3e74b56 could help here. Unfortunately I wasn't able to reproduce the problem so testing the patch won't help. Best Regards, Bernhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
