Bob Crandell wrote:
I put a cron job that restarted httpd about 2 or 3 AM until I had
time to figure out what was going on. I figured if anyone was using
it then they would be so groggy they wouldn't know if it was them or
what.
You were lucky all the site's users were in the same time
Luck?
No luck.
Careful planning. ;^)
Bob Miller ([EMAIL PROTECTED]) wrote*:
Bob Crandell wrote:
I put a cron job that restarted httpd about 2 or 3 AM until I had
time to figure out what was going on. I figured if anyone was using
it then they would be so groggy they wouldn't know if it was
On Fri, Dec 13, 2002 at 04:04:25PM -0800, Bob Miller wrote:
I made small changes, because he was wanting to test for a timeout,
not any ol' error.
#!/usr/bin/perl
use strict;
use LWP::UserAgent;
use HTTP::Status;
sub check() {
my $ua =
Thanks, this is something I can play with too.
TimH
On Sat, 14 Dec 2002 00:50:04 -0800
Jacob Meuser [EMAIL PROTECTED] wrote:
On Fri, Dec 13, 2002 at 04:04:25PM -0800, Bob Miller wrote:
I made small changes, because he was wanting to test for a timeout,
not any ol' error.
I have a heavily used web server that has been deciding to simply stop serving pages
for up to 20 minutes at a time... I have already tried all manner of Apache and OS
tweeks to stop this but nothing seems to work. Restarting the server puts everything
back on track. What I would like to do,
Without having the answer you may want to expand on if 'Restarting the
server' means rebooting or web server restart, i.e .../httpd restart.
Also, when web server slows down does a local 'lynx IP-of-interface'
behave the same?
Would a frequent cron job be able to detect, e.g. huge amount of
...
Would a frequent cron job be able to detect, e.g. huge amount of httpd
children, or other odd symptons,... and then call the reboot or httpd
restart? --there may be symptoms visible before the slowdown reaches the
extreme.
Certainly an every 15 min cron job that calls a logging script
Now that might be a workable idea... Thanks!
TimH
On Fri, 13 Dec 2002 14:03:31 -0800
Roger [EMAIL PROTECTED] wrote:
Around Fri,Dec 13 2002, at 12:12, Tim Howe, wrote:
I have a heavily used web server that has been deciding to simply stop serving
pages for up to 20 minutes at a time... I
Here's a perl script that I use to just determine if my lines and routers
are up. You can easily modify it to suit your needs. A simple system
call would restart the webserver:
system(/etc/init.d/apache stop /etc/init.d/apache start);
I run this in /etc/cron.d every minute and dump the results
example output of line_monitor.pl from logcheck:
Unusual System Events
=-=-=-=-=-=-=-=-=-=-=
Dec 13 13:25:01 neptune line_monitor.pl: www.uoregon.edu:128.223.142.13 WWW failed
This tells me I should be more tollerant with other people webservers
before determining of my line is down (ie trying a
Something is odd on efn -- 2 or 3 of my postings never made it (either
out
or back in), so I am resending.
Date: Fri, 13 Dec 2002 13:23:37 -0800 (PST)
To: [EMAIL PROTECTED]
Subject: Re: [Eug-lug]Use perl to monitor webserver?
Without having the answer you may want to expand on if 'Restarting
Tim Howe wrote:
I have a heavily used web server that has been deciding to simply
stop serving pages for up to 20 minutes at a time... I have already
tried all manner of Apache and OS tweeks to stop this but nothing
seems to work. Restarting the server puts everything back on track.
What I
I'm not ignoring the problem, I'm putting a bandaid on it until I figure out what is
really wrong. I'll play with this code.
TimH
On Fri, 13 Dec 2002 16:04:25 -0800
Bob Miller [EMAIL PROTECTED] wrote:
Tim Howe wrote:
I have a heavily used web server that has been deciding to simply
Hi,
How long does it run before it stops? How much memory are you running now? If you
type free, how much cache is being used?
A couple of the servers I built slowed way down after running a couple days but they
didn't stop like you're describing. I put a cron job that restarted httpd about 2
14 matches
Mail list logo
