Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Apache not starting

Created: 23 Jan 2013 | 8 comments

Having a problem with apache on one of my servers getting the following in the application log.

 

Event Type: Error
Event Source: Apache Service
Event Category: None
Event ID: 3299
Date:  1/23/2013
Time:  1:27:45 PM
User:  N/A
Computer: 
Description:
The Apache service named  reported the following error:
>>> (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:8014     .

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Event Type: Error
Event Source: Apache Service
Event Category: None
Event ID: 3299
Date:  1/23/2013
Time:  1:27:45 PM
User:  N/A
Computer: 
Description:
The Apache service named  reported the following error:
>>> no listening sockets available, shutting down     .

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

 

Anyone have any thoughts on this

Comments 8 CommentsJump to latest comment

SebastianZ's picture

Is any other software on you SEPM using port 8014? - this should be default SEPM APache port.

Give it a try and run the Management Server Configuration Wizard for SEPM. This should restore the proper settings.

Rick Bywalski's picture

Tried that and it did not work this box is dedicated to SEP btw.   This all started when they replaced the SQL server if that helps.

 

Rick Bywalski's picture

I get the message failed to install managment server webserver service you should restart your server and try again.  I have restarted and this keeps happening.

 

SebastianZ's picture

Have a look here:

https://www-secure.symantec.com/connect/forums/fai...

... and checkwhat is currently set under: ...\Program Files\Symantec\Symantec Endpoint Protection Manager\Apache\conf\

 

As you mentioned the SQL server we cannot exclude some corruption in the database - there have been already similar cases:

http://www.symantec.com/docs/TECH167686

 

Have a check with the mentioned dbvalidator:http://www.symantec.com/business/support/index?page=content&id=TECH104892 - if this finds any broken links in the database.

If the validation fails - a recovery from older backup may be required or a disater recovery:

http://www.symantec.com/docs/TECH160736

 

Rick Bywalski's picture

Hmmm well this was set up as a load balance/disaster recovery site.  I am wondering if it might be a good idea to break replication since it has not replicated since the problem started.  Delete the database run the wizard and have it create a new one then turn replication back on.

 

 

Rick Bywalski's picture

Yes I did that was one of the first things I tried.

pete_4u2002's picture

can you check this thread and see if it helps, check for the solution part.

https://www-secure.symantec.com/connect/forums/rec...