Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionJaroslav Kortus
2014-03-13 20:41:01 UTC
Description of problem:
systemd-logind generated a coredump along these lines:
Mar 13 21:00:26 virt-142 dbus[561]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Mar 13 21:00:26 virt-142 systemd-logind[560]: Failed to start unit user-0.slice: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security pol
Mar 13 21:00:26 virt-142 systemd-logind[560]: Failed to start user slice: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blo
Mar 13 21:00:26 virt-142 systemd-logind[560]: Assertion 's->user->slice' failed at src/login/logind-session.c:505, function session_start_scope(). Aborting.
Mar 13 21:00:26 virt-142 dbus-daemon[561]: dbus[561]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
It may be related to https://bugzilla.redhat.com/show_bug.cgi?id=1076232 as they appeared very close to each other
Version-Release number of selected component (if applicable):
systemd-208-8.el7.x86_64
How reproducible:
unknown
Steps to Reproduce:
1.
2.
3.
Actual results:
crash
Expected results:
no crash
Additional info:
It may be related to https://bugzilla.redhat.com/show_bug.cgi?id=1076232 as they appeared very close to each other
Core was generated by `/usr/lib/systemd/systemd-logind'.
Program terminated with signal 6, Aborted.
#0 0x00007fa5ecd3b989 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) bt
#0 0x00007fa5ecd3b989 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007fa5ecd3d098 in __GI_abort () at abort.c:90
#2 0x00007fa5ee3bac93 in log_assert (text=<optimized out>, file=0x7fa5ee3c9476 "src/login/logind-session.c", line=505, func=0x7fa5ee3c9e30 <__PRETTY_FUNCTION__.9892> "session_start_scope",
format=format@entry=0x7fa5ee3ce1f8 "Assertion '%s' failed at %s:%u, function %s(). Aborting.") at src/shared/log.c:716
#3 0x00007fa5ee3bb260 in log_assert_failed (text=<optimized out>, file=<optimized out>, line=<optimized out>, func=<optimized out>) at src/shared/log.c:721
#4 0x00007fa5ee3ad852 in session_start_scope (s=0x7fa5ee74f2c0) at src/login/logind-session.c:505
#5 session_start (s=s@entry=0x7fa5ee74f2c0) at src/login/logind-session.c:559
#6 0x00007fa5ee3a643e in bus_manager_create_session (message=0x7fa5ee74f650, m=0x0) at src/login/logind-dbus.c:643
#7 manager_message_handler (connection=0x7fa5ee74cc30, message=message@entry=0x7fa5ee74f650, userdata=userdata@entry=0x7fa5ee74a030) at src/login/logind-dbus.c:1725
#8 0x00007fa5ed92fc86 in _dbus_object_tree_dispatch_and_unlock (tree=0x7fa5ee74c8d0, message=message@entry=0x7fa5ee74f650, found_object=found_object@entry=0x7fffeff68034) at dbus-object-tree.c:862
#9 0x00007fa5ed921e49 in dbus_connection_dispatch (connection=0x7fa5ee74cc30) at dbus-connection.c:4672
#10 0x00007fa5ee3a1ef7 in manager_run (m=m@entry=0x7fa5ee74a030) at src/login/logind.c:1172
#11 0x00007fa5ee39f65a in main (argc=<optimized out>, argv=<optimized out>) at src/login/logind.c:1307
Comment 4RHEL Program Management
2014-03-22 05:48:02 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.