Starting httpd: (98)Address already in use

How can i fix this issue guys ? When i rebooted the server, running but after a few hour again down.

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]

have you check apache error_log since there should be something or maybe by checking /var/log/messages ?

How can i fix this issue guys ? When i rebooted the server, running but after a few hour again down.

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]

same problem with new patch.

I need new patch to fixed.

This issue being present since last update   CWP version: 0.9.8.12

Telling someone check /var/log/message when you guys know fully aware this bug that introduced in last update.

I have CWP version: 0.9.8.12 on 3 vps  and 2 dedicated servers and they all have same issue.

do you have ssl enabled for your sites ?

do you have ssl enabled for your sites ?

use apache and nginx only.

do you have ssl enabled for your sites ?

use apache and nginx only.

Do nginx using port 80 or 8181?

if you're using nginx as reverse proxy, uninstall nginx and use Apache only and see if the problem is resolved or not

don't forget to rebuild the vhost

if you're using nginx as reverse proxy, uninstall nginx and use Apache only and see if the problem is resolved or not

don't forget to rebuild the vhost

do you have ssl enabled for your sites ?

use apache and nginx only.

Do nginx using port 80 or 8181?

yes, uninstall nginx have issue same.

contact cwp support team for further investigations.

contact cwp support team for further investigations.

I wait feedback cwp support.

This does appear to be a major bug. There are other processes running on port 80 or 8181. You need to kill the running processes which can be done with the command fuser -k 80/tcp if httpd has stopped or fuser -k 8181/tcp if nginx has stopped.

Im running 5 vps and 2 dedicated servers in which i never experienced this bugs.

When can we expect someone to chime in and actually fix a widespread issue?

You cannot use this panel if hosting clients as soon they add new domain Apache reload fails.

It rather amazing the developers not even updated us with least an eta for fix.

You can use following commands to restore httpd service
 
1. killall -9 httpd
2. /etc/init.d/httpd restart

but this is not fix