Bug 961908

Summary: [abrt] realmd-0.14.0-1.fc19: exit: Process /usr/lib64/realmd/realmd was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: ajs <ajsfedora>
Component: libselinuxAssignee: Daniel Walsh <dwalsh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dwalsh, eparis, jhrozek, mgrepl, stefw, yelley
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:de92c3502b704cc98c0d7ea23a6cb0c0d1fa2685
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-13 20:06:02 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 ajs 2013-05-10 17:30:20 UTC 
Description of problem:
I was in the middle of performing test 'https://fedoraproject.org/wiki/QA:Testcase_realmd_join_sssd?rd=QA:Testcase_Active_Directory_realmd_join_sssd'

I had just issued 'sudo klist -k'

Version-Release number of selected component:
realmd-0.14.0-1.fc19

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/lib64/realmd/realmd
crash_function: exit
executable:     /usr/lib64/realmd/realmd
kernel:         3.9.1-301.fc19.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace:
Thread no. 1 (1 frames)
 #9 exit at exit.c:99
Comment 1 ajs 2013-05-10 17:30:23 UTC 
Created attachment 746284 [details]
File: backtrace
Comment 2 ajs 2013-05-10 17:30:25 UTC 
Created attachment 746285 [details]
File: cgroup
Comment 3 ajs 2013-05-10 17:30:26 UTC 
Created attachment 746286 [details]
File: core_backtrace
Comment 4 ajs 2013-05-10 17:30:28 UTC 
Created attachment 746287 [details]
File: dso_list
Comment 5 ajs 2013-05-10 17:30:30 UTC 
Created attachment 746288 [details]
File: environ
Comment 6 ajs 2013-05-10 17:30:31 UTC 
Created attachment 746289 [details]
File: limits
Comment 7 ajs 2013-05-10 17:30:33 UTC 
Created attachment 746290 [details]
File: maps
Comment 8 ajs 2013-05-10 17:30:35 UTC 
Created attachment 746291 [details]
File: open_fds
Comment 9 ajs 2013-05-10 17:30:37 UTC 
Created attachment 746292 [details]
File: proc_pid_status
Comment 10 ajs 2013-05-10 17:30:38 UTC 
Created attachment 746293 [details]
File: var_log_messages
Comment 11 Stef Walter 2013-05-13 10:51:09 UTC 
This happened when realmd was exiting (due to its timeout). The crash happened in libselinux. realmd makes no explicit selinux calls, and this seems to be some sort of atexit() or dl_fini handler.
Comment 12 Daniel Walsh 2013-05-13 13:54:03 UTC 
libselinux has had this behaviour for ever.  Usually when an error happens it is caused by a memory problem.  Basically libselinux at load allocates some memory and at unload frees the memory.  If something in the app has written over memory then it can cause the crash.  Can we run realmd through valgrind to see if it has some memory problems.
Comment 13 Stef Walter 2013-05-13 20:06:02 UTC 
Makes sense. Then this is almost certainly a duplicate of bug 953486

*** This bug has been marked as a duplicate of bug 953486 ***