I thought I set this as an sssd bug, sorry about that. I have many machines (in the tens to hundreds) across an estate all of whom have the same sssd configuration against LDAP. Machines that came up this morning worked with respect to LDAP, the machine that was brought up yesterday and referenced in this bug report still does not. All machines are orchestrated in the same way by the same version controlled mechanism.
It looks like in my case there are a number of bugs happening simultaneously: - Running sss_ssh_authorizedkeys from the command line fails with "set_locale() failed (5): Input/output error" when it should not fail. Backporting the fixes above should fix this. - There are errors in auth.log saying "error: AuthorizedKeysCommand /usr/bin/sss_ssh_authorizedkeys returned status 1" - sss_ssh_authorizedkeys is broken in that it does not log anything to syslog on failure OR ssh is broken in that when it invokes sss_ssh_authorizedkeys the output of sss_ssh_authorizedkeys is lost. For this reason it is impossible to tell for certain whether the "status 1" is caused by the set_locale failed, or something else. For a start, it looks like sss_ssh_authorizedkeys need to log properly, something it does not do now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675118 Title: Setting locale breaks sss_ssh_authorizedkeys: set_locale() failed (5): Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1675118/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
