Ticket #1751 (closed defect: worksforme)

Opened 16 months ago

Last modified 5 weeks ago

[abrt] sssd-1.9.3-1.fc18: be_host_handler: Process /usr/libexec/sssd/sssd_be was killed by signal 11 (SIGSEGV)

Reported by: jhrozek Owned by: pbrezina
Priority: critical Milestone: SSSD 1.9.5
Component: SSSD Version:
Keywords: Cc:
Blocked By: Blocking:
Tests Updated: no Coverity Bug:
Patch Submitted: no Red Hat Bugzilla: 893664, 1019285, 1071823
Design link:
Feature Milestone:
Design review: no Fedora test page:
Chosen: Candidate to push out: no
Release Notes:

Description

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

Change History

comment:1 Changed 16 months ago by jhrozek

  • Design review unset
  • Priority changed from major to critical
  • Tests Updated unset

comment:2 Changed 16 months ago by jhrozek

  • Milestone changed from NEEDS_TRIAGE to SSSD 1.9.4

comment:3 Changed 15 months ago by jhrozek

  • Milestone changed from SSSD 1.9.4 to SSSD 1.9.5
  • Owner changed from somebody to pbrezina

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

comment:4 Changed 15 months ago by jhrozek

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).

comment:5 Changed 15 months ago by jhrozek

  • Resolution set to worksforme
  • Status changed from new to closed

comment:6 Changed 6 months ago by jhrozek

  • Red Hat Bugzilla changed from [https://bugzilla.redhat.com/show_bug.cgi?id=893664 893664] to [https://bugzilla.redhat.com/show_bug.cgi?id=893664 893664], [https://bugzilla.redhat.com/show_bug.cgi?id=1019285 1019285]

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1019285 (Red Hat Enterprise Linux 6)

comment:7 Changed 7 weeks ago by jhrozek

  • Candidate to push out unset

FWIW the fix that corrected the bug was 3082504f4fb4e4efdc50c99369204e5b2cfac40e

comment:8 Changed 5 weeks ago by jhrozek

  • Red Hat Bugzilla changed from [https://bugzilla.redhat.com/show_bug.cgi?id=893664 893664], [https://bugzilla.redhat.com/show_bug.cgi?id=1019285 1019285] to [https://bugzilla.redhat.com/show_bug.cgi?id=893664 893664], [https://bugzilla.redhat.com/show_bug.cgi?id=1019285 1019285], [https://bugzilla.redhat.com/show_bug.cgi?id=1071823 1071823]

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1071823 (Red Hat Enterprise Linux 6)

Note: See TracTickets for help on using tickets.