On 8/13/19 6:00 PM, Charles Hedrick wrote:
On our Ubuntu 18.04 servers, sssd won’t start. Logging shows that it can’t find
any DNS servers. Restarting sssd fixes it.
/etc/resolv.conf is a symlink to ../run/systemd/resolve/stub-resolv.conf
If I replace that with a hardcoded resolv.conf with the right name server, sssd
comes up. Network Manager replaces the file with a different one pointing to
nameserver 127.0.0.53, but after another reboot with that file it still works.
This happens on 4 identical servers, but not on a VM with the same OS. I assume
there’s a timing issue of some sort.
I think this PR might help here: https://github.com/SSSD/sssd/pull/864
SSSD did not watch resolv.conf symlinks for changes so if the original
file did not contains correct DNS server SSSD wouldn't be able to pick
up the new one after resolv.conf is updated.
_______________________________________________
sssd-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/[email protected]
