Hi see https://unix.stackexchange.com/questions/210604/how-to-write-a-systemd-service-unit-file-so-it-waits-until-a-specific-interface maybe that solves it.
Am 22.11.18 um 12:32 schrieb Sumit Bose: > On Thu, Nov 22, 2018 at 12:15:45PM +0100, Harald Dunkel wrote: >> Hi folks, >> >> sssd 1.16.3-1 (rebuilt for Debian 9), systemd >> >> At boot time sssd_nss fails to initialize. systemctl status sssd >> shows >> >> root@srvl061:~# systemctl status sssd >> * sssd.service - System Security Services Daemon >> Loaded: loaded (/lib/systemd/system/sssd.service; enabled; vendor preset: >> enabled) >> Active: active (running) since Thu 2018-11-22 11:57:30 CET; 46s ago >> Main PID: 1312 (sssd) >> Tasks: 5 (limit: 7372) >> CGroup: /system.slice/sssd.service >> |-1312 /usr/sbin/sssd -i --logger=files >> |-1345 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain >> example.com --uid 0 --gid 0 --logger=files >> |-1533 /usr/lib/x86_64-linux-gnu/sssd/sssd_nss --uid 0 --gid 0 >> --logger=files >> |-1534 /usr/lib/x86_64-linux-gnu/sssd/sssd_pam --uid 0 --gid 0 >> --logger=files >> `-1535 /usr/lib/x86_64-linux-gnu/sssd/sssd_pac --uid 0 --gid 0 >> --logger=files >> >> Nov 22 11:57:25 srvl061.ac.example.com systemd[1]: Starting System Security >> Services Daemon... >> Nov 22 11:57:25 srvl061.ac.example.com sssd[1312]: Starting up >> Nov 22 11:57:25 srvl061.ac.example.com sssd[be[1345]: Starting up >> Nov 22 11:57:30 srvl061.ac.example.com sssd[1533]: Starting up >> Nov 22 11:57:30 srvl061.ac.example.com sssd[1534]: Starting up >> Nov 22 11:57:30 srvl061.ac.example.com sssd[1535]: Starting up >> Nov 22 11:57:30 srvl061.ac.example.com systemd[1]: Started System Security >> Services Daemon. >> Nov 22 11:57:45 srvl061.ac.example.com sssd[be[1345]: Backend is offline >> >> >> Apparently this is a problem of resolvconf generating /etc/\ >> resolv.conf at boot time. If I replace it by a static file, then >> the problem is gone. >> >> Question is, how can I tell systemd to wait for resolv.conf? >> Is there some timeout in the backend I could adjust? Does it >> wait for the network at all? >> >> >> Every helpful comment is highly appreciated > Does > https://stackoverflow.com/questions/32873571/debian-systemd-service-starts-before-network-is-ready? > > As an alternative it looks like systemd has something similar to > resolvconf https://github.com/systemd/systemd/issues/7202 maybe this is > something which works for you? > > As another alternative you can add an ExecStartPre script to > sssd.service which waits until /etc/resolv.conf exists. > > HTH > > bye, > Sumit > >> Regards >> Harri >> _______________________________________________ >> sssd-users mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedorahosted.org/archives/list/[email protected] > _______________________________________________ > sssd-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/[email protected]
pEpkey.asc
Description: application/pgp-keys
_______________________________________________ sssd-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected]
