Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#33672 - [nss_ldap] systemd incorrectly handles nss_ldap (based on nsswitch.conf) -> freeze on bootup
Attached to Project:
Arch Linux
Opened by Marek Kozlowski (guayasil) - Friday, 01 February 2013, 19:21 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 22 May 2013, 15:35 GMT
Opened by Marek Kozlowski (guayasil) - Friday, 01 February 2013, 19:21 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 22 May 2013, 15:35 GMT
|
DetailsI have nss_ldap installed. With initscripts everything works fine. With systemd a 5 min. freeze occurs on system startup. I found that the reason is caused by the entries in /etc/nsswitch.conf :
------------------ passwd: files ldap group: files ldap shadow: files ldap ------------------ For absolutely unknown reason systemd tries to contact nss_ldap server at the beginning of system initialization (before the network, that is netcfg/ethernet-dhcp is fully functional) and subsequent timeouts occur. If I remove the `ldap' entries system boots up immediately. Unfortunately I need both: the fully functional system and nss_ldap (unfortunately: critical to my system). |
This task depends upon
Closed by Dave Reisner (falconindy)
Wednesday, 22 May 2013, 15:35 GMT
Reason for closing: Upstream
Additional comments about closing: Well known bug, probably won't be fixed upstream. Use nss-pam-ldapd instead.
Wednesday, 22 May 2013, 15:35 GMT
Reason for closing: Upstream
Additional comments about closing: Well known bug, probably won't be fixed upstream. Use nss-pam-ldapd instead.
systemd isn't really doing anything wrong here, it's just a problem of ordering.
BTW: is there any way to trace / analyze what / when exactly runs it? If have a very limited knowledge on analyzing systemd..
Feb 01 21:32:59 localhost systemd-modules-load[180]: Inserted module 'nfs'
Does it help?
http://forums.opensuse.org/english/get-technical-help-here/network-internet/474413-nss_ldap-attempts-reach-ldap-before-rcnetwork-starts.html
Seems to be a well known bug. A critical one to people using nss_ldap and systemd. The solution for opensuse it no to use systemd. Arch users don't have such option :-(