Based on a previous question, I installed ipmitool (yum install ipmitool).
Even after a reboot, though, i get the following error when trying to run ipmitool power status:
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
Unable to get Chassis Power Status
Is this an OS/hardware issue (CentOS 6.3 x64 on a hosted machine in a remote datacenter - unsure on hardware vendor)? Or have I missed something more elemental in installing ipmitool?
I'm looking for a way to kill all processes with a given name that have been running for more than X amount of time. I spawn many instances of this particular executable, and sometimes it goes into a bad state and runs forever, taking up a lot of cpu.
I'm already using monit, but I don't know how to check for a process without a pid file. The rule would be something like this:
kill all processes named xxxx that have a running time greater than 2 minutes
How would you express this in monit?
Are there any tools to explore what is currently cached inside a memcached pool? Not some much graphs, but the actual key/values currently stored.
By default, htop shows colored status bars for processors, memory, and swap. From left to right, the bars are colored green, blue, yellow, and red depending on some thresholds.
What does it mean when the Memory bar has a small level of green and blue, and almost all the remainder is yellow? The swap bar is empty. The color settings for htop are "default".
For a more comprehensive list of monitoring tools and their features, check out this Wikipedia page.
As the question states, what are the most commonly used tools used for this task and what are their strengths and weaknesses?