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
wrote:
>
>
> On Fri, Mar 16, 2018 at 7:48 PM,
On Fri, Mar 16, 2018 at 7:48 PM, David Hunter
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
Regarding your group issue, do you or have you had trusted domains and the
mystery group is from another domain? Long shot, it we had the same error
when it was trying to resolve the foreign group memberships.
On Wed, Mar 14, 2018, 11:19 AM wrote:
> Hi All
>
> We've got
The first step in debugging any strangeness is usually
https://docs.pagure.org/SSSD.sssd/users/troubleshooting.html
> On 14 Mar 2018, at 16:18, simon...@hotmail.com wrote:
>
> Hi All
>
> We've got SSSD 1.13.0 installed as part of a Centos 7.2.1511 installation.
>
But this is quite an old