sssd.conf missing and fails to be generated

[tigloo]

Hi,

I have a fresh install of FreeNAS 9.10.1-U1 with just minor configuration changes. I have repeatedly reinstalled FreeNAS, but eventually always run into a situation where sssd.conf is not present on the system anymore. This causes for example Samba to throw a few PAM-related error messages.

Is this an intentional side-effect of some configuration option or is this a bug?

 

[dlavigne]

Does updating to U2 resolve the issue?

 

[tigloo]

Well... not so much. Updating to U2 caused the box to not boot anymore, because it can't find the kernel anymore.

 

[Ericloewe]

Sounds like your boot device needs replacing.

 

[tigloo]

@Ericloewe: Already replaced it twice. Looking at the bugs in FreeNAS 9.10.1, I'm not so sure it can be blamed on hardware.

@dlavigne: I started from a fresh installation and even with U2 there is no sssd.conf. It did pull my old settings from somewhere though - does FreeNAS store a backup of its configuration somewhere?

 

[xenu]

@tigloo Did you by any chance allow anonymous bind in FreeNAS LDAP settings? I had a missing sssd.conf and couldn't get it to be regenerated after switching from my own openldab+krb5 to freeIPA. Looking at the main function in "/usr/local/libexec/nas/generate_sssd_conf.py" I noticed it exits if ldap is enabled but anonymous bind is allowed.

 

[tigloo]

@xenu This is correct, unchecking anonymous binds creates an sssd.conf. Thanks!