Panel version 11.5.30 Update (could not bind to address 0.0.0.0:80)

[AaronClifford]

I upgraded to Panel version 11.5.30 Update #2 today and now six times my sites have become unaccessible. I then have to restart httpd to get it working but get this error five or six times before it starts again:

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

Any ideas why this might be happening?

 

[IgorG]

Check it - http://kb.parallels.com/1336

 

[AaronClifford]

I restarted the server and didn't have the issue for around 11 hours, now it just happened again, the sites stopped working and when I restarted httpd I got the same error as above, Looked at the link you sent and this is the response I got:

[]# grep -iR ioncube /etc/php*
/etc/php.d/00-ioncube-loader.ini:; comment out next line to disable ionCube Zend exte nsion in php
/etc/php.d/00-ioncube-loader.ini:zend_extension=/usr/lib64/php/modules/ioncube_loader _lin_5.3.so

Is this correct?

 

[AaronClifford]

[Thu Jul 04 10:19:54 2013] [warn] mod_fcgid: process 3822 graceful kill fail, sending SIGKILL
[Thu Jul 04 10:19:58 2013] [warn] mod_fcgid: process 3870 graceful kill fail, sending SIGKILL
[Thu Jul 04 10:19:58 2013] [warn] mod_fcgid: process 3843 graceful kill fail, sending SIGKILL
[Thu Jul 04 10:19:58 2013] [warn] mod_fcgid: process 3844 graceful kill fail, sending SIGKILL

It's these, having regular downtimes for 1m up to 10m and they correspond with the above errors.

Any ideas?

 

[Nikolay.]

Is this correct?

Yes, it is.

 

[AaronClifford]

Any idea on the post above this Nikolay?

 

[Nikolay.]

Any idea on the post above this Nikolay?

Nope. Otherwise I would have posted them.

I suggest looking at other threads with mod_fcgid issues. Maybe they'll give you some insight.

Also you may try to disable WatchDog module if you use it. Not sure it will help or will not make matters worse, but it may be part of the cause.

 

[InderS]

I upgraded to Panel version 11.5.30 Update #2 today and now six times my sites have become unaccessible. I then have to restart httpd to get it working but get this error five or six times before it starts again:



Any ideas why this might be happening?

Check any process is running on port 80 when you are getting same error

# lsof -i tcp:80