Every time I add site, HTTPD goes down and won't restart

I get this error message:

(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]

The only solution is to reboot the server. Then I have to manually start HTTPD, it goes yellow, then after a refresh it goes green and says "httpd started".

So every time I add a new account, I have to take down the entire server for a minute or two! Seems like an unnecessary inconvenience to me. This really should be fixed.

This is a brand-new server running a clean minimal install of the latest CentOS 6.7, as of 1 week ago. I followed all the default, basic directions.

ssh in to your server as normal user and then su to login as root and then issue killall -9 httpd
then /etc/init.d/httpd restart  this will at least avoid you the reboot.

After that start looking for another panel seeing CWP people have left us all hanging:(

first of all we need information
what is ur server confg?

did you get this error from the beginning when you started using cwp?

did you changed/installed anything to the server recently and get this error ?

last : post the full error log

Yes, from the very beginning. And I haven't modified anything at all, just configured CWP with my information (my specific settings).

Hello,
   Even i am facing same problem, This is arising after  latest update,Please check this bug.

do you use mod security ?

To The Mute developers,

Can we admit cwp current build as major issue with web server portion of package (Apache or Nginx)

We have several servers that auto updated latest version and issue is present its not isolated issue.

With all due respect it would be nice if the developers of this once fine panel grew set balls and faced up to the issue.

The Silence and lack of communications from the devs is the worst part of this.

did you checked the error log why it is happening?
with incomplete information provided how the developers will know what is causing this issue/error?

Believe me for sure devs know very well the cause of the issue and simply creating an new update that  rolls back last update before this one would resolve this for everyone.

My issues is same as everyone else here and theirs more then enough information that as being provided about the issue.

The only new addition to my servers is cwp latest update we do not tend play games with our configurations.

I have same issue on my server with fresh install. Please check that bug

Update ... this will be fixed on next update (developers are working on it)

Any idea when we can expect this update to be rolled out?

Hi, it will be fixed in a new version. Temporarily you can add line:

Code: [Select]

killall -9 httpd to the /etc/init.d/httpd in function stop() :

Code: [Select]

stop() {
        echo -n $"Stopping $prog: "
        killproc -p ${pidfile} -d ${STOP_TIMEOUT} $httpd
        RETVAL=$?
        echo
        [ $RETVAL = 0 ] && rm -f ${lockfile} ${pidfile}
        killall -9 httpd
}


Thanks for temp fix that's just stop gap measure but better then nothing.

But could explain you to me about 2 updates on 10/04/2016 but for most of us only showed up today or last night and nothing mentioned about httpd issue.

Secondly new build introduces dovecot/postfix isssues when its contains mail sever fixes but yet breaks them instead

Starting think guys are in it for the paid support money and starting let quality of the product suffer.

Seriously hope i am misreading it


Version 0.9.8.13 (released 10/04/2016)
- fix for roundcube, phpmyadmin not working with nginx in some cases
- show user quota stats
- mail server fixes
- roundcube fixes for quota, sieve filtering
- softaculous vps detection api, for vps you will get a lower price
- new date-time changer

Version 0.9.8.12 (released 10/04/2016)
- CWP API for account management
- suPHP now shows the script name and path in top or process lists (apache rebuild needed)
- CWP faster loading and possibility to work with multiple processes at the same time.
- Apache is limiting number of php processes per user
- Email Explore, read all mailboxes from one location.
.. few bugs fixed

Hi, the trouble with Apache was fixed in latest update.