#1751 [abrt] sssd-1.9.3-1.fc18: be_host_handler: Process /usr/libexec/sssd/sssd_be was killed by signal 11 (SIGSEGV)
Closed: Invalid None Opened 11 years ago by jhrozek.

https://bugzilla.redhat.com/show_bug.cgi?id=893664 (Fedora)

Description of problem:
Testing out using an ipa server with sssd.

Version-Release number of selected component:
sssd-1.9.3-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/sssd/sssd_be --domain default --debug-to-files
crash_function: be_host_handler
executable:     /usr/libexec/sssd/sssd_be
kernel:         3.6.11-3.fc18.x86_64
remote_result:  NOTFOUND
uid:            0

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 be_host_handler at src/providers/data_provider_be.c:1721
 #1 sbus_message_handler at src/sbus/sssd_dbus_connection.c:430
 #2 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:862
 #4 sbus_dispatch at src/sbus/sssd_dbus_connection.c:104
 #5 tevent_common_loop_timer_delay at ../tevent_timed.c:254
 #6 std_event_loop_once at ../tevent_standard.c:560
 #7 _tevent_loop_once at ../tevent.c:507
 #8 tevent_common_loop_wait at ../tevent.c:608
 #9 server_loop at src/util/server.c:601

Fields changed

blockedby: =>
blocking: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
priority: major => critical
selected: =>
testsupdated: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.4

We could never reliably reproduce the problem nor could the reporter for the last couple of days. We'll still be tracking the bug as we gave the reporter an instrumented build and a gdb script to help us see what's wrong.

But this is not blocking the 1.9.4 release anymore. Bumping to 1.9.5

milestone: SSSD 1.9.4 => SSSD 1.9.5
owner: somebody => pbrezina

The corresponding Fedora bug was closed as worksforme. We patched the host handler to not crash if the data was uninitialized (as do the other handlers already).

Fields changed

resolution: => worksforme
status: new => closed

FWIW the fix that corrected the bug was 3082504

changelog: =>
review: => 0

Metadata Update from @jhrozek:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.9.5

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2793

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata