Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My server has been crashing, a quick check of ps aux shows:

 root     11905 95.5 55.0 1151616 1135256 pts/0 R+   09:05  40:38 vim error_log

Surely this can't be right? Am I reading this right? This seems to be very dire!

If this is really using 95% cpu and 55% memory then how can I stop it/fix it?


share|improve this question
up vote 4 down vote accepted

A very large file is being opened with vim, a text editor. To stop vim, kill it (PID taken from the second column of ps aux):

kill 11905

When checking log files, I suggest you to use less instead as you do not need fancy editing features:

less error_log
share|improve this answer
I normally use cat. Ah cool, kill has stopped it. Could that be what's causing the out of memory errors? – Thomas Clayson Feb 14 '12 at 10:31
Also, I figured error_log was the apache error log which was MAHOOSIVE! So I also deleted that. – Thomas Clayson Feb 14 '12 at 10:31
Other useful tools for log analysis are tail, uniq and grep. See their manpages for more information. – Lekensteyn Feb 14 '12 at 10:36
Ah brilliant, thank you. I'm primarily a programmer, and have a basic understanding of the hardware/server side of stuff, but stuff like this I'm still learning about and stumbling upon when I have issues like this. Thanks for your help and insight. :) Very useful – Thomas Clayson Feb 14 '12 at 10:39

You need also restart apache, or it continues to log to the deleted file.

share|improve this answer
cool :) i did that anyway. – Thomas Clayson Feb 14 '12 at 14:38

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.