Why am I getting ?high? CPU load?
Hi,
My server load sits constantly at ~3.0 and I am wondering if this is abnormally high for a fairly low traffic server running Apache 2.0.40, Postfix 1.12 with MailScanner, MySQL 3.23.58, SSH for SFTP transfers, SQUID 2.4 with DansGuardian and SAMBA 2.27 as a print server (last 3 only available on my LAN). These do not undergo a high usage. I am running RH8.0 and I am running web stats updates once an our which trawls through the web server logs for 3 sites and produces static pages via a perl script, this takes 6 minutes to complete for all three sites. This is a typical uptime command output: Code:
$ uptime Quote:
I have been scratching :scratch: my head about the load issues and am unsure if this is abnormal or not. TIA |
What does top show you as the most active process(es)? Remember that you load is a function of how active the CPU is and how long the waiting process list is. If you are running a lot of processes this will make you load higher as they're all waiting for the same cpu(s).
cheers Jamie... |
Quote:
Quote:
|
hm...
What's with the defunct mf_wrapper? not too sure what that is. You have 2 dhclients running, don't know if this is necessary. Why's there an rpm process? And cups is usually for printers (i believe) if you killed your printer, you can disable this process. |
i have (had) two printers on the machine. One parallel one USB, now i have one Parallel. Can you give me some quick guidance about how to use kill?
TIA |
There are definitely better more efficient ways, but to kill a process, i do
"ps -aux | grep <process>" where process is the name of the process...then see what the process ID is. Then "kill <pid>", and do "ps -aux" again. If the process is still there and remains very stubborn, do "kill -KILL <pid>" that really kills them. |
wat are the more efficient ways?
|
Don't know. do "man kill" and "man grep" and "man ps" for more info. I know that there are many different ways to show only the pid of a process, and pipe that to kill, therefore only needing one command instead of 2 or 3, but the syntax is too complicated to remember, so I don't remember it.
|
LOL, Cool, thanks for the help... going to murder some processes :p
|
why why why isnt this working.. i do following:
Code:
[root@linux-hoster admin]# ps -aux | grep lpd Would a 'soft' reboot help... do i do that by dropping to init 1 then back to init 3? TIA |
Quote:
Code:
killall lpd Code:
kill `ps -ef | grep [l]pd | awk '{ print $2 }' | tr "\n" " "` In case you were wondering ps -ef | grep [l]pd | awk '{ print $2 }' show the process list (ps), grep's out lines that contain 'lpd' but does't match the grep process itself (otherwise you kill grep before you search has finished!), then uses awk to print out the second column of each line which is the process ID. The tr "\n" " " changes the newlines into spaces so you get a list that can be fed into the kill command; this last bit might not be strictly necessary I'm not 100% sure how kill will interpret new lines inbetween it's list of pids. cheers Jamie... |
even with that the process is being extremely stubborn and wont die! As i ask before, would a soft reboot do it? (init 1)
|
I'm having a similar problem with acroread. From time to time, it somehow remains in the memory, and eats all the cpu time (99.9%). I just can't kill it. I thought it might have to do with other processes depending on it, but pstree shows that it's an independent process. I would be very glad if someone could tell me why this is happening, and how it can be solved... (By the way, I'm using an SMP kernel 2.4 on a P-IV with hyperthreading - I've no idea whether this could have something to do with it.)
|
try a kill with -9.
This sends it a much nastier death threat. |
Yes yes yes, tried all that. Doesn't work, not as regular user, and not as root. It's a -really- nasty process. (In case you're wondering, it's not a zombie process either, it's a real, running process.)
|
All times are GMT -5. The time now is 12:14 AM. |