| Author |
|
ckissi
Joined: 09 Aug 2006
Posts: 6
|
 Posted: Wed 09 Aug '06 19:09 Post subject: Apache doesn't respond sometimes |
 |
|
I run Apache 2.0.50 on Windows 2003 server. The machine serves more than 400.000 pages every day (from total 9 sites). About every 5 days apache freezes. It doesn't serve any page at that time. The process seems to run , but no output from apache to user. The RAM and CPU usage seems to be OK. When I looked into logs there was nothing unusual, the last page served at 7:11AM and the next at 7:24PM (I was on vacation) when I noticed that I restarted the PC, The single apache STOP/RUN didn't help, The next time it happened STOP/START helped.
Please advice what to do or how to discover where the issue is ?
Thank you. |
|
| Back to top |
|
pnllan
Joined: 05 Dec 2005
Posts: 221
|
| Posted: Wed 09 Aug '06 19:27 Post subject: |
|
|
| Check your Access Log, and see if the last page accessed is the same before each 'lock-up'. There could be a page(s) that has some bad script in it. |
|
| Back to top |
|
ckissi
Joined: 09 Aug 2006
Posts: 6
|
| Posted: Wed 09 Aug '06 19:57 Post subject: |
|
|
| The logs contains different files on positions before freeze. But all files are with code 200 and bytes were sent to browser. |
|
| Back to top |
|
pnllan
Joined: 05 Dec 2005
Posts: 221
|
| Posted: Wed 09 Aug '06 23:26 Post subject: |
|
|
I'm not exactly sure about the cause of this. I've seen scripts iterate to infinity causing something like this, and some attacks cause this as well.
INFO U: Apache Software Foundation (ASF) now considers Apache 2.0.x as legacy, and since only limited maintenance is performed on these legacy versions - they encourage using Apache 2.2.x. They will likely only fix security flaws as they come up. |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7373
Location: Germany, Next to Hamburg
|
| Posted: Thu 10 Aug '06 10:41 Post subject: |
|
|
Even if you don't want to upgrage to 2.2.3 (which is realy recomment) upgrade to 2.0.59! There are many bugfixes.
One idea why the server maybe freeze is large file download from a Client. The old 2.0.x can only handle file with max. size of ~ 999MB |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU
|
| Posted: Thu 10 Aug '06 22:05 Post subject: |
|
|
| ckissi wrote: | | The process seems to run , but no output from apache to user. The RAM and CPU usage seems to be OK. |
Seems ? What gets the user ?
What about when you try to call a page with http://localhost ?
Can be an issue in Windows, Network, ISP. I personal do not suspect Apache, quite some of us running it for weeks/months.
For this kind of situations you can maybe see more when you run my Statistics  , see http://www.apachelounge.com/article.php?sid=39
and special http://www.apachelounge.com/stats/
Steffen |
|
| Back to top |
|
ckissi
Joined: 09 Aug 2006
Posts: 6
|
| Posted: Thu 17 Aug '06 16:36 Post subject: |
|
|
finally I ordered second machine with ThePlanet and moved all of my minor sites there , the version installed is apache 2.2.3 with PHP 5.1.4 . Now every day I get about 1 - 3 apache restarts with this message in log:
...
[Thu Aug 17 08:49:57 2006] [notice] Parent: child process exited with status 3221225477 -- Restarting.
[Thu Aug 17 08:49:58 2006] [notice] Apache/2.2.3 (Win32) PHP/5.1.4 configured -- resuming normal operations
[Thu Aug 17 08:49:58 2006] [notice] Server built: Jul 27 2006 23:19:26
[Thu Aug 17 08:49:58 2006] [notice] Parent: Created child process 5284
[Thu Aug 17 08:49:58 2006] [notice] Child 5284: Child process is running
[Thu Aug 17 08:49:58 2006] [notice] Child 5284: Acquired the start mutex.
[Thu Aug 17 08:49:58 2006] [notice] Child 5284: Starting 250 worker threads.
[Thu Aug 17 08:49:58 2006] [notice] Child 5284: Starting thread to listen on port 80.
[Thu Aug 17 08:49:58 2006] [notice] Child 5284: Starting thread to listen on port 80.
...
I made research on internet to discover what is the problem but everythin g I got is that it seems to be issue with some DLLs .
BTW in event log is this message: Faulting application httpd.exe, version 2.2.3.0, faulting module php5ts.dll, version 5.1.4.4, fault address 0x000ccd44.
I thing I'm (and all of us with this issue) want to make impossible, it's quite easy to get things work without those messages with sites that get 1000 hits/day but my overall traffic is almost 500.000 hits/day (includes robots) so I think It'll be better for me to move on linux, because I have now 2 servers with my provider and apache works better (so far) but the errors are still there. |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU
|
| Posted: Thu 17 Aug '06 21:03 Post subject: |
|
|
PHP is causing this, you can try to move the memory limit in php.ini a way up, eg:
memory_limit = 64M
The php guys have developed a new memory manager in PHP 5.2, it is still very beta, but you can give it a try at their snap net.
Btw. I know sites that has more hits and not dealing with your issue.
I should advise that you review your php scripts.
Steffen |
|
| Back to top |
|
ckissi
Joined: 09 Aug 2006
Posts: 6
|
| Posted: Fri 18 Aug '06 22:48 Post subject: |
|
|
| thanx Steffen, I changed the value to 32M , I'll wait about 3 - 4 days, it should be enough because I see this error about 2 - 4 times /day. Hope this will help. |
|
| Back to top |
|
ckissi
Joined: 09 Aug 2006
Posts: 6
|
| Posted: Sat 19 Aug '06 12:56 Post subject: |
|
|
Several hours after implementation I got 4 error messages again. So seems that it's not the right way  . I cannot review all scripts because lot of them are third party and I don't have time for that. So I decided to move to centOS which is supported by my server hosting company. If you still have some idea please let me know. I made research again and I saw that people suggest to increase memory_limit but lot of users said that it didn't help. |
|
| Back to top |
|
