Yup, it ended up being that and not an sssd issue per se. Disabling the apparmor profile for sssd worked a charm, albeit a temporary workaround until the bug gets resolved.
On Mon, Mar 19, 2018 at 6:01 AM, Andreas Hasenack <[email protected]> wrote: > > > On Fri, Mar 16, 2018 at 7:48 PM, David Hunter <[email protected]> > wrote: > >> *Guest OS*: Ubuntu 16.04.4 LTS (kernel versions 4.4.0-108 to current 116) >> >> *Virtualization env*: VMWare ESXi 6.0 >> >> *Host hardware*: Dell R720 >> >> >> Using SSSD to bind linux servers to the AD domain for authentication. >> This was working fine right up to 4.4.0-104. After the update to >> -108,-109,-112, or -116, if sssd is enabled OR if it is disabled but then >> started after a successful boot and you perform a lookup (i.e. id >> some_domain_user), the entire system will freeze, and you have to force a >> reboot. There's even a blip in the syslog when it happens. >> >> >> > Hi > > this bug sounds similar: https://bugs.launchpad.net/ubuntu/+source/ > linux/+bug/1746806 > > > _______________________________________________ > sssd-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > >
_______________________________________________ sssd-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
