Bug 967012

Summary: [abrt] sssd-1.9.5-1.fc18: sss_mmap_cache_gr_invalidate_gid: Process /usr/libexec/sssd/sssd_nss was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Bob McCarthy <r-mccarthy>
Component: sssdAssignee: Jakub Hrozek <jhrozek>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: jhrozek, jnansi, lslebodn, mkosek, pbrezina, sbose, sgallagh, ssorce
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1f84ce60218aae6fd67dbf89b8b23a9a561a1b3e
Fixed In Version: sssd-1.11.0-0.2.beta2.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-12 02:02:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Bob McCarthy 2013-05-24 14:09:10 UTC 
Description of problem:
reboot system

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

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/sssd/sssd_nss --debug-to-files
crash_function: sss_mmap_cache_gr_invalidate_gid
executable:     /usr/libexec/sssd/sssd_nss
kernel:         3.9.2-200.fc18.x86_64
runlevel:       N 3
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 sss_mmap_cache_gr_invalidate_gid at src/responder/nss/nsssrv_mmap_cache.c:735
 #1 nss_update_initgr_memcache at src/responder/nss/nsssrv_cmd.c:3498
 #2 nss_memcache_initgr_check at src/responder/nss/nsssrv.c:332
 #3 sbus_message_handler at src/sbus/sssd_dbus_connection.c:430
 #4 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:862
 #6 sbus_dispatch at src/sbus/sssd_dbus_connection.c:104
 #7 tevent_common_loop_timer_delay at ../tevent_timed.c:254
 #8 std_event_loop_once at ../tevent_standard.c:560
 #9 _tevent_loop_once at ../tevent.c:507
 #10 tevent_common_loop_wait at ../tevent.c:608
Comment 1 Bob McCarthy 2013-05-24 14:09:15 UTC 
Created attachment 752653 [details]
File: backtrace
Comment 2 Bob McCarthy 2013-05-24 14:09:18 UTC 
Created attachment 752654 [details]
File: cgroup
Comment 3 Bob McCarthy 2013-05-24 14:09:22 UTC 
Created attachment 752655 [details]
File: core_backtrace
Comment 4 Bob McCarthy 2013-05-24 14:09:25 UTC 
Created attachment 752656 [details]
File: dso_list
Comment 5 Bob McCarthy 2013-05-24 14:09:29 UTC 
Created attachment 752657 [details]
File: environ
Comment 6 Bob McCarthy 2013-05-24 14:09:36 UTC 
Created attachment 752658 [details]
File: limits
Comment 7 Bob McCarthy 2013-05-24 14:09:39 UTC 
Created attachment 752659 [details]
File: maps
Comment 8 Bob McCarthy 2013-05-24 14:09:43 UTC 
Created attachment 752660 [details]
File: open_fds
Comment 9 Bob McCarthy 2013-05-24 14:09:46 UTC 
Created attachment 752661 [details]
File: proc_pid_status
Comment 10 Bob McCarthy 2013-05-24 14:09:50 UTC 
Created attachment 752662 [details]
File: var_log_messages
Comment 11 Jakub Hrozek 2013-05-24 14:22:50 UTC 
Thanks for filing the bug report. Currently we are not aware of any crashes in the memory cache so this must be a new issue. I will clone the bug upstream.
Comment 12 Jakub Hrozek 2013-05-24 14:27:00 UTC 
Upstream ticket:
https://fedorahosted.org/sssd/ticket/1948
Comment 13 Lukas Slebodnik 2013-05-27 10:49:22 UTC 
Could you also attach coredump. It will help us a lot.
It should be located in /var/tmp/abrt/cpp-<date_of_sssd_crash>
If you don't want to attach coredump, you can send it to my email.
Comment 14 Martin Kosek 2013-08-15 13:43:12 UTC 
Related upstream ticket:
https://fedorahosted.org/sssd/ticket/2018
Comment 15 Martin Kosek 2013-08-15 13:45:22 UTC 
Upstream ticket was closed:

master: 9028706a00da1bc48547e74aa872c825ac15adb2
sssd-1-10: 269c115496578dc9bc9f2d9b63e8343e76880a28
sssd-1-9: 4fda9979a05c1a4bf7a066f9633e8db5494f2eb3

Moving to POST.
Comment 16 Fedora Update System 2013-08-23 14:08:01 UTC 
sssd-1.11.0-0.2.beta2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/sssd-1.11.0-0.2.beta2.fc19
Comment 17 Fedora Update System 2013-08-23 23:57:18 UTC 
Package sssd-1.11.0-0.2.beta2.fc19:
* 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.11.0-0.2.beta2.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-15215/sssd-1.11.0-0.2.beta2.fc19
then log in and leave karma (feedback).
Comment 18 Fedora Update System 2013-09-12 02:02:57 UTC 
sssd-1.11.0-0.2.beta2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.