Bug 1261212
| Summary: | puppet agent terminates with SIGTERM | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Randy Zagar <zagar> |
| Component: | puppet | Assignee: | Jeroen van Meeuwen <vanmeeuwen+fedora> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel7 | CC: | dominic, ekohlvan, gchamoul, jose.p.oliveira.oss, k.georgiou, ktdreyer, lsolberg, marianne, mastahnke, mmagr, moses, s, tmz, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-06-12 14:41:48 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: | |||
|
Description
Randy Zagar
2015-09-08 23:11:15 UTC
This is happening to me as well, but in my case it caused a little cascading effect that I will look at some more before reporting them as separate bugzilla's. Basically; * Puppet crashed (as in this bugzilla, it does that a lot, see below!) * abrt starts it's reporting, one of them being generating sosreport. * sosreport tries to run 'lsusb -t', which gets a hanging segfault. * the segfault hangs (http://stackoverflow.com/questions/33673592/segmentation-fault-itself-is-hanging), and a restart of abrtd is needed to "unhang" the segfaults on the system. This makes abrt-status hangs waiting for the lock of the abrt reporting the initial puppet crash. Basically causing the login (to root), (the act of loading bash profiles), to hang. Some of the abrt reports that I have on one of my servers (so you can see how often this is happening); 2015-09-28-12:44:54-1169 2015-09-28-13:40:40-1072 2015-09-28-14:09:56-14117 2015-09-29-08:32:47-6034 2015-09-29-08:34:02-10123 2015-09-29-08:37:19-18028 2015-09-29-08:41:35-26645 2015-09-29-08:46:04-5029 2015-09-29-08:47:43-9266 2015-09-29-08:52:30-20664 2015-09-29-08:53:48-23668 2015-09-29-08:57:20-30389 2015-09-29-09:22:40-27493 2015-09-29-09:32:15-14669 2015-09-29-09:56:12-6562 2015-09-29-09:57:00-8015 2015-09-29-09:59:27-12439 2015-09-29-10:36:50-14058 2015-09-29-10:49:01-17968 2015-09-29-11:23:18-28189 2015-09-29-11:24:59-31388 2015-09-29-12:29:26-10304 2015-09-29-12:32:13-15898 2015-10-02-13:38:11-1786 2015-11-12-10:07:50-19083 2015-10-02-13:42:41-2038 2015-10-02-13:36:41-1645 2015-10-02-13:41:11-1955 2015-10-01-13:34:39-15231 2015-10-01-13:46:11-29721 2015-10-01-13:50:04-2894 2015-10-01-14:12:02-21134 2015-10-02-13:39:41-1869 2015-10-02-13:44:12-2120 2015-10-02-10:57:55-32358 2015-10-02-13:45:42-2208 2015-11-12-10:01:49-11825 2015-11-12-10:03:19-17738 2015-11-12-10:04:50-18834 2015-11-12-10:06:20-18968 Randy, are your crashes with the same stack trace and exception (SIGTERM received)? It indicates that the service is being stopped perhaps, as it's an external signal rather than a crash. Can you provide journalctl output of the affected time period to show if a service stop was requested? Lars, I'm not sure the ABRT issues are due to Puppet, but if you have the same SIGTERM error as above, perhaps you can provide additional information. I've been unable to find similar reports on ABRT's retrace server. Puppet will be retired from EPEL 7. |