Search results

Hello, After upgrading from 5.2.8 to 5.3 Litespeed doesn't work anymore. Plugin in cpanel also doesn't work so I cannot switch to apache and when I try to run manually lsws I get: /usr/local/lsws/bin/lswsctrl restart ./litespeed: /lib64/libc.so.6: version `GLIBC_2.12' not found (required by...

Thanks I will try that.

OK I found this problem with Joomla. http://forum.joomla.org/viewtopic.php?p=2114099 Do you have suggestion how to compile eAccelerator with this option? "I'm having also this issue, the problem seems to be related with latest eaccelerator release 0.9.6.1 by default does not have this function...

It looks like this feature is totally broken. In PHP config I have set 256MB memory limit I don't use any opcode cache until I fix this issue. In ext app for PHP 5 soft limit was 450 and now I raised it to 600MB. And if I check logs I see there is 128mb memory limit. [31-Jan-2012 13:39:25] PHP...

Hello, since you do not recommend xcache running with suPHP Litespeed I'm wondering which version of eAccelerator is good? I see they are not developing anymore eAccelerator so I'm wondering if this 0.9.6.1 is good version? I would be running on latest Litespeed + PHP 5.2.17 which would run...

After that logs work but I lost one day of logs. :(

4.0.16 didn't made any difference I have killed all processes recompiled PHP to 5.2.14 and switched to 4.0.17 and it is fixed now. I see again process is spawned but it dies normally after few minutes. So I guess everything is back to normal.

I have compiled yesterday new php version, so I switched to apache 2.2.15 and it loads pages faster than LiteSpeed 4.0.17. With Apache my page is loaded in 0.6s, and with litespeed 0.78s. My server memory usage is 611 vs. 966MB, so in memory usage LSWS beats apache easly.

Well, i'll test for you I have tried to kill old processes and LSWS has spawned new ones right away, mysql is also restarted just in case. Now i'm runing 4.0.16 and I'll need few days to check if new processes will be created and I will update this topic.

I can't disable xcache load would kill the box, I got millions of hits per day. I checked when 4.0.17 was released and problems started when I upgraded to 4.0.17, so I will try with 4.0.16.

Reply With QuoteCOMMAND PID USER FD TYPE DEVICE SIZE NODE NAME lsphp5 9492 nobody cwd DIR 8,7 4096 5565132 /home/site/public_html lsphp5 9492 nobody rtd DIR 8,5 4096 2 / lsphp5 9492 nobody txt REG 8,5 16326967...

This is trace result of this "hanging" processes: strace -p 9492 Process 9492 attached - interrupt to quit futex(0x4a280c, FUTEX_WAIT, 2, NULL <unfinished ...> Process 9492 detached root[~]# strace -p 10231 Process 10231 attached - interrupt to quit futex(0xaf8140, FUTEX_WAIT, 2, NULL...

My problem is that if I killed them, there will be soon new ones. Here it is: ─litespeed(8114)─┬─httpd(8115) │ └─litespeed(8116)───lsphp5(8135)─┬─lsphp5(14178) │ ├─lsphp5(14432)...

Same thing: nobody 349 0.0 0.3 303396 16236 ? SN May06 0:30 lsphp5 nobody 468 0.0 2.2 365028 92068 ? SN May06 0:57 lsphp5 nobody 469 0.0 1.1 317052 46032 ? SN May06 1:16 lsphp5 nobody 679 0.0 3.6 421292 151752 ? SN Sep03...

Hi, my LSWS is restarted everyday by cPanel when it is needed to process logs, as you know this is how it needs to be done according to cPanel. Lately I noticed increase in memory usage and I found out I got lot of old processes which are not killed properly by graceful restart and if I continue...

Can i automatically reject those requests in LSWS? It would be nice also if after request I can ban them for certain time period.

Can you explain what does this mean? Usually when load is high I see a lot of those errors, so I'm wondering is this because web server cannot server data or client is trying to attack web host? Status 400: Bad request method: 

Yea httpd_ls_bak is there, ok I will try to uninstall.

Plugin for cpanel in LSWS 4.0.14 it doesn't seem to work. I have tried to switch from LSWS to Apache, when I click switch it just waits 30 seconds and says cannot start apache. In error_logs there is no reference to apache load just LSWS related info. Is anyone else experiencing this kind of...

mistwang said that it is not possible to upgrade via web update because some permissions were changed from 4.0.6 version, so I guess when I upgrade to latest version there will be no problem upgrading from 4.0.14 to later version.