Listening errors followed by server crash

#1
Hi,


I have been having some trouble lately, my server keeps on crashing and I cant access any sites, sftp, ssh etc.


I noticed in the litespeed admin panel, theres quite a few errors
2008-08-02 22:48:44.996 ERROR [/usr/local/directadmin/data/users/eliteser/httpd.conf:11] Listener for 69.42.223.19:80 is not available!
2008-08-02 22:48:44.997 ERROR [/usr/local/directadmin/data/users/eliteser/httpd.conf:48] Listener for 69.42.223.19:443 is not available!
2008-08-02 22:48:44.997 ERROR [/usr/local/directadmin/data/users/dxthxcom/httpd.conf:11] Listener for 69.42.223.19:80 is not available!
2008-08-02 22:48:44.998 ERROR [/usr/local/directadmin/data/users/dxthxcom/httpd.conf:48] Listener for 69.42.223.19:443 is not available!
2008-08-02 22:48:44.999 ERROR [/usr/local/directadmin/data/users/wzmetinc/httpd.conf:11] Listener for 69.42.223.19:80 is not available!
2008-08-02 22:48:44.999 ERROR [/usr/local/directadmin/data/users/wzmetinc/httpd.conf:48] Listener for 69.42.223.19:443 is not available!
2008-08-02 22:48:45.000 ERROR [/usr/local/directadmin/data/users/kennyw/httpd.conf:11] Listener for 69.42.223.19:80 is not available!
2008-08-02 22:48:45.001 ERROR [/usr/local/directadmin/data/users/kennyw/httpd.conf:48] Listener for 69.42.223.19:443 is not available!
2008-08-02 22:48:45.001 ERROR [/etc/httpd/conf/extra/httpd-ssl.conf:74] Listener for _default_:443 is not available!
2008-08-02 22:48:45.002 ERROR [/etc/httpd/conf/extra/httpd-ssl.conf:230] Listener for _default_ is not available!


Then after a couple minutes the server just basicallly stops responding and needs to be rebooted manually.

I'm just wondering if this could be a LiteSpeed issue, something on my side, or something more along the lines of my host?



Thanks,
Bob
 
#3
Are you using LSWS with cPanel?
Please PM your server login, we can take a look.


Ah, the problem was actually numtcpsock was set too low. I raised it and its fine now. I dont know if it was caused by LiteSpeed or what...but my server doesnt crash and the listening errors are fixed.
 

mistwang

LiteSpeed Staff
#4
That's great you have figured it out.
Would you mind sharing a little bit more on how to find it out?

What log file you checked? Error? What TCP parameter need to be tuned? We would like to put in our wiki to help other uses who have similar issue.
 
Top