Forum Moderators: phranque
Server: Homebuilt computer with AMD Athlon cpu, 512mb DDR ram, Western Digital 80 gig hd (NTFS format), motherboard (Mainboard K7S5A) has builtin NIC, video and sound cards.
OS: WinXP Pro SP2
other resident aps: ZA Pro, Ewido, Spybot S&D, TZO dynamic DNS client, AVG antivirus
java: I have the most current release of the Java Runtime Environment
online hardware: Linksys WRT54g router and Linksys cable modem
Apache version: 2.0 current release
On to my problem...
I host my own web page and blog using Thingamablog so no Perl, PHP, or MySQL needed. This ap requires the java runtime environment. I have used Thingamablog 1.5 since last year with no errors.
The web site runs for hours (no particular length of time) and then stops responding for no apparent reason. Using the Apache Monitor Console to stop and restart the server brings it back online. I get no indication of trouble from the OS. I examine my access.log every few hours and when I notice that there is a large gap of time since the last hits to the web page, I try to view it online. I get a "not available" message in my browser. After resetting the server in the Apache Monitor, I can again view the page. This started happening with the previous stable release of Apache 2.0 and continues with the current upgrade release.
I examined the apache error.log and it doesnt give me a clue.
It does NOT seem to be an Apache configuration error. It stops randomly whether I use the default settings or with my custom settings.
The server computer does not exhibit any other problems. I am able to use the browser and look at my yahoo account to reads email all the while that the web server has stopped responding. Originally I had only 256mb of ram when this started. I added another 256mb stick and everything is faster but the problem with the server continues. Could there be a glitch with the originally installed ram?
No other running applications seem to be affected by this... has there been any reports of memory leaks or anything with apache?
Any ideas? As a last resort... is there a script I could run to take apache offline and restart it at timed intervals?
We still don't know the course of the problem but we know how to temporarily solve it. We have written a bash script using cron job to restart apache server every 8 hours. It works fine for us, although we want to fix this permanently
