Red Hat Bugzilla – Bug 908759
[abrt] sssd-1.9.3-1.fc18: talloc_abort: Process /usr/libexec/sssd/sssd_be was killed by signal 6 (SIGABRT)
Last modified: 2013-05-15 13:29:29 EDT
Description of problem:
Ran ipa-client-install to join an IPA domain. 10 minutes later sssd crash notification came up.
Version-Release number of selected component:
cmdline: /usr/libexec/sssd/sssd_be --domain ipa.thewalter.lan --debug-to-files
var_log_messages: Feb 7 13:31:37 stef-rawhide-thewalter-lan abrt: Saved core dump of pid 8282 (/usr/libexec/sssd/sssd_be) to /var/spool/abrt/ccpp-2013-02-07-13:31:36-8282 (18923520 bytes)
Thread no. 1 (10 frames)
#2 talloc_abort at ../talloc.c:317
#3 talloc_abort_access_after_free at ../talloc.c:336
#4 talloc_chunk_from_ptr at ../talloc.c:357
#6 talloc_get_name at ../talloc.c:1153
#7 talloc_check_name at ../talloc.c:1172
#8 ipa_dyndns_child_handler at src/providers/ipa/ipa_dyndns.c:1173
#9 child_invoke_callback at src/util/child_common.c:578
#10 tevent_common_loop_immediate at ../tevent_immediate.c:135
#11 std_event_loop_once at ../tevent_standard.c:556
#12 _tevent_loop_once at ../tevent.c:507
Created attachment 694448 [details]
Created attachment 694449 [details]
Created attachment 694450 [details]
Created attachment 694451 [details]
Created attachment 694452 [details]
Created attachment 694453 [details]
Created attachment 694454 [details]
Created attachment 694455 [details]
Created attachment 694456 [details]
Created attachment 694457 [details]
Thank you for the bug report. Can you check if there is anything in /var/log/sssd/sssd_ipa.thewalter.lan.log ? The reason why the SSSD crashed was an access-after-free and we should be logging those by default.
Hmmm, my sssd_ipa.thewalter.lan.log is empty, and has been since last year. Is there something i should have in /etc/sssd/sssd.conf by default?
(In reply to comment #13)
> Hmmm, my sssd_ipa.thewalter.lan.log is empty, and has been since last year.
> Is there something i should have in /etc/sssd/sssd.conf by default?
No, we added a support to include talloc logs in SSSD's debug logs at the most verbose level. You should see them even if debug_level is set to 0. If you don't, then probably talloc didn't detect the problem on its own.
Hi, the backtrace says that it was detected by talloc so there definitely should be a message. Is it possible that you have disabled debugging to files?
sssd is configured to work with kerberos and nis. ypbind may or may not be running depending on network connectivity
OS Release: Fedora release 18 (Spherical Cow)
(In reply to comment #16)
> sssd is configured to work with kerberos and nis. ypbind may or may not be
> running depending on network connectivity
> backtrace_rating: 4
> Package: sssd-1.9.4-5.fc18
> OS Release: Fedora release 18 (Spherical Cow)
I'm reasonably sure that this is a different issue as the code in question is only ever reachable when using the IPA provider. Can you open a new bug?
sssd-1.10.0-3.fc19.beta1 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing sssd-1.10.0-3.fc19.beta1'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
sssd-1.10.0-4.fc19.beta1 has been submitted as an update for Fedora 19.
sssd-1.10.0-3.fc19.beta1 has been pushed to the Fedora 19 obsolete repository. If problems still persist, please make note of it in this bug report.