Search results

may not. since lsws will replace apache, which is not under your control as you're a shared host user.

no problem of the permission. it's strange of your issue. Can you PM me the access to your server.

maybe a permission issue? please check

both lslb (litespeed load balancer) and lsws(litespeed web server) has built-in anti-ddos feature. here's the detail document on how to configure the this feature in lslb and lsws: http://www.litespeedtech.com/docs/webserver/config/security/#perClientConnLimit in your case, lsws may be...

do you have other opcode cache like eAccelerator, XCache enabled? if none of them enabled, recommend you have one, absolutely it'll improve the php performance a lot. opcode cache is built as php extension, you can save/keep your current php binary, just build out apc.so, xcache.so...

4.0.17 select latest APC 3.1.4 instead of 3.1.3p1 when build PHP in admin console. so if you want to try APC 3.1.4, rebuild PHP in 4.0.17

you can order "One Time Installation Service" at http://store.litespeedtech.com/store/cart.php?gid=5

looks like litespeed isn't installed properly. have you followed http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:apache:plesk to install litespeed with plesk?

looks a serious issue and hard to trace... what's your wordpress version? I upgraded to 4.017 on a wpmu 2.9.2 site, php 5.3.2, without problem.

maybe Redhat or CentOS

is lsws the latest version 4.0.17? you can start/stop lsws by /usr/local/lsws/lswsctrl start/stop

you can start with 2-CPU license. please read http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:license:all_about_licenses

can you upgrade to 4.0.17 and rebuild php? it uses APC 3.1.4 this looks the first report we received regarding APC 3.1.3p1 not working with WP well. and we have selected APC version higher than 3.0.19 for a long time. that's why we don't stick to 3.0.19. thanks for the report. We may...

same way to resolve these errors. in CentOS,

2010-10-07 18:03:30.633 ERROR [config:vhost:example.com] missing <docRoot> in <virtualHostConfig> 2010-10-07 18:03:30.633 ERROR [config:vhost:example.com] configuration failed! as the message hint, the vhost's document root not set yet. after creating a vhost, the next step is to fully...

can check access log, which URL are accessed with too many times during DDOS

yes, 4.0.17 use APC 3.1.4

to be clear, must include and not use there are just Unknown options.

yes, the error message tell the cause: checked the PHP document, http://www.php.net/manual/en/curl.installation.php no --enable-curl option, instead, it's --with-curl

does the DDOS access a same URL, like vhost's homepage?