Red Hat Bugzilla – Bug 1519987
Logging of the server process memory/cpu (MiqServer.log_status) is incorrect
Last modified: 2018-02-28 08:10:26 EST
New commit detected on ManageIQ/manageiq/fine: https://github.com/ManageIQ/manageiq/commit/a093979fa911b8944d362e479bef5bce7072e701 commit a093979fa911b8944d362e479bef5bce7072e701 Author: Oleg Barenboim <chessbyte@gmail.com> AuthorDate: Tue Nov 14 17:19:34 2017 +0200 Commit: Satoe Imaishi <simaishi@redhat.com> CommitDate: Fri Dec 1 16:03:40 2017 -0500 Merge pull request #16460 from jrafanie/get_server_process_info Workers can run log_status so ask for the right pid (cherry picked from commit 974e36052bdf98dc46637f821db8026295759062) https://bugzilla.redhat.com/show_bug.cgi?id=1519987 app/models/miq_server/status_management.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Milan, you need to make sure your workers have different memory/cpu times values before you can recreate it. So, perhaps, do some minor work until you have a good difference in worker memories and cpu times or force workers to restart so some have much larger cpu times. Then, check the logs and you should see the up and down nature of the logging.
You were right, Joe, thanks. Verified in 5.8.3.0 (against 5.8.2.3)
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-2018:0374