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.

Description of problem:

Received abrt report on crash:

time:           Wed 30 Sep 2015 11:31:49 AM EDT
cmdline:        /usr/lib/systemd/systemd-logind
uid:            0 (root)
abrt_version:   2.1.11
backtrace_rating: 4
crash_function: __epoll_wait_nocancel
event_log:      
executable:     /usr/lib/systemd/systemd-logind
global_pid:     621
hostname:       ibm-hs21-12.testrelm.test
kernel:         3.10.0-320.el7.x86_64
last_occurrence: 1443627109
pid:            621
pkg_arch:       x86_64
pkg_epoch:      0
pkg_name:       systemd
pkg_release:    17.el7
pkg_version:    219
pwd:            /
runlevel:       N 3
username:       root

coredump.gz:    Binary file, 71736 bytes

Version-Release number of selected component (if applicable):
pkg_name:       systemd
pkg_release:    17.el7
pkg_version:    219

How reproducible:
unknown

Steps to Reproduce:
Unknown

Actual results:
crash

Expected results:
no crash

Additional info:

Created attachment 1078763 [details]
abrt email

Same crash 
OS RHEL7.1 + Update systemd, dracut, linux-firmware and kernel.

systemd-219-19.el7.x86_64

(gdb) bt
#0  0x00007fa408d77763 in __epoll_wait_nocancel () from /lib64/libc.so.6
#1  0x00007fa409ce3449 in sd_event_wait (e=e@entry=0x7fa40a4b1230,
    timeout=timeout@entry=18446744073709551615)
    at src/libsystemd/sd-event/sd-event.c:2372
#2  0x00007fa409cda137 in sd_event_run (timeout=18446744073709551615,
    e=0x7fa40a4b1230) at src/libsystemd/sd-event/sd-event.c:2499
#3  manager_run (m=0x7fa40a4b00a0) at src/login/logind.c:1119
#4  main (argc=<optimized out>, argv=<optimized out>)
    at src/login/logind.c:1181

We should definitely backport commit that adjusts watchdog timeout. 1min. is just too short in some cases. Also there are couple other related fixes we should pull in

https://github.com/systemd/systemd/commit/19854865a877a3a4fa3d04550c15a99c0e1187ff
https://github.com/systemd/systemd/commit/b215b0ede11c0dda90009c8412609d2416150075

https://github.com/lnykryn/systemd-rhel/pull/36

QA acking..

Committed to staging -> 
https://github.com/lnykryn/systemd-rhel/commit/5be84b3ae46c0fd35c3e80d4f457bf5aedc8af8f
https://github.com/lnykryn/systemd-rhel/commit/a3b8feb9320f745f960fe8f7006183137f4969b1
https://github.com/lnykryn/systemd-rhel/commit/64e21697bdefe0a37edc8557fd110daea2667771
-> post

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-2016-2216.html