that would be a VERY bad idea.
it would (if it works) kill sshd but leave the box running -> no way to access it remotely anymore.
however i've already issued a "reboot" command nearly 20h ago.
who knows maybe the server will reboot at some point but right now I think that only a hard reset will get it running again.
Or, next time everything works fine, you write down on a piece of paper the id of the Apache process. Like this, no need to do a ps when something bad happens, you can directly kill it.
Hint of advice. Next time run apache with a Nice level (something like 10+) if it keeps overtaking the CPU usage. By doing so you will still be able to SSH in.
Another thing to consider is running a cron script to check the CPU usage of Apache and if it stays at 99% or greater for more than an hour just have it kill and restart apache.
Oh dear.. Too bad that apache is going berserk... killall httpd (maybe not) or killall apache2 (maybe better) would do something
I wonder if updating apache would fix something, but of course that depends on accessmethods to server (I mean, if updating it is possible by admins accessing server via ssh and if there is new version of apache available atm).
Hope that reboot-command doesn't take too many hundreds of days to process
Take your time. We'll wait
oh well only one thing to do, gotta start taking bets on when it will be back up ^^
So very glad i decided to download AOM just before it went down i have nfi how i would be able 2 keep track of my downloads without it. tho i still prefer to use the webbie over AOM.
After a restart the server is running fine again.
You might still notice short downtimes every now and then today and this WE as I am making some updates.