#1947 [abrt] sssd-1.10.0-4.fc19.beta1: get_server_status: Process /usr/libexec/sssd/sssd_be was killed by signal 11 (SIGSEGV)
Closed: Fixed None Opened 5 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 967004

Description of problem:
After reconnecting the network in network manager, SSSD crashed. Likely due to
attempting to reconnect to network account services?

Version-Release number of selected component:
sssd-1.10.0-4.fc19.beta1

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/sssd/sssd_be --domain ad.firstyear.id.au
--debug-to-files
crash_function: get_server_status
executable:     /usr/libexec/sssd/sssd_be
kernel:         3.9.2-301.fc19.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 get_server_status at src/providers/fail_over.c:308
 #1 fo_resolve_service_server at src/providers/fail_over.c:1036
 #2 fo_resolve_service_cont at src/providers/fail_over.c:1025
 #3 resolve_srv_done at src/providers/fail_over.c:1303
 #4 fo_discover_srv_done at src/providers/fail_over_srv.c:139
 #5 resolv_discover_srv_done at src/resolv/async_resolv_utils.c:299
 #6 resolv_getsrv_done at src/resolv/async_resolv.c:1661
 #7 qcallback at ares_query.c:180
 #8 end_query at ares_process.c:1266
 #9 process_answer at ares_process.c:611

Fields changed

blockedby: =>
blocking: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.10.0
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

changelog: =>
owner: somebody => lslebodn
patch: 0 => 1

Fields changed

owner: lslebodn => pbrezina
status: new => assigned

resolution: => fixed
status: assigned => closed

Fields changed

changelog: => N/A, just a bugfix

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

2 years ago

Login to comment on this ticket.

Metadata