Hello,
I am having a problem where a user is trying to authenticate to our European servers while sitting in our Asian office where the link is not of the best quality.
What he is experiencing is a number of failed authentication attempts.
SSSD version 1.8.5 from Timo Aaltonen's PPA running on Ubuntu 12.04.
auth.log says: sudo: pam_sss(sudo:auth): Request to sssd failed. Broken pipe sssd.log says: [sssd] [monitor_quit] (0x0010): Monitor received Terminated: terminating children
I am attaching our sssd.conf (template, treat [% ... %] entries as containing valid information, I can't disclose that).
From what I understand, an LDAP query is being fired, but it cannot complete due to network going down each now and then.
Can we do something to limit the impact of failed communication attempts?
Best regards, Bolesław Tokarski
On Wed, Jan 23, 2013 at 02:55:18PM +0100, Bolesław Tokarski wrote:
Hello,
I am having a problem where a user is trying to authenticate to our European servers while sitting in our Asian office where the link is not of the best quality.
What he is experiencing is a number of failed authentication attempts.
SSSD version 1.8.5 from Timo Aaltonen's PPA running on Ubuntu 12.04.
auth.log says: sudo: pam_sss(sudo:auth): Request to sssd failed. Broken pipe sssd.log says: [sssd] [monitor_quit] (0x0010): Monitor received Terminated: terminating children
"Broken Pipe" could indicate a segfault, can you check syslog for any signs of an SSSD component crashing?
If there's nothing of interest, can you raise the debug level (put debug_level=N where N is 7 or higher into the [pam] and [domain] sections of SSSD and restart the SSSD) and attach the logs?
Hello,
On 01/24/2013 06:22 AM, Jakub Hrozek wrote:
auth.log says: sudo: pam_sss(sudo:auth): Request to sssd failed. Broken pipe sssd.log says: [sssd] [monitor_quit] (0x0010): Monitor received Terminated: terminating children "Broken Pipe" could indicate a segfault, can you check syslog for any signs of an SSSD component crashing?
Thanks for the tip, I was thinking about the same, but there's nothing indicative in syslog.
If there's nothing of interest, can you raise the debug level (put debug_level=N where N is 7 or higher into the [pam] and [domain] sections of SSSD and restart the SSSD) and attach the logs?
I will try getting that and will report back.
Have a good day.
Cheers, Ballock
sssd-users@lists.fedorahosted.org