Similar to dhcp in Bug 16642, nslcd.service (from nss-pam-ldapd) uses After=network.target, but for some services in Mageia 5, this no longer works correctly, and you have to set it to After=network-online.target, otherwise the service tries to start before the network is up and fails. For users upgrading from Mageia 4 to Mageia 5, this is a non-obvious and unpleasant surprise, so let's fix this now. Advisory: ----------------------------------------- The nslcd service in nss-pam-ldapd was not correctly waiting for the network to be up before attempting to start, causing it to fail to start at boot time. ----------------------------------------- Updated packages in core/updates_testing: ----------------------------------------- nss-pam-ldapd-0.8.14-3.1.mga5 from nss-pam-ldapd-0.8.14-3.1.mga5 Reproducible: Steps to Reproduce:
I can verify that the updated service file fixes the issue on Mageia 5 i586.
Whiteboard: (none) => MGA5-32-OK
Testing complete mga5 64 Verified with rpmdiff on madb the only changes in the srpm are bumping sebrel and.. -After=syslog.target network.target +After=syslog.target network-online.target named.service slapd.service Ensured the package updates cleanly.
Keywords: (none) => validated_updateWhiteboard: MGA5-32-OK => MGA5-32-OK mga5-64-okCC: (none) => sysadmin-bugs
Advisory uploaded.
Whiteboard: MGA5-32-OK mga5-64-ok => advisory MGA5-32-OK mga5-64-ok
Sorry, forgot to svn ci. Done now :)
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0130.html
Status: NEW => RESOLVEDResolution: (none) => FIXED