RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1214996 - [abrt] systemd: log_assert(): systemd-logind killed by SIGABRT
Summary: [abrt] systemd: log_assert(): systemd-logind killed by SIGABRT
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 7.2
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL: http://faf-report.itos.redhat.com/pro...
Whiteboard: abrt_hash:8c8787909f205ae5f373aea73a8...
Depends On: 1182781
Blocks: 1118366
TreeView+ depends on / blocked
 
Reported: 2015-04-24 05:19 UTC by Jakub Filak
Modified: 2016-12-01 00:49 UTC (History)
15 users (show)

Fixed In Version: systemd-219-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1182781
Environment:
Last Closed: 2015-11-19 15:00:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 124312 0 None None None Never
Red Hat Product Errata RHBA-2015:2092 0 normal SHIPPED_LIVE systemd bug fix and enhancement update 2015-11-19 12:13:57 UTC

Description Jakub Filak 2015-04-24 05:19:26 UTC 
I think this bug is a dupe of the crash data attached to bug #1214971. See https://bugzilla.redhat.com/attachment.cgi?id=1018268


+++ This bug was initially created as a clone of Bug #1182781 +++

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

--- Additional comment from Zbigniew Jędrzejewski-Szmek on 2015-01-27 22:38:28 CET ---

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.

--- Additional comment from Zbigniew Jędrzejewski-Szmek on 2015-01-27 22:40:03 CET ---

BTW, any chance you could attach full 'journalctl -b' output, at least the part from before logind started failing.
Comment 2 Lukáš Nykrýn 2015-04-24 08:49:08 UTC 
This should be fixed in 7.2 with the rebase.
Comment 4 errata-xmlrpc 2015-11-19 15:00:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2092.html
Note You need to log in before you can comment on or make changes to this bug.