Apache Crashing?

[Unborn]

Hi guys.
About every 10 minutes or so, Apache just stops and I have to start it again manually.

In it's error logs, I get this message:

Code: Select all

[Sun Jan 25 14:37:07 2009] [notice] Parent: child process exited with status 3221225477 -- Restarting.


However, It doesn't restart.

I'm only using XAMPP for running Apache/PHP/etc, No MySQL or FTP.
I'm using the default settings with the exception of a modified document root and vhosts.

If someone could please help me figure out why it keeps crashing, or even tell me how to enable automatic restarting after a crash I would greatly appreciate it.

Thank you
Unborn

[Izzy]

What OS and what version of XAMPP?

Go to start>Administrative Tools>Event Viewer>Application and look for any clues, also click on System to see if there are any clues in there - Double click on the red X or the Information to see the error messages.

[Unborn]

Windows Server 2008 Standard (32-bit), and the latest version of XAMPP (1.7.0, I think).

The event viewer does contain logs of apache.exe crashing, but I have absolutely no idea what it describes:

Code: Select all

Log Name:      Application
Source:        Application Error
Date:          1/25/2009 5:32:11 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      WIN-ZPJ839X91DM
Description:
Faulting application apache.exe, version 2.2.11.0, time stamp 0x493f5d44, faulting module kernel32.dll, version 6.0.6001.18000, time stamp 0x4791a76d, exception code 0xc0000005, fault offset 0x000bf285, process id 0x67c, application start time 0x01c97ec75d29ca50.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-01-25T08:32:11.000Z" />
    <EventRecordID>569171</EventRecordID>
    <Channel>Application</Channel>
    <Computer>WIN-ZPJ839X91DM</Computer>
    <Security />
  </System>
  <EventData>
    <Data>apache.exe</Data>
    <Data>2.2.11.0</Data>
    <Data>493f5d44</Data>
    <Data>kernel32.dll</Data>
    <Data>6.0.6001.18000</Data>
    <Data>4791a76d</Data>
    <Data>c0000005</Data>
    <Data>000bf285</Data>
    <Data>67c</Data>
    <Data>01c97ec75d29ca50</Data>
  </EventData>
</Event>


When looking under system, all it tells me is that it has crashed 8 times.

[Izzy]

One of the suggested fixes was to add this line to the bottom of the httpd.conf file:
Win32DisableAcceptEx
Save the file and restart Apache and try again to see if your issue returns.

Not seen many with the kernel fault, usually it is a dll at fault.

If you want some heavy reading about this I did a Google search just looking for the kernel issue.

A forum search here reveals the dll issues but only one result with the kernel issue and no fix offered.

Try the above and reboot your PC and see if it continues to intermittently crash whilst waiting to see if any other members have had similar problems and know of a more positive fix.

Sorry I can't be much more help to you.

[Unborn]

Thanks for your help.

After reading through some of the pages returned by your Google search, It appears to be a problem with PHP.
I traced the crash to 2 scripts, and after some debugging found that the crash doesn't seem to occur when I don't manually close MySQL Sockets with mysql_close().
I am now leaving PHP to close the sockets automatically when the script terminates, and it hasn't crashed since.

If it does start to crash again I will try the suggestion you pointed out of disabling AcceptEx, but I'll keep it enabled for now as the documentation states that it can provide better performance.

[Izzy]

Thanks for posting back with some positive results that I hope may help others with a similar issue when searching the forums.

I hope it holds and your fix is successful.

Good luck.

[Harmalicious]

This setting, Win32DisableAcceptEx, corrected the issue I was having with multiple .dll issues which included the issue noted in the original post.