Max-connections is always one more than it should be, 2 if you include the parent

F

fantasydreaming

Well-Known Member
#1
#1
I.e. I have max-processes: 2, but ps auxxf shows 3 child processes under each parent process. The web console also shows '3 processes', '3 idle'.

Also, when it's doing the "Emergency" extra spawns to handle load, the admin interface seems to only show the max-processes as exisitng, when it's really 2* that number that have been loaded.

kevin 25317 0.7 2.8 96188 58652 ? SNs 11:13 0:03 \_ rails storywrite
kevin 25333 3.4 3.1 103956 65632 ? SN 11:13 0:16 | \_ rails storywrite
kevin 25334 5.5 3.5 111240 72948 ? SN 11:13 0:27 | \_ rails storywrite
kevin 25335 3.7 3.7 115644 77024 ? SN 11:13 0:18 | \_ rails storywrite
 
M

mistwang

LiteSpeed Staff
#2
#2
Are you using 2CPU enterprise? The server should not increase the max connection on its own. Which version of LSWS are you using? Maybe should upgrade to the latest one if not yet.

Is it possible for me to login your server and take a look? If yes, please PM me a temp login.

Also, when it's doing the "Emergency" extra spawns to handle load, the admin interface seems to only show the max-processes as exisitng, when it's really 2* that number that have been loaded.
Click to expand...
That's normal, because the server will only try to make that number of connections to the backend, the backend fork extra processes on its own, the server has no idea about what happened.
 
F

fantasydreaming

Well-Known Member
#3
#3
I upgraded to the latest update (today, 3.02? or .03) just to make sure it wasn't fixed already.

1cpu non-enterprise, rails easy setup.

Sorry, the server is secure, so we can't create temporary logins :( I can check anything specific for you if you want though.

This should be pretty easy to reproduce with an easy rails setup that does a sleep(5) call or something, then pound it with ab..
 
You must log in or register to reply here.
Top