Bug 961908 - [abrt] realmd-0.14.0-1.fc19: exit: Process /usr/lib64/realmd/realmd was killed by signal 6 (SIGABRT)
Summary: [abrt] realmd-0.14.0-1.fc19: exit: Process /usr/lib64/realmd/realmd was kille...
Keywords:
Status: CLOSED DUPLICATE of bug 953486
Alias: None
Product: Fedora
Classification: Fedora
Component: libselinux
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:de92c3502b704cc98c0d7ea23a6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-10 17:30 UTC by ajs
Modified: 2013-05-13 20:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-13 20:06:02 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (12.88 KB, text/plain)
2013-05-10 17:30 UTC, ajs 		no flags Details
File: cgroup (154 bytes, text/plain)
2013-05-10 17:30 UTC, ajs 		no flags Details
File: core_backtrace (1.21 KB, text/plain)
2013-05-10 17:30 UTC, ajs 		no flags Details
File: dso_list (4.56 KB, text/plain)
2013-05-10 17:30 UTC, ajs 		no flags Details
File: environ (92 bytes, text/plain)
2013-05-10 17:30 UTC, ajs 		no flags Details
File: limits (1.29 KB, text/plain)
2013-05-10 17:30 UTC, ajs 		no flags Details
File: maps (23.22 KB, text/plain)
2013-05-10 17:30 UTC, ajs 		no flags Details
File: open_fds (538 bytes, text/plain)
2013-05-10 17:30 UTC, ajs 		no flags Details
File: proc_pid_status (895 bytes, text/plain)
2013-05-10 17:30 UTC, ajs 		no flags Details
File: var_log_messages (9.40 KB, text/plain)
2013-05-10 17:30 UTC, ajs 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.