Red Hat Bugzilla – Bug 1306385
/etc/cron.hourly/miq_top_hourly calls /bin/miqtop which does not exist
Last modified: 2017-08-30 04:02:48 EDT
Description of problem:
/etc/cron.hourly/miq_top_hourly calls /bin/miqtop which does not exist. /bin/miqtop.sh does exist. On CF 3.2 this appears to break the ability for top_output.log and vmstat_output.log processes from restarting automatically hourly.
Version-Release number of selected component (if applicable):
Install a current 3.2 appliance
Steps to Reproduce:
1. view /etc/cron.hourly/miq_top_hourly
2. try to run command from last line without redirecting stdout and stderr
3. view /bin/miqtop.sh and note error there as well for creation of cron job.
If top or vmstat logging processes die, they do not restart.
If top of vmstat logging processes die, the cron job will restart them.
This process appears to have been reworked in 4.0. Not sure what restarts the processes there at this point, but there's no incorrect entry in the cron file and the cron file has been renamed.
For version 5.5 these services were broken out into systemd units and the timestamp functionality was left as a cron job.
Systemd allows for options to restart services if they exit with a failure state.
This change can be made for 5.5 and upstream.
For 5.4 we can fix the typo in the file, and that should fix the issue.
New commit detected on ManageIQ/manageiq-appliance/master:
Author: Nick Carboni <email@example.com>
AuthorDate: Wed Feb 10 14:57:13 2016 -0500
Commit: Nick Carboni <firstname.lastname@example.org>
CommitDate: Wed Feb 10 14:57:13 2016 -0500
Added Restart directive for miqtop and miqvmstat services
This tells systemd to restart these services if they exit uncleanly
COPY/usr/lib/systemd/system/miqtop.service | 1 +
COPY/usr/lib/systemd/system/miqvmstat.service | 1 +
2 files changed, 2 insertions(+)
Killing the processes (kill -9) running miqtop and miqvmstat (can be found via `systemctl status <service>`) should cause them to be restarted automatically (can be seen in the logs yielded with `journalctl -u <service>`)
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.