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
We have a separate daemon that renews all credentials that are in use. This
requires a pam module to register credentials for renewal. You’re welcome to
use it. It’s part of our kerberos tools at
https://github.com/clhedrick/kerberos.
> On Aug 14, 2019, at 10:33 AM, Goetz, Patrick G wrote:
>
We run stock sssd on a number of Ubuntu 18.04 servers, and I have not
seen this problem. Also, I haven't done anything to the out of box DNS
configuration. The issue we run in to regularly is that Kerberos
tickets are not renewed and the machine falls out of the domain, but we
now think this
yes, it’s the same thing. The workaround to add a dependency on network up or
systemd-resolved.service work (either one).
A static /etc/resolv.conf also works, but I’m going to use the extra startup
dependency. Probably systemd-resolved.
We didn’t have the problem on a system with static
Hello,
On Tue, Aug 13, 2019 at 1:01 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.
Sounds like https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350 ?
