Bug 1267707
| Summary: | systemd-logind __epoll_wait_nocancel crash | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Scott Poore <spoore> | ||||
| Component: | systemd | Assignee: | Jan Synacek <jsynacek> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Branislav Blaškovič <bblaskov> | ||||
| Severity: | high | Docs Contact: | Lucie Vařáková <lmanasko> | ||||
| Priority: | high | ||||||
| Version: | 7.2 | CC: | bblaskov, hartsjc, jsynacek, masanari.iida, moagrawa, mosvald, msekleta, rmetrich, ssahani, systemd-maint-list | ||||
| Target Milestone: | rc | ||||||
| Target Release: | 7.3 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | systemd-219-25.el7 | Doc Type: | Release Note | ||||
| Doc Text: |
The value of "net.unix.max_dgram_qlen" increased to 512
Previously, the default value of the "net.unix.max_dgram_qlen" kernel option was 16. As a consequence, when the network traffic was too high, certain services could terminate unexpectedly. This update sets the value to 512, thus preventing this problem. Users need to reboot the machine to apply this change.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-11-04 00:44:05 UTC | Type: | Bug | ||||
| 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: | 1203710, 1546795 | ||||||
| Attachments: |
|
||||||
|
Description
Scott Poore
2015-09-30 18:19:42 UTC
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 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 |