Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1271668 - top_output log missing datetime stamp
top_output log missing datetime stamp
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
5.5.0
Unspecified Unspecified
medium Severity medium
: GA
: 5.5.0
Assigned To: Nick Carboni
Kyrylo Zvyagintsev
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-14 09:14 EDT by Dave Johnson
Modified: 2015-12-08 08:38 EST (History)
4 users (show)

See Also:
Fixed In Version: 5.5.0.7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-12-08 08:38:28 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2551 normal SHIPPED_LIVE Moderate: CFME 5.5.0 bug fixes and enhancement update 2015-12-08 12:58:09 EST

  None (edit)
Description Dave Johnson 2015-10-14 09:14:26 EDT
Description of problem: the vmstat_output.log in the vmdb/log directory should have an miqtop log line at the beginning of each hour so that we can keep good alignment with the top_output data.  the vmstat log lines are intended to be generated each 60 seconds, but without the “guidepost” miqtop log lines there is no meands to detect and correct TOD drift.

Version-Release number:  5.5.0.1-beta1
How reproducible: 100%

Actual results: no miqtop log lines are visible at all in the vmstat_output.log file

Expected results:expected to see miqtop log lines at the beginning of each hour
Comment 5 errata-xmlrpc 2015-12-08 08:38:28 EST
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://access.redhat.com/errata/RHSA-2015:2551

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