Bug 1182781

Summary: [abrt] systemd: log_assert(): systemd-logind killed by SIGABRT
Product: [Fedora] Fedora Reporter: Mikhail Yarashevich <aloner>
Component: systemdAssignee: systemd-maint
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fac_franky, fischerjd, hannsj_uhl, johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5dfdd9347fcd1d68c773406b024b80f5475b223e
Whiteboard: abrt_hash:8c8787909f205ae5f373aea73a8cf463ce1eac2e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1214996 (view as bug list) Environment:
Last Closed: 2015-06-30 01:21:08 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:
Bug Depends On:    
Bug Blocks: 1214996    
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 Mikhail Yarashevich 2015-01-15 21:51:21 UTC 
Version-Release number of selected component:
systemd-208-28.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-logind
crash_function: log_assert
executable:     /usr/lib/systemd/systemd-logind
kernel:         3.17.8-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (6 frames)
 #2 log_assert
 #3 log_assert_failed
 #4 session_start
 #5 manager_message_handler
 #6 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:862
 #8 manager_run
Comment 1 Mikhail Yarashevich 2015-01-15 21:51:25 UTC 
Created attachment 980664 [details]
File: backtrace
Comment 2 Mikhail Yarashevich 2015-01-15 21:51:27 UTC 
Created attachment 980665 [details]
File: cgroup
Comment 3 Mikhail Yarashevich 2015-01-15 21:51:29 UTC 
Created attachment 980666 [details]
File: core_backtrace
Comment 4 Mikhail Yarashevich 2015-01-15 21:51:30 UTC 
Created attachment 980667 [details]
File: dso_list
Comment 5 Mikhail Yarashevich 2015-01-15 21:51:32 UTC 
Created attachment 980668 [details]
File: environ
Comment 6 Mikhail Yarashevich 2015-01-15 21:51:33 UTC 
Created attachment 980669 [details]
File: limits
Comment 7 Mikhail Yarashevich 2015-01-15 21:51:35 UTC 
Created attachment 980670 [details]
File: maps
Comment 8 Mikhail Yarashevich 2015-01-15 21:51:36 UTC 
Created attachment 980671 [details]
File: open_fds
Comment 9 Mikhail Yarashevich 2015-01-15 21:51:38 UTC 
Created attachment 980672 [details]
File: proc_pid_status
Comment 10 Mikhail Yarashevich 2015-01-15 21:51:41 UTC 
Created attachment 980673 [details]
File: var_log_messages
Comment 11 Zbigniew Jędrzejewski-Szmek 2015-01-27 21:38:28 UTC 
The underlying problem is a communication failure with PID 1. I'm not sure about the reason yet.

But the crash is easy enough to fix. I prepared a simple patch locally (for the v208-stable branch), and a more invasive patch for master. The fix should be part of the next build.
Comment 12 Zbigniew Jędrzejewski-Szmek 2015-01-27 21:40:03 UTC 
BTW, any chance you could attach full 'journalctl -b' output, at least the part from before logind started failing.
Comment 13 Fedora End Of Life 2015-05-29 13:37:00 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Fedora End Of Life 2015-06-30 01:21:08 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.