| Summary: | Hung awk after logrotate fails | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Trevor Hemsley <trevor.hemsley> |
| Component: | logrotate | Assignee: | Jan Kaluža <jkaluza> |
| Status: | CLOSED CANTFIX | QA Contact: | qe-baseos-daemons |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.7 | CC: | tsmetana |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-08 07:11:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Are you sure cobblerd is causing it? Does removing (or commenting everything in) /etc/logrotate.d/cobblerd_rotate fixes the problem? I rm'ed /etc/logrotate.d/cobbler* yesterday and did not get the problem last night for the first time in a long time. It's possible that the problem with the cobbler logs is now fixed as I just checked and the cobbler that is installed on this system is quite old - 2.0.3.1-3.el5 from EPEL and there is a much newer one available. Since it isn't used any more, I have just disabled it for now. I just figured I'd report what appeared to be the same Fedora bug also affecting EL. I will try to reproduce it on RHEL5, thanks for help so far. Hm, it works for me correctly on latest RHEL5 with latest cobbler from EPEL. Could you please try it with latest cobbler package? Since there is no response for longer time and I'm not able to reproduce it with latest versions available, I'm closing this bug. |
Description of problem: Logrotate on RHEL 5.7 seems to have the bug described by Fedora bugzilla 517321 and 542538 Version-Release number of selected component (if applicable): logrotate-3.7.4-12 How reproducible: Every night if you have an error in your logrotate config Steps to Reproduce: 1. Install logrotate 2. Install e.g. cobblerd and never run the daemon so the log files are non-existent 3. Wait for overnight Actual results: Get error message in logs e.g. Oct 3 04:02:05 dmckenzie logrotate: ALERT exited abnormally with [1] plus a mail saying something like error: stat of /var/log/cobbler/tasks/*.log failed: No such file or directory Now ps fax shows forever until killed 3493 ? Ss 0:03 crond 9467 ? S 0:00 \_ crond 9468 ? Ss 0:00 \_ /bin/bash /usr/bin/run-parts /etc/cron.daily 9901 ? S 0:00 \_ awk -v progname=/etc/cron.daily/logrotate progname {????? print progname ":\n"????? progname="";???? }???? { print; } Expected results: No logrotate hang Additional info: duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=517321