Litespeed + cPanel + Cloudlinux

[tina]

How do we get the WHM plugin to upgrade LiteSpeed to 4.0.14?

[tina]

The Version Management page of the LiteSpeed web admin does not show an upgrade link to 4.0.14, only a Force Reinstall link. We are running 4.0.13. Any ideas?

[NiteWave]

The upgrade link will be enabled after a few days. Sometimes this can catch possible serious bug before upgrade widely.

[tina]

Originally Posted by NiteWave

The upgrade link will be enabled after a few days. Sometimes this can catch possible serious bug before upgrade widely.

Ah, that makes sense. Thanks!

[optize]

Is there a way to disable cloudlinux via litespeed? Comment out a module?

[mistwang]

we will add an option to turn it on/off.

[DanEZPZ]

To those of you that properly tested this, how did you get on?

We fired up a new server and put a few users on to test it, within a few minutes they had taken it offline.

The idea behind it is great, but it's not ready for real world use IMO.

[iseletsk]

Originally Posted by DanEZPZ

To those of you that properly tested this, how did you get on?

We fired up a new server and put a few users on to test it, within a few minutes they had taken it offline.

The idea behind it is great, but it's not ready for real world use IMO.

Did you change CPU and maxEntryProc limits, or did you run with default one?
What did you see in lveps -d?

[DanEZPZ]

Hi Igor,

We exchanged a few emails a week or so ago, I'm Dan from EZPZ Hosting (as my forum name suggests).

The CPU limit is at 25 and procs is at 30.

A client ran a script designed to stress the server which just killed disk I/O. Obviously clients wouldn't be doing this in a "real-world" environment but it was enough to show us the protection isn't quite what we expected.

If you want to have a look at the setup and run the script you're more than welcome to have the root details.

Dan

[iseletsk]

Dan,

Thanks a lot. Yes, I remember that.
We just figured out that Lite Speed doesn't take into account maxEntryProcs that LVE has.
So, if you site runs more PHP scripts then there is maxEntryProcs -- all extra scripts will run outside LVE -- dragging down the server.
You can control number of concurrent PHP scripts via LiteSpeed, on per user bases by setting PHP suEXEC Max Conns option.
Make sure this value is lower then maxEntryProcs.

In the future versions LiteSpeed will correctly reject (or queue requests) to server dynamic content once the site is over maxEntryProcs.