See that process on top - that is my problem.(see attached file)

Some of apache processes (wwwrun) just hung, and kill my processor (takeing 99% of it's use).

How can i stop it ????

maybe something in config to block processes to run more than 5 minutes or less.....

Attached Images

killing.GIF (14.6 KB, 179 views)

That is really messed up. It appears that PID 18180 and 8256 are uniteruptable for some reason and this is keeping 21692 in R state instead of S state where it should be. Is your web server running properly? Does this get a lot of traffic? What OS is this running on?

- Does this get a lot of traffic?
Last month 60GB

- OS
Apache/1.3.26
Linux/SuSE 8.2


- Is your web server running properly?
Hmm if not where i can find any solution...?
This abnormal situation happens 2 times during last week, and completly block acces to server.
I was wondering to write a script which will kill -9 that processes, but that is not a good way....


(sorry for my english, it's not my primary lang.)

No need to apologize for your english. It is much better than my usage of your native language (whatever that may be)

When this problem arises, do you kill every httpd process and then restart your apache server? Or do you just kill the processes that seem to be problematic? I have had times when I can't even kill a process with the -9 switch if it is "D". Are you able to kill these?

Have you tried a restart of apache with either:
or

Sorry for all the questions, I am just grasping in the dark really. While I use Linux/apache, I don't have near the traffic that you are talking about. The only thing that is certain is that your PID 21692 is stuck on the run queue and has been for a long long time. I am just not sure why. Is there anything that happens just prior to this happening?

Sorry for long delay...

Sometimes is not only one process, two, three...

When it happen it's hard to login as root, procesor is on 99% it's take a while
then i use:

it says it's FaIeLD, so i can only do

but it shutdown all httpd prcesses...

so i sometimes use only kill -9 pid , only for that stucked processes, and it helps too..

i was wondering is there any thing in apache configuration to cut off long working prcesses...

it had happen today....

Attached Images

kolejny.JPG (75.6 KB, 81 views)

it's going to be more and more.. .look what i saw today..9 processes that shouldn't life...

Attached Images

123.bmp (20.8 KB, 52 views)

You should check, with Apache's server-status page..

you can enable it somewhere in httpd.conf, you don't seem to be a newbie, it should work.

by visiting that page, just after the prblem starts you might be able to see if you are under an DOS attack.
I've had the problem once, apache was going crazy and crached, the problem was that a PHP-Nuke site fetched 'http://localhost/,' , which doesn't exist, it didn't get the expected result and tried again and again and again.. etc etc.

You can also check your error/access logs, but that can be a pain on shared servers with logs everywhere

__________________
Pastebin
PHP Documentation Site
Allowee's Blog http://allowee.net