I have seen in the past from various companies products graphs which plot memory usage by process, so you can see which process is using the most memory. In addition, there have been CPU usage per process graphs as well. Seeing the below made me think about the memory/per process.
I tried the ps vax command on both an AIX and Redhat box and both worked. Would it be possible to implement this sort of a graph in hobbit?
-Jeff
On 5/1/06, Michael Lowery <mlowery at alliedtechgroup.com> wrote:
Ok, I don't have a clear understanding of the memory check. I do understand what has been discussed, but I have a Redhat 9 where the "actual" memory utilized is 96%. However, when I run: ps vax --sort -rss, I get the following. It looks like my actual memory usage shouldn't be at 96%, is this correct?
PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND 2916 ? SL 0:00 470 298 2093 2388 0.9 [ntpd] 2948 pts/1 R 0:00 187 66 2561 684 0.2 ps vax --sort -rss 2690 ? S 0:00 11252 265 6594 612 0.2 /usr/sbin/sshd 2692 pts/1 S 0:00 2666 588 3775 604 0.2 -bash 891 ? S 3:15 30426 24 1415 100 0.0 syslogd -m 0 31227 ? S 0:00 50692 33 1374 60 0.0 /home/hobbit/client/bin/hobbitlaunch --config=/home/hobbit/client/etc/client 1 ? S 0:04 28806 23 1352 36 0.0 init 2878 ? S 0:00 7714 131 4480 36 0.0 [nqmgr] 2885 ? S 0:00 4231 190 4481 16 0.0 [smtpd] 2902 ? S 0:00 2566 130 4485 16 0.0 [cleanup] 895 ? S 0:00 124 18 1349 4 0.0 klogd -x 1029 ? S 0:01 520 265 3238 4 0.0 /usr/sbin/sshd 1043 ? S 0:00 97 129 1890 4 0.0 xinetd -stayalive -reuse -pidfile /var/run/xinetd.pid 1142 ? S 0:00 340 56 1347 4 0.0 gpm -t ps/2 -m /dev/psaux 1151 ? S 0:00 42450 19 1404 4 0.0 crond 1185 tty1 S 0:00 98 6 1345 4 0.0 /sbin/mingetty tty1 1186 tty2 S 0:00 98 6 1345 4 0.0 /sbin/mingetty tty2 1187 tty3 S 0:00 98 6 1345 4 0.0 /sbin/mingetty tty3 1188 tty4 S 0:00 98 6 1345 4 0.0 /sbin/mingetty tty4 1189 tty5 S 0:00 98 6 1345 4 0.0 /sbin/mingetty tty5 1190 tty6 S 0:00 98 6 1345 4 0.0 /sbin/mingetty tty6 31309 ? S 0:10 185817 16 9287 4 0.0 /usr/sbin/snmpd -s -l /dev/null -P /var/run/snmpd -a 2941 ? S 0:00 473 588 1447 4 0.0 sh -c vmstat 300 2 1>/home/hobbit/client/tmp/hobbit_vmstat.2930 2>&1; mv /ho 2943 ? S 0:00 118 7 1408 4 0.0 vmstat 300 2 2 ? SW 0:00 0 0 0 0 0.0 [keventd]
Thanks, Michael
-----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Wednesday, February 08, 2006 9:47 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Memory check
On Wed, Feb 08, 2006 at 09:26:31AM -0500, David Gilmore wrote:
Ok I understand the concept. However, I don't want to continue to receive Alerts because Linux is doing exactly what it is designed to do. Does anyone have a script that can clear the buffers and stop hobbit from paging me? Can I modify the script to only alert when REAL memory is at 100% or higher? Or do I have to reboot my server ever morning to resolve this alert? I currently have the alerts disabled, but I am concerned that I could miss a critical error
Assuming that you're using the Hobbit client on the Linux box, you can just configure the client to only go red if the actual memory usage goes above a certain threshold. In your hobbit-clients.cfg, you would have
HOST=linux.foo.com MEMPHYS 100 101 MEMACT 80 95 MEMSWAP 40 70
Then it will stay green as long as the "actual" memory usage is below 80%, go yellow when it's between 80-95%, and go red when it is at 95% or higher.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk