Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#759544: nslcd: fails 'sometimes' to start at boot (systemd?)
314 views
Skip to first unread message
Andreas B. Mundt
Aug 28, 2014, 6:40:01 AM8/28/14
to
Package: nslcd
Version: 0.9.4-2
Severity: normal
Dear Arthur,
another issue I just observed: nslcd 'sometimes', perhaps 1 of 5 reboots,
fails to start/run at boot. systemctl status tells me in these cases:
root@workstation00:~# systemctl status nslcd -l
nslcd.service - LSB: LDAP connection daemon
Loaded: loaded (/etc/init.d/nslcd)
Active: active (exited) since Thu 2014-08-28 12:08:13 CEST; 6min ago
Process: 439 ExecStart=/etc/init.d/nslcd start (code=exited, status=0/SUCCESS)
Aug 28 12:08:13 workstation00 systemd[1]: Starting LSB: LDAP connection daemon...
Aug 28 12:08:13 workstation00 nslcd[535]: version 0.9.4 starting
Aug 28 12:08:13 workstation00 nslcd[439]: Starting LDAP connection daemon: nslcdnslcd: unable to daemonize: Success
Aug 28 12:08:13 workstation00 nslcd[439]: failed!
Aug 28 12:08:13 workstation00 systemd[1]: Started LSB: LDAP connection daemon.
From journalctl:
Aug 28 12:08:13 workstation00 nslcd[535]: version 0.9.4 starting
Aug 28 12:08:13 workstation00 dbus[449]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service'
Aug 28 12:08:13 workstation00 systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks...
Aug 28 12:08:13 workstation00 systemd[1]: Stopping LSB: Start NTP daemon...
Aug 28 12:08:13 workstation00 polkitd[537]: started daemon version 0.105 using authority implementation `local' version `0.105'
Aug 28 12:08:13 workstation00 dbus[449]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Aug 28 12:08:13 workstation00 systemd[1]: Started Authenticate and Authorize Users to Run Privileged Tasks.
Aug 28 12:08:13 workstation00 accounts-daemon[461]: started daemon version 0.6.37
Aug 28 12:08:13 workstation00 systemd[1]: Started Accounts Service.
Aug 28 12:08:13 workstation00 ntpd[502]: ntpd exiting on signal 15
Aug 28 12:08:13 workstation00 ntp[539]: Stopping NTP server: ntpd.
Aug 28 12:08:13 workstation00 systemd[1]: Starting LSB: Start NTP daemon...
Aug 28 12:08:13 workstation00 ntpd[556]: ntpd 4.2...@1.2349-o Mon May 20 14:24:35 UTC 2013 (1)
Aug 28 12:08:13 workstation00 ntp[550]: Starting NTP server: ntpd.
Aug 28 12:08:13 workstation00 systemd[1]: Started LSB: Start NTP daemon.
Aug 28 12:08:13 workstation00 ifup[245]: Restarting ntp (via systemctl): ntp.service.
Aug 28 12:08:13 workstation00 ntpd[557]: proto: precision = 0.119 usec
Aug 28 12:08:13 workstation00 ntpd[557]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Aug 28 12:08:13 workstation00 ntpd[557]: Listen and drop on 1 v6wildcard :: UDP 123
Aug 28 12:08:13 workstation00 ntpd[557]: Listen normally on 2 lo 127.0.0.1 UDP 123
Aug 28 12:08:13 workstation00 ntpd[557]: Listen normally on 3 eth0 10.0.0.50 UDP 123
Aug 28 12:08:13 workstation00 ntpd[557]: Listen normally on 4 lo ::1 UDP 123
Aug 28 12:08:13 workstation00 ntpd[557]: peers refreshed
Aug 28 12:08:13 workstation00 ntpd[557]: Listening on routing socket on fd #21 for interface updates
Aug 28 12:08:13 workstation00 systemd[1]: Started Munin Node.
Aug 28 12:08:13 workstation00 kernel: intel8x0_measure_ac97_clock: measured 53158 usecs (4351 samples)
Aug 28 12:08:13 workstation00 kernel: intel8x0: measured clock 81850 rejected
Aug 28 12:08:13 workstation00 dhclient[261]: bound to 10.0.0.50 -- renewal in 18284 seconds.
Aug 28 12:08:13 workstation00 ifup[245]: bound to 10.0.0.50 -- renewal in 18284 seconds.
Aug 28 12:08:13 workstation00 ifup[245]: Sending network state change signal to nslcd...done.
Aug 28 12:08:13 workstation00 nslcd[439]: Starting LDAP connection daemon: nslcdnslcd: unable to daemonize: Success
Aug 28 12:08:13 workstation00 nslcd[439]: failed!
Aug 28 12:08:13 workstation00 systemd[1]: Started LSB: LDAP connection daemon.
Perhaps this is some race triggered by the switch so systemd?
Manually starting nslcd works fine.
Best regards,
Andi
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nslcd depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.53
ii libc6 2.19-9
ii libgssapi-krb5-2 1.12.1+dfsg-7
ii libldap-2.4-2 2.4.39-1.1+b1
Versions of packages nslcd recommends:
ii bind9-host [host] 1:9.9.5.dfsg-4
ii ldap-utils 2.4.39-1.1+b1
ii libnss-ldapd [libnss-ldap] 0.9.4-2
ii libpam-krb5 4.6-3
ii nscd 2.19-9
ii nslcd-utils 0.9.4-2
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Version: 0.9.4-2
Severity: normal
Dear Arthur,
another issue I just observed: nslcd 'sometimes', perhaps 1 of 5 reboots,
fails to start/run at boot. systemctl status tells me in these cases:
root@workstation00:~# systemctl status nslcd -l
nslcd.service - LSB: LDAP connection daemon
Loaded: loaded (/etc/init.d/nslcd)
Active: active (exited) since Thu 2014-08-28 12:08:13 CEST; 6min ago
Process: 439 ExecStart=/etc/init.d/nslcd start (code=exited, status=0/SUCCESS)
Aug 28 12:08:13 workstation00 systemd[1]: Starting LSB: LDAP connection daemon...
Aug 28 12:08:13 workstation00 nslcd[535]: version 0.9.4 starting
Aug 28 12:08:13 workstation00 nslcd[439]: Starting LDAP connection daemon: nslcdnslcd: unable to daemonize: Success
Aug 28 12:08:13 workstation00 nslcd[439]: failed!
Aug 28 12:08:13 workstation00 systemd[1]: Started LSB: LDAP connection daemon.
From journalctl:
Aug 28 12:08:13 workstation00 nslcd[535]: version 0.9.4 starting
Aug 28 12:08:13 workstation00 dbus[449]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service'
Aug 28 12:08:13 workstation00 systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks...
Aug 28 12:08:13 workstation00 systemd[1]: Stopping LSB: Start NTP daemon...
Aug 28 12:08:13 workstation00 polkitd[537]: started daemon version 0.105 using authority implementation `local' version `0.105'
Aug 28 12:08:13 workstation00 dbus[449]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Aug 28 12:08:13 workstation00 systemd[1]: Started Authenticate and Authorize Users to Run Privileged Tasks.
Aug 28 12:08:13 workstation00 accounts-daemon[461]: started daemon version 0.6.37
Aug 28 12:08:13 workstation00 systemd[1]: Started Accounts Service.
Aug 28 12:08:13 workstation00 ntpd[502]: ntpd exiting on signal 15
Aug 28 12:08:13 workstation00 ntp[539]: Stopping NTP server: ntpd.
Aug 28 12:08:13 workstation00 systemd[1]: Starting LSB: Start NTP daemon...
Aug 28 12:08:13 workstation00 ntpd[556]: ntpd 4.2...@1.2349-o Mon May 20 14:24:35 UTC 2013 (1)
Aug 28 12:08:13 workstation00 ntp[550]: Starting NTP server: ntpd.
Aug 28 12:08:13 workstation00 systemd[1]: Started LSB: Start NTP daemon.
Aug 28 12:08:13 workstation00 ifup[245]: Restarting ntp (via systemctl): ntp.service.
Aug 28 12:08:13 workstation00 ntpd[557]: proto: precision = 0.119 usec
Aug 28 12:08:13 workstation00 ntpd[557]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Aug 28 12:08:13 workstation00 ntpd[557]: Listen and drop on 1 v6wildcard :: UDP 123
Aug 28 12:08:13 workstation00 ntpd[557]: Listen normally on 2 lo 127.0.0.1 UDP 123
Aug 28 12:08:13 workstation00 ntpd[557]: Listen normally on 3 eth0 10.0.0.50 UDP 123
Aug 28 12:08:13 workstation00 ntpd[557]: Listen normally on 4 lo ::1 UDP 123
Aug 28 12:08:13 workstation00 ntpd[557]: peers refreshed
Aug 28 12:08:13 workstation00 ntpd[557]: Listening on routing socket on fd #21 for interface updates
Aug 28 12:08:13 workstation00 systemd[1]: Started Munin Node.
Aug 28 12:08:13 workstation00 kernel: intel8x0_measure_ac97_clock: measured 53158 usecs (4351 samples)
Aug 28 12:08:13 workstation00 kernel: intel8x0: measured clock 81850 rejected
Aug 28 12:08:13 workstation00 dhclient[261]: bound to 10.0.0.50 -- renewal in 18284 seconds.
Aug 28 12:08:13 workstation00 ifup[245]: bound to 10.0.0.50 -- renewal in 18284 seconds.
Aug 28 12:08:13 workstation00 ifup[245]: Sending network state change signal to nslcd...done.
Aug 28 12:08:13 workstation00 nslcd[439]: Starting LDAP connection daemon: nslcdnslcd: unable to daemonize: Success
Aug 28 12:08:13 workstation00 nslcd[439]: failed!
Aug 28 12:08:13 workstation00 systemd[1]: Started LSB: LDAP connection daemon.
Perhaps this is some race triggered by the switch so systemd?
Manually starting nslcd works fine.
Best regards,
Andi
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nslcd depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.53
ii libc6 2.19-9
ii libgssapi-krb5-2 1.12.1+dfsg-7
ii libldap-2.4-2 2.4.39-1.1+b1
Versions of packages nslcd recommends:
ii bind9-host [host] 1:9.9.5.dfsg-4
ii ldap-utils 2.4.39-1.1+b1
ii libnss-ldapd [libnss-ldap] 0.9.4-2
ii libpam-krb5 4.6-3
ii nscd 2.19-9
ii nslcd-utils 0.9.4-2
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Arthur de Jong
Aug 28, 2014, 6:20:01 PM8/28/14
to
On Thu, 2014-08-28 at 12:34 +0200, Andreas B. Mundt wrote:
> another issue I just observed: nslcd 'sometimes', perhaps 1 of 5 reboots,
> fails to start/run at boot. systemctl status tells me in these cases:
>
> root@workstation00:~# systemctl status nslcd -l
> nslcd.service - LSB: LDAP connection daemon
> Loaded: loaded (/etc/init.d/nslcd)
> Active: active (exited) since Thu 2014-08-28 12:08:13 CEST; 6min ago
> Process: 439 ExecStart=/etc/init.d/nslcd start (code=exited, status=0/SUCCESS)
Is there anything in the logs?
> another issue I just observed: nslcd 'sometimes', perhaps 1 of 5 reboots,
> fails to start/run at boot. systemctl status tells me in these cases:
>
> root@workstation00:~# systemctl status nslcd -l
> nslcd.service - LSB: LDAP connection daemon
> Loaded: loaded (/etc/init.d/nslcd)
> Active: active (exited) since Thu 2014-08-28 12:08:13 CEST; 6min ago
> Process: 439 ExecStart=/etc/init.d/nslcd start (code=exited, status=0/SUCCESS)
There is a known issue in nslcd/ldap/gnutls:
https://bugs.debian.org/643948
https://bugs.launchpad.net/bugs/1029656
If this is the same issue, providing the information as described in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643948#61
is probably very helpful. Being able to get a stack trace from this
would be very useful.
--
-- arthur - ade...@debian.org - http://people.debian.org/~adejong --
Andreas B. Mundt
Aug 29, 2014, 11:30:02 AM8/29/14
to
Hi Arthur,
On Fri, Aug 29, 2014 at 12:09:17AM +0200, Arthur de Jong wrote:
> On Thu, 2014-08-28 at 12:34 +0200, Andreas B. Mundt wrote:
> > another issue I just observed: nslcd 'sometimes', perhaps 1 of 5 reboots,
> > fails to start/run at boot.
(date ; gdb -return-child-result -ex run -ex "thread apply all bt full" -ex "quit" --args ldapsearch -x -H ldap://ldap/ -b 'dc=intern' uid=admin mail ) < /dev/null >> /var/log/nslcd.ldapsearch.boot.log 2>&1 &
But this seems not to give any hints:
Fri Aug 29 17:04:29 CEST 2014
GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1
[...]
Reading symbols from ldapsearch...(no debugging symbols found)...done.
Starting program: /usr/bin/ldapsearch -x -H ldap://ldap/ -b dc=intern uid=admin mail
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
# extended LDIF
#
# LDAPv3
# base <dc=intern> with scope subtree
# filter: uid=admin
# requesting: mail
#
# admin, people, gosa, intern
dn: uid=admin,ou=people,ou=gosa,dc=intern
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
[Inferior 1 (process 557) exited normally]
where for this boot again 'systemctl status nslcd -l' shows:
nslcd.service - LSB: LDAP connection daemon
Loaded: loaded (/etc/init.d/nslcd)
Active: active (exited) since Fri 2014-08-29 17:04:29 CEST; 21s ago
Process: 455 ExecStart=/etc/init.d/nslcd start (code=exited, status=0/SUCCESS)
Aug 29 17:04:28 workstation00 systemd[1]: Starting LSB: LDAP connection daemon...
Aug 29 17:04:29 workstation00 nslcd[547]: version 0.9.4 starting
Aug 29 17:04:29 workstation00 nslcd[455]: Starting LDAP connection daemon: nslcdnslcd: unable to daemonize: Success
Aug 29 17:04:29 workstation00 nslcd[455]: failed!
Aug 29 17:04:29 workstation00 systemd[1]: Started LSB: LDAP connection daemon.
In the log:
Aug 29 17:04:29 workstation00 nslcd[547]: version 0.9.4 starting
Aug 29 17:04:29 workstation00 ifup[257]: Sending network state change signal to nslcd...done.
Aug 29 17:04:29 workstation00 nslcd[455]: Starting LDAP connection daemon: nslcdnslcd: unable to daemonize: Success
Aug 29 17:04:29 workstation00 nslcd[455]: failed!
Hm. Any other hints how to pin down the issue?
Best regards,
Andi
On Fri, Aug 29, 2014 at 12:09:17AM +0200, Arthur de Jong wrote:
> On Thu, 2014-08-28 at 12:34 +0200, Andreas B. Mundt wrote:
> > another issue I just observed: nslcd 'sometimes', perhaps 1 of 5 reboots,
> > fails to start/run at boot.
> Is there anything in the logs?
>
> There is a known issue in nslcd/ldap/gnutls:
> https://bugs.debian.org/643948
> https://bugs.launchpad.net/bugs/1029656
>
> If this is the same issue, providing the information as described in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643948#61
> is probably very helpful. Being able to get a stack trace from this
> would be very useful.
I added:
>
> There is a known issue in nslcd/ldap/gnutls:
> https://bugs.debian.org/643948
> https://bugs.launchpad.net/bugs/1029656
>
> If this is the same issue, providing the information as described in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643948#61
> is probably very helpful. Being able to get a stack trace from this
> would be very useful.
(date ; gdb -return-child-result -ex run -ex "thread apply all bt full" -ex "quit" --args ldapsearch -x -H ldap://ldap/ -b 'dc=intern' uid=admin mail ) < /dev/null >> /var/log/nslcd.ldapsearch.boot.log 2>&1 &
But this seems not to give any hints:
Fri Aug 29 17:04:29 CEST 2014
GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1
[...]
Reading symbols from ldapsearch...(no debugging symbols found)...done.
Starting program: /usr/bin/ldapsearch -x -H ldap://ldap/ -b dc=intern uid=admin mail
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
# extended LDIF
#
# LDAPv3
# base <dc=intern> with scope subtree
# filter: uid=admin
# requesting: mail
#
# admin, people, gosa, intern
dn: uid=admin,ou=people,ou=gosa,dc=intern
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
[Inferior 1 (process 557) exited normally]
where for this boot again 'systemctl status nslcd -l' shows:
nslcd.service - LSB: LDAP connection daemon
Loaded: loaded (/etc/init.d/nslcd)
Process: 455 ExecStart=/etc/init.d/nslcd start (code=exited, status=0/SUCCESS)
Aug 29 17:04:28 workstation00 systemd[1]: Starting LSB: LDAP connection daemon...
Aug 29 17:04:29 workstation00 nslcd[547]: version 0.9.4 starting
Aug 29 17:04:29 workstation00 nslcd[455]: Starting LDAP connection daemon: nslcdnslcd: unable to daemonize: Success
Aug 29 17:04:29 workstation00 nslcd[455]: failed!
Aug 29 17:04:29 workstation00 systemd[1]: Started LSB: LDAP connection daemon.
In the log:
Aug 29 17:04:29 workstation00 nslcd[547]: version 0.9.4 starting
Aug 29 17:04:29 workstation00 ifup[257]: Sending network state change signal to nslcd...done.
Aug 29 17:04:29 workstation00 nslcd[455]: Starting LDAP connection daemon: nslcdnslcd: unable to daemonize: Success
Aug 29 17:04:29 workstation00 nslcd[455]: failed!
Hm. Any other hints how to pin down the issue?
Best regards,
Andi
Arthur de Jong
Nov 10, 2014, 4:10:04 PM11/10/14
to
On Fri, 2014-08-29 at 17:22 +0200, Andreas B. Mundt wrote:
> Hm. Any other hints how to pin down the issue?
Sorry to not get back to you sooner. Can you try these patches:
> Hm. Any other hints how to pin down the issue?
http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=a726d291b0f6794abec0a0192cf2b2a742648e4a
http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=1d3b19b1ecd3b10f36e8925e8a752a28e3e74b56
Thanks,
Andreas B. Mundt
Nov 15, 2014, 4:30:03 PM11/15/14
to
Hi Arthur,
On Mon, Nov 10, 2014 at 10:07:26PM +0100, Arthur de Jong wrote:
> On Fri, 2014-08-29 at 17:22 +0200, Andreas B. Mundt wrote:
> Sorry to not get back to you sooner. Can you try these patches:
>
> http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=a726d291b0f6794abec0a0192cf2b2a742648e4a
> http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=1d3b19b1ecd3b10f36e8925e8a752a28e3e74b56
>
They do not fix the issue. However, 'systemctl status nslcd' gives:
● nslcd.service - LSB: LDAP connection daemon
Loaded: loaded (/etc/init.d/nslcd)
Active: active (exited) since Sat 2014-11-15 22:03:38 CET; 1min 23s ago
Process: 912 ExecStart=/etc/init.d/nslcd start (code=exited, status=0/SUCCESS)
Nov 15 22:03:33 guest03.intern nslcd[965]: version 0.9.4 starting
Nov 15 22:03:33 guest03.intern nslcd[965]: DEBUG: unlink() of /var/run/nslcd/socket failed (ignored): No such file or directory
Nov 15 22:03:38 guest03.intern nslcd[912]: Starting LDAP connection daemon: nslcdnslcd: wait_for_response(): read_response() returned 0 (expected 4)
Nov 15 22:03:38 guest03.intern nslcd[912]: nslcd: unable to daemonize: No data available
Nov 15 22:03:38 guest03.intern nslcd[912]: failed!
Nov 15 22:03:38 guest03.intern systemd[1]: Started LSB: LDAP connection daemon.
Perhaps this gives some hint ...
On Mon, Nov 10, 2014 at 10:07:26PM +0100, Arthur de Jong wrote:
> On Fri, 2014-08-29 at 17:22 +0200, Andreas B. Mundt wrote:
> Sorry to not get back to you sooner. Can you try these patches:
>
> http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=a726d291b0f6794abec0a0192cf2b2a742648e4a
> http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=1d3b19b1ecd3b10f36e8925e8a752a28e3e74b56
>
● nslcd.service - LSB: LDAP connection daemon
Loaded: loaded (/etc/init.d/nslcd)
Active: active (exited) since Sat 2014-11-15 22:03:38 CET; 1min 23s ago
Process: 912 ExecStart=/etc/init.d/nslcd start (code=exited, status=0/SUCCESS)
Nov 15 22:03:33 guest03.intern nslcd[965]: version 0.9.4 starting
Nov 15 22:03:33 guest03.intern nslcd[965]: DEBUG: unlink() of /var/run/nslcd/socket failed (ignored): No such file or directory
Nov 15 22:03:38 guest03.intern nslcd[912]: Starting LDAP connection daemon: nslcdnslcd: wait_for_response(): read_response() returned 0 (expected 4)
Nov 15 22:03:38 guest03.intern nslcd[912]: nslcd: unable to daemonize: No data available
Nov 15 22:03:38 guest03.intern nslcd[912]: failed!
Nov 15 22:03:38 guest03.intern systemd[1]: Started LSB: LDAP connection daemon.
Perhaps this gives some hint ...
0 new messages