Apache Webserver showing as stopped

Submitted by cyrus on Sun, 05/29/2011 - 13:56 Pro Licensee

Webmin version 1.550 Virtualmin version 3.85 Pro Operating system CentOS Linux 5.6

I received an email from my system stating:

/etc/cron.daily/logrotate:

Stopping httpd: [ OK ] Starting httpd: (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] Stopping httpd: [FAILED] Starting httpd: (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]

I logged into Virtualmin and see that Apache is down in my 'Service Status'. When I attempt to start Apache from my 'System Information' page, I am directed to the following message:

Failed to start apache :

Starting httpd: (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]

All my websites are working fine though, kindly advise.

Status: 
Closed (fixed)

Comments

Submitted by andreychek on Sun, 05/29/2011 - 14:01

Howdy -- those errors suggest that Apache isn't stopping and restarting cleanly.

To correct that -- what I'd suggest is logging into your server over SSH as root, and running these commands:

killall httpd
sleep 5
/etc/init.d/httpd start

After that -- does Apache show up correctly in Virtualmin?

Submitted by cyrus on Sun, 05/29/2011 - 14:15 Pro Licensee

[root@host ~]# killall httpd [root@host ~]# sleep 5 [root@host ~]# /etc/init.d/httpd start Starting httpd: [ OK ]

Logged in to Virtualmin, refreshed the page, and all's well.

Thank you.

Submitted by andreychek on Sun, 05/29/2011 - 14:20

Great, I'm glad that helped. Let us know if you have any other questions!

Submitted by Issues on Sun, 06/12/2011 - 19:21

Automatically closed -- issue fixed for 2 weeks with no activity.