• 1

autofs ignores sssd if it starts too slowly...


I've been trying the feature with a freshly installed fedora 17 (to have sssd answer autofs before it is actually started).

It works... until I enabled nss-mdns (I use this for my local network). Then autofs seems to start before sssd is ready and ignores its information (and all my ldap maps !).

Jun 3 16:44:19 black-cube automount[846]: setautomntent: lookup(sss): setautomntent: Connection refused

I tried adding an After = sssd.service in the systemd unit of autofs, but sssd is not ready by the time sssd is.

Edited at 2012-06-03 03:37 pm (UTC)

Re: autofs ignores sssd if it starts too slowly...

Right, the startup order might be a problem. In the traditional SysV scripts on RHEL6, we solved this by choosing the correct startup order.

I'm surprised that After=sssd.service didn't help, though. Maybe it's another case similar to upstream bug https://fedorahosted.org/sssd/ticket/1357 where SSSD reports it's up when it's really not, or, more precisely, only the main monitor SSSD process is up but none of the responders such as the autofs responder.

  • 1

Log in