Version-Release number of selected component:
cmdline: /usr/libexec/sssd/sssd_be --domain ger.corp.intel.com -d 0x77f0 --debug-to-files
runlevel: N 5
Thread no. 1 (10 frames)
#2 talloc_abort at ../talloc.c:338
#3 talloc_abort_unknown_value at ../talloc.c:362
#4 talloc_chunk_from_ptr at ../talloc.c:381
#5 talloc_get_name at ../talloc.c:1253
#6 talloc_check_name at ../talloc.c:1272
#7 nsupdate_child_handler at src/providers/dp_dyndns.c:890
#8 child_invoke_callback at src/util/child_common.c:580
#9 tevent_common_loop_immediate at ../tevent_immediate.c:135
#10 epoll_event_loop_once at ../tevent_epoll.c:912
#11 std_event_loop_once at ../tevent_standard.c:112
Created attachment 763573 [details]
Created attachment 763574 [details]
Created attachment 763575 [details]
Created attachment 763576 [details]
Created attachment 763577 [details]
Created attachment 763578 [details]
Created attachment 763579 [details]
Created attachment 763580 [details]
Created attachment 763581 [details]
Created attachment 763582 [details]
is this issue reproducible? Can you attach sssd logs please?
I think the suspiction you have about timeout is correct, David's DNS server wasn't the AD server but rather dnsmasq. But we have a unit test that exercises the timeout..
There is a patch on the list. Didn't make 1.10.0 though.
sssd-1.10.1-1.fc19 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.1-1.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
sssd-1.10.1-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.