Search results

I just got an idea. Could you do # ldconfig and then try restarting LiteSpeed

This is exactly what we are controlling when we say that we control resources. We will not allow client's PHP processes to use more CPU resources that you set the limit too. As the result, he will not be able to affect any of your other clients. This is also the reason we started with...

You can also contact me: E-Mail: iseletsk@cloudlinux.com GTalk: iseletsk@gmail.com Skype: iseletsk it will be faster to resolve it direct.

Did you get any errors while running centos2cl? when you do uname -a: do you see cloudlinux kernel? what is the result of rpm -qa|grep lve?

Is everyone happy how LiteSpeed works with CloudLinux now? Any feedback?

Sorry, that wasn't meant to say that user killed the server due to that. As you said before -- user just hit the IO. We cannot stop that yet.

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...

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

It is possible that the site is not serving dynamic content right now -- and that is why you see 0 for cpu usage if you run lveps -- it will show you the number of jiffies (cpu ticks) spent by lve to serve that site. Also, could you do lveps -p and see if that process (isphp5) is in LVE? It...

What does this script do? How are you testing it? Are you hitting some PHP script all the time? TOP shows CPU usage since process starts lveps shows the usage during the last few seconds

We are not limiting individual processes, but all of them together, for a site. Could you show me what lveps -d shows? Also, what are you settings in /etc/container/ve.cfg and how many cores does your server have?

The big numbers are jiffies (Within the Linux 2.6 operating system kernel, since release 2.6.13, on the Intel i386 platform a jiffy is by default 4 ms, or 1/250 of a second. The jiffy values for other Linux versions and platforms have typically varied between about 1 ms and 10 ms.) spent by CPU...

Thanks a lot :) Good to see you as well. I am looking forward working with Litespeed company & community. I think this web server rocks.

Litespeed should work on CloudLinux out of the box. Yet, to get the benefit of LVE (ability to control amount of CPU the site can use) -- small changes needs to be added to the CGI/FastCGI part of the server. It is virtually 10-20 lines of code that needs to be added -- but without them --...