Description of problem: I upgraded to Fedora 19 from Fedora 18 using fedup. I tried to login with my AD credentials which had been set up using "realm join" in F18. I could not authenticate so logged in as a local user, did "realm leave" and then a new "realm join". Can now authenticate. However, when using sudo to run a command, I get a crash in sssd_pac. /var/log/sssd/sssd_pac.log is 0 byte. Version-Release number of selected component: sssd-ipa-1.10.0-12.fc19.beta2 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/sssd/sssd_pac --debug-to-files crash_function: pac_lookup_sids_done executable: /usr/libexec/sssd/sssd_pac kernel: 3.9.8-300.fc19.x86_64 runlevel: N 5 uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 pac_lookup_sids_done at src/responder/pac/pacsrv_cmd.c:309 #1 pac_lookup_sids_next_done at src/responder/pac/pacsrv_cmd.c:1070 #2 sss_dp_internal_get_done at src/responder/common/responder_dp.c:779 #3 complete_pending_call_and_unlock at dbus-connection.c:2314 #5 sbus_dispatch at src/sbus/sssd_dbus_connection.c:104 #6 tevent_common_loop_timer_delay at ../tevent_timed.c:341 #7 epoll_event_loop_once at ../tevent_epoll.c:916 #8 std_event_loop_once at ../tevent_standard.c:112 #9 _tevent_loop_once at ../tevent.c:530 #10 tevent_common_loop_wait at ../tevent.c:634
Created attachment 768565 [details] File: backtrace
Created attachment 768566 [details] File: cgroup
Created attachment 768567 [details] File: core_backtrace
Created attachment 768568 [details] File: dso_list
Created attachment 768569 [details] File: environ
Created attachment 768570 [details] File: limits
Created attachment 768571 [details] File: maps
Created attachment 768572 [details] File: open_fds
Created attachment 768573 [details] File: proc_pid_status
Created attachment 768574 [details] File: var_log_messages
It is good, that you were able to authenticate after running commands "reaml leave" and "realm join". If you want verbose debug messages in pac log, you will need to add option "debug_level = 10" to "pac" section in sssd configuration file "/etc/sssd/sssd.conf". If there is not any "pac" section, It will be no problem to create one. [pac] debug_level = 10 I have an idea, why sssd crashed, but I am not really sure. Could you attach coredump? Coredump help us a lot with finding a real reason of crash. It should be automatically generated by abrt, but it has not been uploaded to this ticket. You can find coredump in /var/spool/abrt or /var/tmp/abrt/ Log files will be also very helpful (at least sssd_pac and sssd_<domain_name>)
I was able to reproduce this crash. Even coredump or logs are not needed.
Upstream ticket: https://fedorahosted.org/sssd/ticket/2008
Package sssd-ad >= 1.10.0-13.fc19 should fix your issue and sssd-ad-1.10.0-16 is available in Fedora 19 testing repository. You can install this package with command: sudo yum update --enablerepo=updates-testing sssd-ad-1.10.0-16.fc19
sssd-ad-1.10.0-16.fc19 seems to have solved this particular crash for me, however I am now seeing a crash in sssd-common which doesn't seem to have any functional impact. Next time I see it I will investigate further and see if it's already reported.
(In reply to Andy Kelk from comment #15) > sssd-ad-1.10.0-16.fc19 seems to have solved this particular crash for me, > however I am now seeing a crash in sssd-common which doesn't seem to have > any functional impact. Next time I see it I will investigate further and see > if it's already reported. Thank you for testing, Andy! I'm going to close this particular bug and please open a new report if you can reproduce the other crash. Thank you for reporting the issues and sorry for the trouble you are having.