> "Machines that came up this morning worked with respect to LDAP"
Very interesting, but that makes it hard to differ from a transient
issue that happened just once or if on the given day the combination of
packages was in a state to cause this :-/
> "the machine that was brought up yesterday and referenced in this bug
report still does not."
So at least we could check to go debugging this one as long as it is
broken.
The code throwing that msg is
53 ret = set_locale();
54 if (ret != EOK) {
55 DEBUG(SSSDBG_CRIT_FAILURE,
56 "set_locale() failed (%d): %s\n", ret, strerror(ret));
57 ERROR("Error setting the locale\n");
58 ret = EXIT_FAILURE;
59 goto fini;
60 }
So it actually logs about as much as it can which makes up the error
message you reported.
The fix referenced seems to apply back to trusty, but since all other
machines work fine we have the problem that as soon as we change
*anything* we might consider it being the fix while it is not.
Also since neither you nor I can recreate a new system to debug I'd much
more like to keep the broken system broken and debug there for now.
Could you follow [1] to add debug symbols.
Then install at least sssd-common-dbgsym (actually all sssd-*-dbgsym might be
safer to catch all). As well as libc6-dbg libc6-dbgsym.
I read that a direct call to /usr/bin/sss_ssh_authorizedkeys fails, so you
could now run
$ gdb /usr/bin/sss_ssh_authorizedkeys
b set_locale
run <yourusername>
This will get you to the function set_locale of sssd.
It has three real things it does, step #1 is to find which one is failing for
you.
Just enter "n" to step through.
One of the thee setlocale, bindtextdomain, textdomain will be the one throwing
the I/O error.
I don't see how the setlocale would fail, but the two textdomain related
calls at least do I/O.
Once you know which one fails you can start over and use "s" to step into.
Some gdb basics are at [2], but this can quickly get complex depending on your
experience with it. Do this as deep as you can and this should bring us closer
to understand what your I/O error actually is about.
If anything I'd see LOCALEDIR in the I/O error scope, but that should be
/usr/share/locale for you.
Could you check just to be sure there is no random I/O or path issue what an ls
to that path gives you and if there is a subdir for your locale?
I love that sssd not even isntalls own bits there :-/ at least what I see with:
$ dpkg -L $(dpkg -l '*sssd*' | awk '/ii/ {print $2}' | xargs) | grep locale
[1]: https://wiki.ubuntu.com/Debug%20Symbol%20Packages
[2]:
https://sourceware.org/gdb/onlinedocs/gdb/Continuing-and-Stepping.html#Continuing-and-Stepping
** Changed in: sssd (Ubuntu)
Status: New => Incomplete
--
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
