#9 0x00007f8513ef4a4a in kScreenSaverMain (argc=,Īt /usr/src/debug/kde-workspace-4.10.2/kscreensaver/libkscreensaver/main.cpp:228 #6 0x00007f85136c39ef in QEventLoop::processEvents flags=.) at kernel/qeventloop.cpp:149 This=, flags=.) at kernel/qguieventdispatcher_glib.cpp:204 #5 0x00007f8512b0ec1e in QGuiEventDispatcherGlib::processEvents ( #2 g_main_context_iterate self=) at gmain.c:3285 I waited 2-3 more minutes and the restarted sssd to make login work again.(Running on openSUSE 12.3 here, with KDE 4.10.2 and Qt 4.8.4) In sssd_pam.log, it says that 1) it successfully reconnected to the data provider, but 2) an identical authentication request already exists.ĥ. Wait for sssd_be getting killed and restarted.Ĥ. In sssd_pam.log, you can see an authentication request getting sent.ģ. Try to log in, nothing happens (expected). Hence, it's not 100% the identical to the problem #2 described above.Ģ. This situation comes very close to the original problem, but I do not get the Timer expired error message in /var/log/messages. I was not able to reproduce this 100%, I think the key part is to do a login trial while sssd_be is not responding. But also, I cannot login, once sssd_be restarted. If I try to login to the box while sssd_be is in STOP state, nothing happens (obviously). Do so, the pings to sssd_be fail and it gets killed and restarted after about 5+ ping trials. I tried to simulate a hang of sssd_be by issuing a "pkill -signal STOP sssd_be". Summary: Login fails after some idle time - default module crashed? => Login fails - sssd_be module polling fd indefinitely and gets killed Module sssd_default restarts, but login still not possible, maybe due to broken connection to sssd/ldap/krb module after restart ( Timer expired error around 13:06-13:08)? Solution Login at 13:01:53 fails as sssd_default seems to crash when performing LDAP search. Still, login is not possible after this, as all the KDE login trials between 13:06 and 13:08 with user iscan don't even show up in here.There is sudden break after "Executing sasl bind mech: GSSAPI, user: (null)" at 13:01:53 suggest that this module crashed and then is restartet ad 13:03./var/log/sssd/sssd_default.log is interesting./var/log/sssd/ldap_child.log looks normal, child acquires Kerberos principal from keytab:\./var/log/sssd/krb5_child.log, nothing really around the mentioned time\.Nov 19 13:08:32 st-iscan kcheckpass: Authentication failure for iscan (invoked by uid 10052) Nov 19 13:08:32 st-iscan kcheckpass: pam_sss(xdm:auth): Request to sssd failed. Nov 19 13:08:09 st-iscan kcheckpass: Authentication failure for iscan (invoked by uid 10052) Nov 19 13:08:09 st-iscan kcheckpass: pam_sss(xdm:auth): Request to sssd failed. Nov 19 13:07:49 st-iscan kcheckpass: Authentication failure for iscan (invoked by uid 10052) Nov 19 13:07:49 st-iscan kcheckpass: pam_sss(xdm:auth): Request to sssd failed. Nov 19 13:07:28 st-iscan kcheckpass: Authentication failure for iscan (invoked by uid 10052) Nov 19 13:07:28 st-iscan kcheckpass: pam_sss(xdm:auth): Request to sssd failed. Nov 19 13:06:53 st-iscan kcheckpass: Authentication failure for iscan (invoked by uid 10052) Nov 19 13:06:53 st-iscan kcheckpass: pam_sss(xdm:auth): Request to sssd failed. Nov 19 13:03:35 st-iscan sssd]: Starting up
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |