Hey guys,
At random points throughout the last few weeks apache started stopping for no reason. No entry in the log files. Luckily, we have scripts that monitor apache every 1 minute and restart it if its down.
Server load is not high
Bandwidth usage is normal
No errors in the log files
Apache 1.3.19
We will be upgrading apache version shortly but we are stuck with it now
Anyone have any ideas? Thanks
nozol
11-30-2002, 11:06 PM
Did you check the memory usage? Perhaps you need more memory.
Ram is low but there is a ton of swap space
ChickenSteak
11-30-2002, 11:47 PM
I was experiencing this same issue on one of our p4 2ghz, 1 gb ram so it's def not the ram. I just setup monitoring as you did, only diffrence we're using apache 1.3.27.
i have this problem sometimes aswell,
maybe not as often but it does happen.
RobTheGolfer
12-01-2002, 01:40 PM
We are experiencing this problem on 2 of our servers. It isn't the RAM for us either.
tariehk
12-01-2002, 05:35 PM
Hi,
I am having the same problem. Check this thread out:
http://www.webhostingtalk.com/showthread.php?s=&threadid=89636
rkyler
12-31-2002, 04:03 PM
I got it 2! Sometimes apache will run for 2 weeks, sometimes only 2 hours, sometimes 3 days, somtimes a week??? It's all a mystery!
I've upgraded to the latest version, I havent had this problem occur again yet...
FuelGuru
12-31-2002, 06:07 PM
Nothing in /var/log/messages? Write a script to check if httpd is running and if down start the service. Set it to run every 15 mins. ;-)
Originally posted by FuelGuru
Nothing in /var/log/messages? Write a script to check if httpd is running and if down start the service. Set it to run every 15 mins. ;-)
mabey you should read the first post again.....
Originally posted by MaB
...No entry in the log files. Luckily, we have scripts that monitor apache every 1 minute and restart it if its down. ....
rkyler
12-31-2002, 06:39 PM
Yep, got it, it's a must, gotta have it, and it's a lifesaver!
AcuNett
12-31-2002, 06:39 PM
How big are your log files / suexec files? We had two problems once.
First was that the suexec log was humongous , a copule gigs I believe.
Second time was when someone at rackshack changed our hostname to rackshack.net