Search results

yes, use same options as apache, just remove '--with-apxs2=/usr/sbin/apxs' or replace it with '--with-litespeed'

right. just remove '--with-apxs2=/usr/sbin/apxs' rebuild php using web admin console: Actions --> Compile PHP

can you compare phpinfo() under apache and litespeed, see any difference ? for example, value of "Configure Command"

back to apache, run phpinfo(). save the build options. then rebuild php under admin console --> Actions --> Compile PHP using same options as apache (remove 1 or 2 related to apache) please try yourself or refer our wiki page regarding how to rebuild php under litespeed.

stop apache; then restart litespeed, check if litespeed running at port 80. if not, check apache httpd.conf and update it. since apache and litespeed can't listen to same IP:port. configure apache httpd.conf as before, just think apache is replaced by litespeed, and litespeed read and...

please refer: http://xcache.lighttpd.net/wiki/XcacheIni http://xcache.lighttpd.net/browser/trunk/xcache.ini default: xcache.var_size=0 try: xcache.var_size=4M or xcache.var_size=16M etc

what's your control panel?

please don't run apimport.sh, it's old and not tested for some time. instead, after install lsws, in admin console,try config: Server--> -->General -->Using Apache Configuration File this should be better than running apimport.sh

do you have a control panel like cPanel ?

please try RC3, not RC2. just change RC2 to RC3 in the download link

not good to go back to 4.0.11, since 4.0.14 and below has a security issue. you can manually to upgrade to 4.1RC3, see if working fine. if issue of 4.0.17 still continue, we can check your server and identify why.

Thanks for sharing. Maybe 4.1RC3 has even lower memory overhead -- you can try and compare.

good for trouble-shooting if issue can reproduce. I access the URL, it's normal and no 503. you mean after entering correct password, 503 will happen?

yes, it is.

run "pstree -p", check how many of "litespeed" processes are running. there is 1 parent litespeed process, the number of sub processes equal to your CPU license number.

the issue was introduced by 4.0.17 new feature:mod_action support. its PHP Content-Type is "handler/fcgid-script". the new 4.0.17 build ignore "fcgid-script" and fixed the problem. lugus, can you give more info about your current problem? you can post here or through PM.

that's normal. it shows your server handle the requests quickly. if your server is mainly serving download files, you're see big number of "Request in processing" and small number of "Requests per second", since downloading a large file take time to complete.

thanks for sharing.

so what change you've made to solve the issue?

yes, confirmed from our developer, 4 core license will do better than 2 core license when handling ddos. p.s, you can upgrade/downgrade between 1/2/4/8-CPU license at anytime yourself in our store's client area, to choose the license which is best suitable for your current traffic, load etc...