Has anyone else had the problem of getting a red cpu status of "Load is CRITICAL!" with the process list showing a Xymon process of rpm being the top user of CPU resources? I looked all over the source code and don't see anywhere that Xymon is using the rpm command to do anything. Since this is a "canned" status on a running system, not on a system where Xymon is being built, for example, this is obviously a default process, but where is it coming from?
Thanks,
David
Has anyone else had the problem of getting a red cpu status of "Load is CRITICAL!" with the process list showing a Xymon process of rpm being the top user of CPU resources? I looked all over the source code and don't see anywhere that Xymon is using the rpm command to do anything. Since this is a "canned" status on a running system, not on a system where Xymon is being built, for example, this is obviously a default process, but where is it coming from?
Thanks,
David
Xymon isn't running the rpm process...xymon is alerting you to the fact that your CPU is pegged, and that the rpm process appears to be at the top of the CPU hogging process list.
You'll want to look in your crontabs, your cron.d and cron.daily jobs, etc, to determine just what is calling rpm and why.
-- Mike Burger http://www.bubbanfriends.org
"It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
On Sunday, September 8, I'll be participating in the Spokes of Hope ride, to raise money for cancer awareness and make a difference in the lives of cancer victims and their families/friends. If you'd care to donate, please click:
Thank you.
On Wed, August 7, 2013 2:41 pm, Mike Burger wrote:
Has anyone else had the problem of getting a red cpu status of "Load is CRITICAL!" with the process list showing a Xymon process of rpm being the top user of CPU resources? I looked all over the source code and don't see anywhere that Xymon is using the rpm command to do anything. Since this is a "canned" status on a running system, not on a system where Xymon is being built, for example, this is obviously a default process, but where is it coming from?
Thanks,
David
Xymon isn't running the rpm process...xymon is alerting you to the fact that your CPU is pegged, and that the rpm process appears to be at the top of the CPU hogging process list.
You'll want to look in your crontabs, your cron.d and cron.daily jobs, etc, to determine just what is calling rpm and why.
There's nothing in either the Terabithia RPM or the default RPM (that I know of) that would call the 'rpm' command itself. And an install that went awry would be running as the root user, not the xymon user.
Can you post the specific command (or ps line) in question?
Regards,
-jc
On 07-08-2013 16:41, Mike Burger wrote:
Has anyone else had the problem of getting a red cpu status of "Load is CRITICAL!" with the process list showing a Xymon process of rpm being the top user of CPU resources? I looked all over the source code and don't see anywhere that Xymon is using the rpm command to do anything.
Xymon isn't running the rpm process...xymon is alerting you to the fact that your CPU is pegged, and that the rpm process appears to be at the top of the CPU hogging process list.
Actually, it could be running out of Xymon - but it is not a standard feature of the Xymon packages that I know of.
If it really is the xymon user running the rpm command, then check for an add-on script that triggers this. My guess would be something running "rpm -Va" as a "poor-man's integrity check".
tasks.cfg or clientlaunch.cfg is probably a good place to start.
Regards, Henrik
participants (4)
-
cleaver＠terabithia.org
-
dewelker＠gmail.com
-
henrik＠hswn.dk
-
mburger＠bubbanfriends.org