Search results

@George : PHP opcode cache means.... eaccelerator.shm_size? Mine is just use the default 16 mb. So I must to reduce that size again? Yes I remember you have told me to empty it around every 5 minutes... Btw I regularly clean my /dev/shm/eaccelerator with hourly cron job. Is that too...

Here they are, bro : ----------------------------- PHP_LSAPI_MAX_REQUESTS=3000 PHP_LSAPI_CHILDREN=175 LSAPI_MAX_IDLE=5 LSAPI_PGRP_MAX_IDLE=5 LSAPI_MAX_PROCESS_TIME=300 ----------------------------- And again.... :(

The CPUs are getting wild again.... :(

Actually, the main problem that pushed me to run easyapache and then re-setting LSWS is : the cpu load. Switch to LSWS makes CPU spike randomly to 40-50 from 2.x - 3.x I don't know what caused this. Just spikes quickly to 10-20-30-40-50... and then go down to 2.x - 3.x again. In next couple...

The fixing steps are : 1. killall -9 lshttpd 2. restart LSWS <--- not fix it self 3. again, killall -9 lshttpd 4. start Apache 5. reinstall 4.0.2 from scratch pheww... thanks for all helps, really appreciated :)

is there any other way to stop this LSWS? does just kill LSWS pid will safe to do? can't hold any longer... thank you...

Thank you auser, But still LSWS forcing to start as the only webserver. root@medusa [/tmp]# cd /usr/local/lsws/bin root@medusa [/usr/local/lsws/bin]# ./lswsctrl stop [OK] lshttpd: stopped. root@medusa [/usr/local/lsws/bin]# cd /usr/local/apache/bin root@medusa [/usr/local/apache/bin]#...

anyone know how to stop LSWS and then start apache manually from console? so then I can start to reinstal 4.0.2 immediately... thanks in advance.

my clients are starting terrorize me by phone now... they cannot login to their forum and/or their member area on their websites....

but reinstall needs to switch to apache first... while i still got : ---------------------------------------------------------------------- "LiteSpeed Web Server Control Operation ... Switch to Apache LSWS is still running. Fail to stop within 30 secs LiteSpeed is still running! Failed to...

still cannot switch to 4.0.2 and apache.... still cannot access https.... would you mind to help me to look at these issue... thank you!

Update Still stucked... Cannot switch back to 4.0.2 through WHM LSWS plugin :(

Your words is my command! I'll do that, George!

whoa... you are right! but... how to do that safely? rm -rf * on /tmp ? Thank you

Firstly, I suddenly got this : Secondly, I switch 4.0.2 to 4.0.1 in hoping to fix that error. Switched to 4.0.1. But still got that error and plus I cannot switch back to 4.0.2 again. I even cannot switch LSWS to Apache in order to reinstall this LSWS to 4.0.2. Stucked. In this...

Perhaps you should add the mod_sec rules first? Or it have been missing? The path for mode_sec was on /usr/local/apache/conf/ Btw some of C99 has succesfully made them self "disappear" from ClamAV. ClamAV cannot recognize that special C99 as a trojan/virus. So ClamAV will be unused on that...

They still can run on XSS way? On my server, I have put all of those php disable_function, except php_uname, and I try my self for some of shell scripts can not execute any important command to hack to another account.

Solved by mistwang... 4.0.1 installed now without any problem. Cool!! Many of thank you :)

I have switching between v3.3.24, v4.0, and v4.0.1 on the fly through lsws whm plugin but still resulting error 406 while executing login form on any sites under my server. But if I switch to apache + suphp, the problem is just dissapear. The mod_sec2 rules are the same for both apache or...

Update 3 : 1. Uninstall v4.0.1 through sh /usr/local/lsws/admin/misc/uninstall.sh 2. Remove lsws directory 3. Installing v4.0 from scratch Problem solved :)