[solved] Make Litespeed compatible with Cloudlinux's limits

[Michael]

Howdy Stormy,

100% ModSecurity support is never going to be possible, but better support is a big priority for us — this is always true, but we're especially focusing right now.

m

 

[wanah]

Keep those feature requests coming!

Michael

I'm going to have to think hard about that one as 4.2.5 seems to solve all of mine in one go !

 

[stormy]

So - what's the recommended configuration for limits now? Same in Cloudlinux and Litespeed?

 

[mistwang]

Cloudlinux limit >= litespeed limit.

 

[stormy]

I have Cloudlinux NPROC at its default of 100. Litespeed Process Soft Limit and Process Hard Limit are set at 200, which is obviously wrong. Not sure if this is Litespeed's default or if it was set by my DC.

Should I set both limits at 100 so they are the same as Cloudlinux then?

 

[Pong]

Yes, you can. If there is any problem, you might want to increase limit to a little bit higher.

Now litespeed has 400 as soft limit and 450 as hard limit.

 

[stormy]

I'm not sure how the soft and hard defaults interact with Cloudlinux. Should they both be set the same?

 

[Pong]

Regarding the soft limit and hard limit, You can check
http://litespeedtech.com/docs/webserver/config/security#procSoftLimit
http://litespeedtech.com/docs/webserver/config/security#procHardLimit

You can set the same or different.

Regarding how cloudlinux and Litespeed work together, I believe both run independently on the limit. No mather how your setup (the same or different, which one is greater), either one reaches the limit will trigger the error. Logically Cloudlinux limit >= litespeed limit.

 

[stormy]

Advice from Cloudlinux support is to set them both at 100, the same as NPROC in Cloudlinux. I've done the change, so far so good.

Thanks for the help!