Problem starting Apache

6 posts / 0 new
Last post
#1 Tue, 03/04/2014 - 13:55
DoubleSpeed

Problem starting Apache

When I try and start Apache I'm getting an error message:

Failed to start apache : Starting httpd: [Tue Mar 04 19:34:06 2014] [warn] module version_module is already loaded, skipping httpd: Could not reliably determine the server's fully qualified domain name, using XX.XX.190.35 for ServerName [Tue Mar 04 19:34:06 2014] [warn] VirtualHost XX.XX.190.35:80 overlaps with VirtualHost XX.XX.190.35:80, the first has precedence, perhaps you need a NameVirtualHost directive (98)Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs [FAILED]

Can anyone advise what is wrong?

Tue, 03/04/2014 - 14:18
andreychek

Howdy,

It sounds like there may still be an Apache process in memory that's holding that port open.

Try killing the existing Apache processes with this command first:

killall -9 httpd

Then start Apache again:

/etc/init.d/httpd start

And let us know if that works. The above is for CentOS systems, let us know if you're on a different distro.

-Eric

Tue, 03/04/2014 - 14:23
DoubleSpeed

Thanks, tried that hasn't made any difference, same messages?

Tue, 03/04/2014 - 15:16
andreychek

Howdy,

What Linux distro/version are you using?

And what output do you receive when running this command:

ps auxw | grep http

Tue, 03/04/2014 - 15:19
Locutus

Theoretically, though rather quite unlikely, it could also be a different process that's holding port 80 blocked. You can find that out with netstat -tpln | grep :80. That will tell you which process is currently listening on port 80.

Tue, 03/04/2014 - 16:19
DoubleSpeed

Thanks for the replies I think I found the issue with the server's fully qualified domain name, this is a new server and it was cloned from a 'image' of another server I've updated the Hostname and DNS Client and the server now restarts and runs.

I do seem to have a problem with getting the correct SSL certificate to be used by the virtual host/domain, I've installed a GoDaddy SSL Certificate in the Manage SSL Certificate I put the files on the server in the home directory and selected these using the File on server method in the Update Certificate and Key all appeared to work OK and in the CA Certificate it shows GoDaddy however in the Current Certificate tab it still says Self-signed. When I try and view a file in the website with https it complains saying the certificate isn't valid and when I view the certificate in the browser it appear to the the self signed for the server IP not the GoDaddy one?

Operating system CentOS Linux 5.10 Webmin version 1.660 Virtualmin version 4.03.gpl GPL

Topic locked