Apache Friends Support Forum

Yesterday I upgraded XAMMP from 1.7.2 to 1.7.3. Since the upgrade Apache shuts down when you try to view a local url. It start and stays running until you try to connect. I checked the logs and there is nothing in them about the shutdown. Running on Windows XP Pro

I checked the logs and there is nothing in them about the shutdown.

Unless your machine re-booted I find that a bit hard to believe - but hey its a 'puter, so anything could happen.

You should look in your system and application event logs if Apache's error.log REALLY has no releveant info. It proabably worth posting the last few entries from error.log anyway...

Good Luck

I uninstalled XAMMP then did a reinstall and have the same problem. Now something is showing up in the logs. Also, my firewall says that apache is shutting down httpd.

[Tue Nov 30 21:20:35 2010] [notice] Child 440: Child process is running
[Tue Nov 30 21:20:35 2010] [crit] (OS 10022)An invalid argument was supplied. : Parent: WSADuplicateSocket failed for socket 25941584. Check the FAQ.
[Tue Nov 30 21:20:35 2010] [crit] (OS 10022)An invalid argument was supplied. : master_main: create child process failed. Exiting.
[Tue Nov 30 21:20:35 2010] [notice] Parent: Forcing termination of child process 36
[Tue Nov 30 21:20:35 2010] [crit] (OS 109)The pipe has been ended. : setup_inherited_listeners: Unable to read socket data from parent

Also, my firewall says that apache is shutting down httpd.

That's because Apache (httpd.exe) thread safe is actually two processes when running properly on Windows. And the worker/'child' signalled for a graceful shutdown.

Because Apache for Windows is multithreaded, it does not use a separate process for each request, as Apache can on Unix. Instead there are usually only two Apache processes running: a parent process, and a child which handles the requests. Within the child process each request is handled by a separate thread.

http://httpd.apache.org/docs/2.2/platform/windows.html

First - are you using mod_perl for anything??? If not - try disabling it with the setup_xammp.bat or Setup in the XAMPP Control Panel. Its quirky and might be the cause.

If Apache is a service, you will want to reboot prolly, and see if everything is smiley

If that's not a fix -

Ok - its an upgrade - Did you move your files back into the document root?

Also possible you have a corrupt TCP/IP STACK (there's a non-destructive fix)

All just 'thoughts' at the moment.

Good Luck

Something turned on windows firewall and it was blocking Apache.

OK - cool

thanks for posting what the resolution was, I wan't thinking along those lines - SOOO I need to revise my FAQ to include - check the statuts of the Windows Firewall.