Apache Service Premature Termination

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Apache Service Premature Termination

Postby howardparsons » 30. December 2009 00:14

Hello,
I am unable to start the Apache service either manually or automatically. The System error log shows the following:
The Apache2.2 service terminated unexpectedly. It has done this 9 time(s).


The last time Apache ran successfully was on 6 December, 2009. The Apache error log shows the following:
[Sun Dec 06 10:53:35 2009] [notice] Digest: generating secret for digest authentication ...
[Sun Dec 06 10:53:35 2009] [notice] Digest: done
[Sun Dec 06 10:53:36 2009] [notice] Apache/2.2.12 (Win32) DAV/2 mod_ssl/2.2.12 OpenSSL/0.9.8k mod_autoindex_color PHP/5.3.0 mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal operations
[Sun Dec 06 10:53:36 2009] [notice] Server built: Jul 22 2009 11:35:54
[Sun Dec 06 10:53:36 2009] [notice] Parent: Created child process 2144
Terminating on signal SIGTERM(15)
] Digest: generating secret for digest authentication ...
[Sun Dec 06 10:53:37 2009] [notice] Digest: done
[Sun Dec 06 10:53:38 2009] [notice] Child 2144: Child process is running
[Sun Dec 06 10:53:38 2009] [notice] Child 2144: Acquired the start mutex.
[Sun Dec 06 10:53:38 2009] [notice] Child 2144: Starting 150 worker threads.
[Sun Dec 06 10:53:38 2009] [notice] Child 2144: Starting thread to listen on port 443.
[Sun Dec 06 10:53:38 2009] [notice] Child 2144: Starting thread to listen on port 443.
[Sun Dec 06 10:53:38 2009] [notice] Child 2144: Starting thread to listen on port 80.
[Sun Dec 06 10:53:38 2009] [notice] Child 2144: Starting thread to listen on port 80.
Terminating on signal SIGTERM(15)
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs


I have tried upgrading to the latest release but no joy.

Any help/suggestions would be appreciated.

Howard Parsons
Howard Parsons
President - Parsonage Data Services
User avatar
howardparsons
 
Posts: 12
Joined: 30. January 2009 22:56
Location: Charlottesville, VA - USA

Re: Apache Service Premature Termination

Postby Wiedmann » 30. December 2009 00:19

(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down

Another program is using the Apache port 80.

Any help/suggestions would be appreciated.>

Try xampp-portcheck.
Wiedmann
AF Moderator
 
Posts: 17106
Joined: 01. February 2004 12:38
Location: Stuttgart / Germany

Re: Apache Service Premature Termination

Postby howardparsons » 30. December 2009 00:23

I've tried portcheck. Here are the results:
Service Port Status
==============================================================================
Apache (HTTP) 80 free
Apache (WebDAV) 81 free
Apache (HTTPS) 443 free

MySQL 3306 free

FileZilla (FTP) 21 free
FileZilla (Admin) 14147 free

Mercury (SMTP) 25 free
Mercury (POP3) 110 free
Mercury (IMAP) 143 free
Mercury (HTTP) 2224 free
Mercury (Finger) 79 free
Mercury (PH) 105 free
Mercury (PopPass) 106 free

Tomcat (AJP/1.3) 8009 free
Tomcat (HTTP) 8080 free

Press <Return> to continue.
Howard Parsons
President - Parsonage Data Services
User avatar
howardparsons
 
Posts: 12
Joined: 30. January 2009 22:56
Location: Charlottesville, VA - USA

Re: Apache Service Premature Termination

Postby Izzy » 30. December 2009 00:31

The error message definitely relates to another use of port 80 but the port check shows free.

Perhaps your Windows Firewall or even ZoneAlarm - try temporarily disabling any of these types if enabled and test again.

BTW what Windows OS are you using?
Izzy
 
Posts: 3344
Joined: 25. April 2006 17:06

Re: Apache Service Premature Termination

Postby howardparsons » 30. December 2009 00:55

Hello Izzy,
I just turned the firewall off & tried to start Apache but no joy. I'm using Vista 64 & have had no problems w/ Apache up to now.

Howard
Howard Parsons
President - Parsonage Data Services
User avatar
howardparsons
 
Posts: 12
Joined: 30. January 2009 22:56
Location: Charlottesville, VA - USA

Re: Apache Service Premature Termination

Postby Izzy » 30. December 2009 01:09

Sometimes OS auto updates or even manual OS updates can cause issues with existing services that previously were running smoothly.

Are you logged into Vista as an Administrator and have you disabled UAC? - usually required to run Windows services and especially a web server.

Try a reboot after making any changes mentioned above - also if you are already logged in as an admin and have UAC disabled - just to see if there is any issues again in the log file when you try and manually start Apache in the XAMPP Control Panel (XCP).

You can also try in XCP to remove the tick in the Apache Svc box then, after answering the question, try and Start Apache using the Start... button again to get the green running indication.

BTW is MySQL showing a green running indication in the XCP?
Izzy
 
Posts: 3344
Joined: 25. April 2006 17:06

Re: Apache Service Premature Termination

Postby howardparsons » 30. December 2009 02:01

Izzy,
I tried the Uninstall/Install bit w/XPC, No luck. I did get a Windows Defender warning -
- System

- Provider

[ Name] Microsoft-Windows-Windows Defender
[ Guid] {11CD958A-C507-4EF3-B3F2-5FD9DFBD2C78}
[ EventSourceName] WinDefend

- EventID 3004

[ Qualifiers] 0

Version 0

Level 3

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2009-12-30T00:44:30.000Z

EventRecordID 117744

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel System

Computer Howard-PC

Security


- EventData

Product Name %%827
Product Version 1.1.1600.0
Scan ID {56228106-75A4-4567-A0E8-4B99E04A1F88}
Unused
Unused
Unused
Unused
Domain Howard-PC
User Howard
SID S-1-5-21-3045926992-4149281227-4199829-1000
Threat Name Unknown
Threat Id
Threat Severity
Threat Category
FWLink %%832
Path Found service:Apache2.2;file:C:\xampp\apache\bin\httpd.exe
Threat Classification Index 0
Threat Classification %%807
Unused
Unused
Detection Type Index
Detection Type


but the subsequent message -
Windows Defender Real-Time Protection agent has taken action to protect this machine from spyware or other potentially unwanted software.
For more information please see the following:
Not Applicable
Scan ID: {56228106-75A4-4567-A0E8-4B99E04A1F88}
User: Howard-PC\Howard
Name: Unknown
ID:
Severity ID:
Category ID:
Alert Type: Unclassified software
Action: Ignore


implied that it was ignored.

UAC is off & has been off for a week or two.

A review of the system log for the last day that Apache ran successfully showed Apache shutting down about the same time as a windows update was running. I'll have to investigate further. -- Never mind. It was simply part of the E-O-D shut down.

The indicator for MySQL is green in XCP.

I'll report in tomorrow after I reboot.
Last edited by howardparsons on 30. December 2009 02:34, edited 1 time in total.
Howard Parsons
President - Parsonage Data Services
User avatar
howardparsons
 
Posts: 12
Joined: 30. January 2009 22:56
Location: Charlottesville, VA - USA

Re: Apache Service Premature Termination

Postby Izzy » 30. December 2009 02:22

Howard, you seem to have narrowed it down to Windows Defender perhaps being the offender here.

You can test this out by temporarily disabling it and see if it helps:
http://www.vista4beginners.com/How-to-d ... s-Defender

The general consensus seems to be that although it is free there are much better anti-spy and anti-adware type software offerings out there that perceivably do a better job - a web search I used was keywords windows defender what is to see what turned up.
http://www.google.com/search?q=windows+defender+what+is
And these web search results may also help:
http://www.google.com/search?q=windows+ ... +configure

BTW it would seem it updates every day so you may need to keep your eye on this if things seem unexpectedly to not be responding as they should.
Izzy
 
Posts: 3344
Joined: 25. April 2006 17:06

Re: Apache Service Premature Termination

Postby howardparsons » 30. December 2009 02:36

Izzy,
I'll give it a go tomorrow. I've had it for today. :wink:
Howard Parsons
President - Parsonage Data Services
User avatar
howardparsons
 
Posts: 12
Joined: 30. January 2009 22:56
Location: Charlottesville, VA - USA

Re: Apache Service Premature Termination

Postby howardparsons » 30. December 2009 04:55

Izzy,
Just when I thought it was safe for me to go to bed, I remembered that I forgot to pay a bill & so I had to restart the PC. :oops:

One of the 1st things I checked was Apache & even with Windows Defender disabled, Apache would not start. A colleague here in Charlottesville seems to think that something else is in contention for port 80 even though XCP's portsniffer says that it's free. :?
Howard Parsons
President - Parsonage Data Services
User avatar
howardparsons
 
Posts: 12
Joined: 30. January 2009 22:56
Location: Charlottesville, VA - USA

Re: Apache Service Premature Termination

Postby Izzy » 30. December 2009 07:24

howardparsons wrote:A colleague here in Charlottesville seems to think that something else is in contention for port 80 even though XCP's portsniffer says that it's free.
Howard, both Wiedmann and I mentioned the fact that there is something else using port 80 because the error message is quite clear about it and most of the subsequent replies have been trying to locate what it may have been.

So now we take another tack to hopefully find the culprit - this is all a process of elimination and one has to be somewhat of a PC System detective when things are simply not clear cut, as in your case.


Open the XCP and click on the Shell button.

At the shell # prompt type
Code: Select all
netstat -ano |findstr "80"
then hit Enter.

You should get back a list that has the process ID number of what is using port 80 in the end column.
The following example has 3128 being the process ID or PID.
Code: Select all
 TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       3128
Next open the Task Manager - right click on the Task Bar and select it from the context menu then click on the Processes tab.

Look for the corresponding Process ID number in the PID column and it should give a name in the Image Name column of the associated file.

Make a note of what that name is and see if you can associate it with any software you have on your PC.

It can then be located and configured not to start when Windows is booted if possible.

BTW if nothing is using port 80 then port 80 will not be displayed in the netstat results.
And if you are not certain about the netstat results then clicking on the small icon in the top left of the shell window will give an Edit > menu for Mark and Copy so you can paste the list here in a reply box.

This OP had a similar problem but with port 443:
viewtopic.php?f=16&t=38660
Izzy
 
Posts: 3344
Joined: 25. April 2006 17:06

Re: Apache Service Premature Termination

Postby howardparsons » 30. December 2009 15:09

Izzy,
You're right about mentioning that there might be a port conflict. After a thread goes so far, you forget who said what & between talking w/ you my colleague, it becomes even more confusing. :wink:

At any rate, here are the results of the netstat:
TCP 0.0.0.0:8019 0.0.0.0:0 LISTENING 2796
TCP 0.0.0.0:8443 0.0.0.0:0 LISTENING 2980
TCP 192.168.1.101:1073 216.239.122.102:80 CLOSE_WAIT 4132
TCP 192.168.1.101:1074 74.125.113.121:80 CLOSE_WAIT 3840
TCP 192.168.1.101:1084 65.212.121.29:80 CLOSE_WAIT 4956
TCP 192.168.1.101:1101 216.92.55.100:80 CLOSE_WAIT 2440
TCP 192.168.1.101:1219 74.125.91.102:80 ESTABLISHED 5980
TCP 192.168.1.101:1231 24.143.196.97:80 ESTABLISHED 5980
TCP 192.168.1.101:1234 24.143.196.97:80 ESTABLISHED 5980
TCP 192.168.1.101:1300 74.125.115.113:443 ESTABLISHED 5980
TCP 192.168.1.101:1311 24.143.196.115:80 ESTABLISHED 5980
TCP 192.168.1.101:1313 24.143.196.115:80 ESTABLISHED 5980
TCP 192.168.1.101:1314 24.143.196.115:80 ESTABLISHED 5980
TCP 192.168.1.101:1315 24.143.196.115:80 ESTABLISHED 5980
TCP 192.168.1.101:1316 24.143.196.115:80 ESTABLISHED 5980
TCP 192.168.1.101:1336 96.17.204.20:80 ESTABLISHED 5980
TCP 192.168.1.101:1917 74.125.115.101:80 ESTABLISHED 5980
TCP 192.168.1.101:1918 74.125.8.222:80 CLOSE_WAIT 5980
UDP 0.0.0.0:57809 *:* 2760
UDP [fe80::28e8:233d:3f57:fe9a%10]:1900 *:*
1184
UDP [fe80::28e8:233d:3f57:fe9a%10]:57134 *:*
1184
UDP [fe80::cda2:5355:3e0c:6cde%11]:1900 *:*
1184
UDP [fe80::cda2:5355:3e0c:6cde%11]:57132 *:*
1184


As you can see, nothing resembling your example for Port 80.
Howard Parsons
President - Parsonage Data Services
User avatar
howardparsons
 
Posts: 12
Joined: 30. January 2009 22:56
Location: Charlottesville, VA - USA

Re: Apache Service Premature Termination

Postby Izzy » 31. December 2009 00:54

Code: Select all
TCP    0.0.0.0:8019    0.0.0.0:0    LISTENING    2796
TCP    0.0.0.0:8443    0.0.0.0:0    LISTENING    2980
Stop and close your browser and/or anything else that is connecting to the Internet so as not to include any superfluous entries in the netstat results.

Check again and look for similar entries to the above code and then check the PID and see what those 2 entries relate to.

BTW please paste your netstat entries inside forum code tags as it makes it easier to read.

You are also using a router, make sure that it is not the culprit by checking it is configured correctly also if it contains some kind of firewall - this is out of my scope as I know little of router issues.
Izzy
 
Posts: 3344
Joined: 25. April 2006 17:06

Re: Apache Service Premature Termination

Postby howardparsons » 31. December 2009 01:22

Izzy,

Here are the results:
Code: Select all
# netstat -ano |findstr "80"
  TCP    0.0.0.0:5800           0.0.0.0:0              LISTENING       7160
  TCP    0.0.0.0:8019           0.0.0.0:0              LISTENING       7000
  TCP    0.0.0.0:8443           0.0.0.0:0              LISTENING       2980
  TCP    192.168.1.101:38042    192.168.1.103:9220     ESTABLISHED     7888
  UDP    [fe80::14d1:3571:3f57:fe9a%10]:1900  *:*
     1184
  UDP    [fe80::14d1:3571:3f57:fe9a%10]:50975  *:*
      1184
  UDP    [fe80::cda2:5355:3e0c:6cde%11]:546  *:*
    592
  UDP    [fe80::cda2:5355:3e0c:6cde%11]:1900  *:*
     1184
  UDP    [fe80::cda2:5355:3e0c:6cde%11]:50973  *:*
      1184


PID 7000 Is the QuickBooks Company File Monitor Service. Tried killing it & starting Apache but no joy.

PID 2980 is the Visual SVN Server.

PID 7160 has no entry but I believe that it is connected w/ Ultra VNC which I installed this afternoon.
Howard Parsons
President - Parsonage Data Services
User avatar
howardparsons
 
Posts: 12
Joined: 30. January 2009 22:56
Location: Charlottesville, VA - USA

Re: Apache Service Premature Termination

Postby Izzy » 31. December 2009 02:05

Are you still getting the same error message in the error.log file?

If so then we have not located the software that is preventing Apache from starting on port 80

Go to the xampp folder and try and start Apache running the apache_start.bat file and see what message is returned.

You can appreciate how difficult it can be trying to imagine what is happening on a remote PC when the only method of communication is via forum posts.



In your PC you have somewhere under the logged in user a folder that stores the start up links that are used when ever you boot your PC - find it and see what is started when you boot.

You can create a folder called disabled_startup and drag the links into it so they are not started on boot - if there is no effect on trying to start Apache again after a reboot then simply drag the links back into the original start up folder then boot up again to have them start again.

Also in the XCP is a button SCM which will take you to the Windows Service Control Manager where you will see all the programs installed as a service and started automatically when ever you boot.

Take a look at what is started and see if you can spot any program that may be interfering with Apache starting - I know not what programs you have but you do - any you suspect can be disabled in the SCM for testing and enabled again if they have no effect.

You can also try this:
Close/Exit the XCP.

Open a command prompt
Click start
Click on Run...
Type: cmd.exe
Click OK

Type:
sc delete apache2.2
Click OK

Close the command console

Then try again to start Apache either in the XCP or using the bat file mentioned above.


Finally and as a last resort you may need to completely and cleanly uninstall XAMPP using one of the methods described on the home page, making sure that all ticks are removed from any Svc boxes and all components are stopped, then close the XCP before making sure that the xampp folder is deleted.

Reboot and check in the Task Manager that no XAMPP components or anything that could remotely effect the new XAMPP installation is ended before trying to install XAMPP again.

You may also like to search your registry for any Apache entries and remove them because XAMPP does not make any entries in the registry and so may be interfering in the start process.

BTW your issue has far exceeded the bounds of what is normally related to this port 80 issue and as such needs to be addressed using 'lateral thinking' or 'thinking out of the square' or similar terminology.

I hope we can persevere and somehow solve this mystery.


If you like Howard, you can also try using a different port number to port 80 by making configuration changes to the Listen directive in the httpd.conf file - but I prefer to solve this mystery if possible as changing the port number would seemingly amount to giving in to what ever is causing this issue - I think I read somewhere on your web site that this would also be your philosophy.
Izzy
 
Posts: 3344
Joined: 25. April 2006 17:06

Next

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 66 guests