Problem with new IP's

N

niget2002

Member
#1
#1
We added new IP's to our box. Now, when restarting lsws, we get the following errors:

from /usr/local/lsws/logs/error.log

Code: 
2011-05-18 06:46:52.959 [WARN] [config:server:listener] No listener is available for normal virtual host! 
2011-05-18 06:47:38.761 [ERROR] [/etc/apache2/conf.d//zz010_psa_httpd.conf:108] Listener for 10.1.30.54:80 is not available! 
2011-05-18 06:47:38.761 [ERROR] [/etc/apache2/conf.d//zz010_psa_httpd.conf:108] Listener for 199.204.137.30:80 is not available! 
2011-05-18 06:47:38.761 [ERROR] [/etc/apache2/conf.d//zz010_psa_httpd.conf:108] Listener for 199.204.137.31:80 is not available! 
2011-05-18 06:47:38.761 [ERROR] [/etc/apache2/conf.d//zz010_psa_httpd.conf:108] Listener for 199.204.137.99:80 is not available! 
2011-05-18 06:47:38.791 [ERROR] [/etc/apache2/conf.d//zz010_psa_httpd.conf:445] Listener for 10.1.30.54:80 is not available! 
2011-05-18 06:47:38.791 [ERROR] [/etc/apache2/conf.d//zz010_psa_httpd.conf:445] Listener for 199.204.137.30:80 is not available! 
2011-05-18 06:47:38.791 [ERROR] [/etc/apache2/conf.d//zz010_psa_httpd.conf:445] Listener for 199.204.137.31:80 is not available! 
2011-05-18 06:47:38.791 [ERROR] [/etc/apache2/conf.d//zz010_psa_httpd.conf:445] Listener for 199.204.137.99:80 is not available! 
2011-05-18 06:47:38.853 [WARN] [] can't set 'Forced Type', undefined MIME Type handler/perl-script 
2011-05-18 06:47:38.855 [WARN] [] can't set 'Forced Type', undefined MIME Type handler/perl-script 
2011-05-18 06:47:42.083 [ERROR] [/var/www/vhosts/feefighters.com/conf/httpd.include:44] Listener for 199.204.137.30:80 is not available! 
2011-05-18 06:47:42.086 [ERROR] [/etc/apache2/conf.d//zzz_horde_vhost.conf:1] Listener for 10.1.30.54:80 is not available! 
2011-05-18 06:47:42.086 [ERROR] [/etc/apache2/conf.d//zzz_horde_vhost.conf:1] Listener for 199.204.137.30:80 is not available! 
2011-05-18 06:47:42.086 [ERROR] [/etc/apache2/conf.d//zzz_horde_vhost.conf:1] Listener for 199.204.137.31:80 is not available! 
2011-05-18 06:47:42.086 [ERROR] [/etc/apache2/conf.d//zzz_horde_vhost.conf:1] Listener for 199.204.137.99:80 is not available!
The errors are only on the newly added IP's. All existing IP's are working correctly. The system is using Plesk with Unlimited domains.

Any ideas on what can be causing this?
 
W

webizen

Well-Known Member
#2
#2
Please check if those newly added IP are available (e.g. pingable) on the system. If not, the following errors will be shown even though they are configured in Plesk (httpd.conf).

2011-05-18 06:47:38.761 [ERROR] [/etc/apache2/conf.d//zz010_psa_httpd.conf:108] Listener for 10.1.30.54:80 is not available!
2011-05-18 06:47:38.761 [ERROR] [/etc/apache2/conf.d//zz010_psa_httpd.conf:108] Listener for 199.204.137.30:80 is not available!
2011-05-18 06:47:38.761 [ERROR] [/etc/apache2/conf.d//zz010_psa_httpd.conf:108] Listener for 199.204.137.31:80 is not available!
...
Click to expand...
 
W

webizen

Well-Known Member
#4
#4
what lsws version and edition are you using? also, are you using vps? if so, you may check user bean counter for any error count
 
Last edited:
T

tommynsong

Member
#5
#5
webizen said:
what lsws version and edition are you using? also, are you using vps? if so, you may check user bean counter for any error count
Click to expand...
This is vmware VM running lsws 4.1 enterprise.
bean counter does not apply nor the numtcpsocket.
lsws can bind other port such as 53, 443 and 3000.

any other thought you might have?

Tommy
 
T

tommynsong

Member
#7
#7
webizen said:
try create listener (for port 80) in lsws (admin console -> configuration-> listeners).
Click to expand...
I can manually add the listener in LSWS admin console but nothing is serving on port 80 since it does not bind to any vhost.
This is a Plesk + LSWS setup, so lsws need to be able to bind port 80 from apache's configuration.

http://199.204.137.30/ return a 404 (manually add listener in lsws admin console) while
https://199.204.137.30/ load Plesk default page (read apache's configuration).

Please advise,
Tommy
 
M

mistwang

LiteSpeed Staff
#8
#8
How many IP do you have on that box? Have you checked "netstat -an | grep LISTEN" see if IP:80 are binded.
Try a full stop, then start from command line. No need to manually add listener in admin console.
Also you can manually download 4.1.1 package by changing version number in the download link and give it a try.
 
T

tommynsong

Member
#9
#9
mistwang said:
How many IP do you have on that box? Have you checked "netstat -an | grep LISTEN" see if IP:80 are binded.
Try a full stop, then start from command line. No need to manually add listener in admin console.
Also you can manually download 4.1.1 package by changing version number in the download link and give it a try.
Click to expand...
Hi Mistwang,

Is there limitation to the number of IP address lsws can bind?
I did check that port 80 bind on other IP addresses except those new ones.
Other ports beside 80 bind correctly:

# netstat -anp | grep 199.204.137.30
tcp 0 0 199.204.137.30:53 0.0.0.0:* LISTEN 8675/named
tcp 0 0 199.204.137.30:3000 0.0.0.0:* LISTEN 21543/litespeed (ls
tcp 0 0 199.204.137.30:443 0.0.0.0:* LISTEN 21543/litespeed (ls
udp 0 0 199.204.137.30:53 0.0.0.0:* 8675/named
udp 0 0 199.204.137.30:123 0.0.0.0:* 28761/ntpd
#

This is a production server with several hundreds of site on it.
Randomly upgrade lsws without knowing whether or not it correct the issue is not a feasible option for us.

Thanks,
Tommy
 
N

NiteWave

Administrator
#10
#10
Randomly upgrade lsws without knowing whether or not it correct the issue is not a feasible option for us
Click to expand...
upgrade is quite safe -- the old version is still there and not overwritten. you can switch back to old version easily: lsws admin console->Actions->Version Manager->SwitchTo, just one click.
 
M

mistwang

LiteSpeed Staff
#11
#11
If there are more than one hundred IP addresses assigned to that server, you should try a full stop, then start

cd /usr/local/lsws/bin
./lswsctrl stop
./lswsctrl start

LSWS will bind to *:80 instead of each individual IP:80 when there are more than 100 IP addresses, to reduce the number of file handles used for listener sockets.

It requires a full stop/start to apply that change.
 
You must log in or register to reply here.
Top