Bug 1306385 - /etc/cron.hourly/miq_top_hourly calls /bin/miqtop which does not exist
/etc/cron.hourly/miq_top_hourly calls /bin/miqtop which does not exist
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
Unspecified Unspecified
high Severity high
: GA
: 5.6.0
Assigned To: Nick Carboni
luke couzens
: ZStream
Depends On:
Blocks: 1306430 1306433
  Show dependency treegraph
Reported: 2016-02-10 12:05 EST by Jeffrey Cutter
Modified: 2017-08-30 04:02 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1306430 1306433 (view as bug list)
Last Closed: 2016-06-29 11:37:29 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeffrey Cutter 2016-02-10 12:05:32 EST
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):

How reproducible:

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.

Actual results:

If top or vmstat logging processes die, they do not restart.

Expected results:

If top of vmstat logging processes die, the cron job will restart them.

Additional info:

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.
Comment 2 Nick Carboni 2016-02-10 14:55:14 EST
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.
Comment 4 CFME Bot 2016-02-10 16:43:46 EST
New commit detected on ManageIQ/manageiq-appliance/master:

commit ec48b862022c0adfe2d5aaadd54cdcdc1ee549da
Author:     Nick Carboni <ncarboni@redhat.com>
AuthorDate: Wed Feb 10 14:57:13 2016 -0500
Commit:     Nick Carboni <ncarboni@redhat.com>
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(+)
Comment 6 Nick Carboni 2016-04-28 08:37:43 EDT
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>`)
Comment 9 errata-xmlrpc 2016-06-29 11:37:29 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.