crashes every Sunday like a clockwork
Here's a weird data point for you. I have an ubuntu server, probably version 8
or 10, that has a few rails sites running under lighttpd. It used to crash
every two or three weeks at the same time. Guess what time it crashed.
I never did track it down, I'd just
Here's a weird data point for you. I have an ubuntu server, probably
version 8 or 10, that has a few rails sites running under lighttpd. It
used to crash every two or three weeks at the same time. Guess what time
it crashed.
I never did track it down, I'd just restart it and go to church.
On 03/10/2013 08:18 PM, Toth, Csaba wrote:
Our lab's web server at Vandy crashes every Sunday at 7:41am exactly.
Interesting, my Debian did the same thing about 5 years ago for a
few weeks. Update took care of it.
--
Jerry Perkins
Home page http://jperkins.us html://jperkins/us
On 3/10/13 9:18 PM, Toth, Csaba wrote:
Hey Linux Gurus,
I wonder about your advices how I can solve this.
Our lab's web server at Vandy crashes every Sunday at 7:41am exactly.
I cannot track down the culprit. It's an Ubuntu Server Edition 12.04.1
LTS Precise.
Apache has php5 and even Drupal. We
Hey Linux Gurus,
I wonder about your advices how I can solve this.
Our lab's web server at Vandy crashes every Sunday at 7:41am exactly.
I cannot track down the culprit. It's an Ubuntu Server Edition 12.04.1 LTS
Precise.
Apache has php5 and even Drupal. We don't use Drupal and very little php.
On Sun, Mar 10, 2013 at 8:26 PM, andrew mcelroy sophri...@gmail.com wrote:
On Sun, Mar 10, 2013 at 8:18 PM, Toth, Csaba csaba.t...@vanderbilt.edu
wrote:
Hey Linux Gurus,
I wonder about your advices how I can solve this.
Our lab's web server at Vandy crashes every Sunday at 7:41am exactly.
First thing I would try is removing PHP. If you are not using it that much
why suffer the security issues? Depending on how it is being use can you
move that functionality to a standard cgi process? If you can't remove it,
implement modsecurity to see if that does anything to help.
Are you sure
Try restarting apache yourself and check the logs. It is possible
something is cycling apache (maybe for log rotation) and that FastCGI is
preventing it from closing down cleanly. If you restart apache yourself and
get the same error, it should lead you down the right path.
I will second
What about trying to renice the task before the other routines get the
chance to get a lot of CPU time?
It does sound strange that it would crash on a predictable basis.
If Drupal is not being used, I would consider trying to remove it and
see what happens.
Dave
On Mon, 2013-03-11 at 01:18
