Description of problem: Regression in the way that we show the top_output.log. We are only showing ruby and not the process names which makes it difficult to troubleshoot issues. Based on the code it seems that we only do a: top -b -d 60 and not, top -b -c -d 60. Example: Showing Ruby processes: top - 09:16:35 up 2 days, 21:18, 0 users, load average: 0.04, 0.03, 0.05 Tasks: 220 total, 1 running, 219 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.0 us, 0.3 sy, 0.2 ni, 98.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 12137824 total, 6612580 free, 4356620 used, 1168624 buff/cache KiB Swap: 9433084 total, 9433084 free, 0 used. 7454908 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 8739 root 20 0 702560 348380 7764 S 4.6 2.9 166:55.63 ruby 10670 root 30 10 656280 346400 4372 S 0.3 2.9 8:04.24 ruby 10698 root 23 3 723060 347592 3944 S 0.3 2.9 11:21.20 ruby 10689 root 21 1 666208 353940 4136 S 0.1 2.9 7:03.04 ruby 10681 root 21 1 666396 355040 4140 S 0.1 2.9 7:02.78 ruby What it should be showing: Tasks: 281 total, 2 running, 279 sleeping, 0 stopped, 0 zombie %Cpu(s): 5.7 us, 2.3 sy, 0.4 ni, 91.0 id, 0.1 wa, 0.2 hi, 0.2 si, 0.0 st MiB Mem : 14869.4 total, 8149.5 free, 5261.1 used, 1458.8 buff/cache MiB Swap: 9212.0 total, 9212.0 free, 0.0 used. 9099.0 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3934 root 20 0 579952 324488 13628 S 25.2 2.1 17:19.16 MIQ Server 4398 root 21 1 592788 388468 11892 S 0.7 2.6 0:16.90 MIQ: MiqEmsRefreshCoreWorker id: 1000000000060, queue: ems_1 4447 root 30 10 718728 479864 12284 S 0.7 3.2 1:21.14 MIQ: MiqGenericWorker id: 1000000000064, queue: generic 4457 root 21 1 530104 320536 8128 S 0.7 2.1 1:16.86 MIQ: MiqPriorityWorker id: 1000000000065, queue: generic 4467 root 21 1 532380 321160 8128 S 0.7 2.1 1:16.33 MIQ: MiqPriorityWorker id: 1000000000066, queue: generic 4404 root 21 1 591576 386876 11892 S 0.3 2.5 0:17.03 MIQ: MiqEmsRefreshCoreWorker id: 1000000000061, queue: ems_1 4439 root 30 10 592296 383244 12284 S 0.3 2.5 0:44.96 MIQ: MiqGenericWorker id: 1000000000063, queue: generic 4487 root 23 3 533096 311676 7488 S 0.3 2.0 0:43.45 MIQ: MiqScheduleWorker id: 1000000000067 Version-Release number of selected component (if applicable): 5.11
https://github.com/ManageIQ/manageiq-appliance/pull/257
New commit detected on ManageIQ/manageiq-appliance/master: https://github.com/ManageIQ/manageiq-appliance/commit/4cc7212ba1c75109deb3fede8952c56fa3a90e7c commit 4cc7212ba1c75109deb3fede8952c56fa3a90e7c Author: Joe Rafaniello <jrafanie> AuthorDate: Tue Sep 10 14:09:11 2019 -0400 Commit: Joe Rafaniello <jrafanie> CommitDate: Tue Sep 10 14:09:11 2019 -0400 Run top in command-line/program name mode Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1749494 In rhel/centos 7, procps-ng version 3.3.10, top would run in command-line mode without a .toprc. With rhel/centos 8, 3.3.15, top does NOT run in command line mode by default so you must specify it. Previously, we would see the proc title we set instead of "ruby". See also: https://gitlab.com/procps-ng/procps/issues/6 LINK/usr/bin/miqtop.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Apparently, procps-ng-3.3.10-26 upgraded "top" and defaults to the non-command line format which shows just "ruby". procps-ng-3.3.10-23 was fine so it's very likely older versions such as 5.10 need to get this change. Added hammer/yes on upstream PR