I am getting an extremely large trouble with a website performance. It is a php site on Apache on Home windows Server 2003.

Site is essentially crashes with 'connection was reset' or 'cannot load web page' quite frequently. httpd process in Home windows takes about 100mb on normal traffic, getting about 1gb of memory still free

This really is very first time I host a php site on Home windows (Home windows was requirement within this situation) and I am unsure what exactly are my options

Thanks

Apache log is exhibiting the next (sorry for pasting it like this, could not get it done as 'code block' from some reason. This surely does not look right. Any ideas what is happening?

[Tue November 08 16:44:43 2011] [notice] Parent: Received restart signal -- Restarting the server.

[Tue November 08 16:44:43 2011] [notice] Child 2072: Exit event signaled. Child process is ending.

httpd.exe: Couldn't dependably determine the server's properly accredited domain title, using 192.168.67.1 for ServerName

[Tue November 08 16:44:44 2011] [notice] Apache/2.2.17 (Win32) mod_ssl/2.2.17 OpenSSL/.9.8o PHP/5.2.17 set up -- returning to normal procedures

[Tue November 08 16:44:44 2011] [notice] Server built: March 18 2010 01:58:12

[Tue November 08 16:44:44 2011] [notice] Parent: Produced child process 7692

httpd.exe: Couldn't dependably determine the server's properly accredited domain title, using 192.168.67.1 for ServerName

httpd.exe: Couldn't dependably determine the server's properly accredited domain title, using 192.168.67.1 for ServerName

[Tue November 08 16:44:44 2011] [notice] Child 2072: Launched the beginning mutex

[Tue November 08 16:44:44 2011] [notice] Child 7692: Child process is running

[Tue November 08 16:44:44 2011] [notice] Child 7692: Acquired the beginning mutex.

[Tue November 08 16:44:44 2011] [notice] Child 7692: Beginning 1000 worker threads.

[Tue November 08 16:44:44 2011] [notice] Child 7692: Beginning thread to listen on port 2090.

[Tue November 08 16:44:44 2011] [notice] Child 7692: Beginning thread to listen on port 8011.

[Tue November 08 16:44:44 2011] [notice] Child 7692: Beginning thread to listen on port 8080.

[Tue November 08 16:44:44 2011] [notice] Child 7692: Beginning thread to listen on port 443.

[Tue November 08 16:44:44 2011] [notice] Child 7692: Beginning thread to listen on port 80.

[Tue November 08 16:44:45 2011] [notice] Parent: child process left with status -- Restarting.

httpd.exe: Couldn't dependably determine the server's properly accredited domain title, using 192.168.67.1 for ServerName

Home windows event viewer is tossing the next

Error - VsJITDebugger. An unhandled win32 exception happened in httpd.exe [4416]. Just-In-Time debugging this exception unsuccessful using the following error: Debugger couldn't be began because no user is drenched on.


Can anybody assist with this?

That '[notice] Parent: child process left with status -- Restarting' is explaining the problem here. Tho it describes it in vary vague way. Server is essentially restarting by itself every couple of minutes. I required the website lower having a holding page and also the error and restart ddidn't occure. I added an html page and bombed it with mixtures of demands using AB. It might always crash at demands near to quantity of ThreadsPerChild specified by mpm config, which i've set to 1000. Each crash adopted by having an error

apr_socket_recv: A current connection was intentionally closed through the remote host. (730054)

That error only shows when benchmarking. Nothing beats that seems in apache log. Just I switch the website back live, it begins to crash every couple of minutes. The website creates about 100 demands per page and it is using 2-3 ajax calls per page (while loading)

I spent hrs searching the net for possible solutions. Found nothing that matches. I am completely from options. I am not really experienced running apache on home windows as throughout five years Sometimes in the industry I never needed to run php sites on Home windows. I've not seen such error on linux neither

You will find two places best places to take a look:

  • Regular Apache logs, situated within the logs folder inside Apache installation.
  • Home windows event viewer, situated in Home windows user interface

Particularly, the 2nd you will log Apache crashes and can possibly reveal additional particulars.