Search results

please check the ower/permission along the path /dev/shm/lsws/gzip make sure this folder exists and nobody user(which litespeed process run as) can create/update/delete folders/files under /dev/shm/lsws/gzip

please confirm: does gzip work on 4.2.19 but not on 4.2.20 ?

test link has no problem now -- assume the issue has been fixed.

can you give me the access to the server (in private conversation), so I can reproduce the issue and identify the cause.

you can install 4.2.19 via #/usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.19 so you can test between 4.2.19 and 4.2.20

>Out of memory (allocated 8278245376) (tried to allocate 80 bytes) this is terrible -- already allocated 8G memory so please refer #2 reply. you have to improve the php code, for example if it's wordpress site, disable plugin one by one, maybe one plugin has caused the memory nightmare.

then switch back to previous lsws version fix the issue ? if so, what's the old and new lsws version ?

to be sure lsws web admin -> Configuration -> Server -> PHP suEXEC: Yes

should be lsphp5 process

disable EacceLerator will save some (maybe a lot) memory. anyway you can try disable it, see if any improvement during high traffic

it should relate to override check if AllowOverride None exists somewhere in httpd.conf. then change to AllowOverride All restart lsws

the master configuration file is /usr/local/lsws/conf/httpd_config.xml, like apache's httpd.conf you can edit it via script (sed / awk / python / perl) etc, it's same effective to edit it via CP in PHP. at the end, graceful restart lsws to make your changes effective...

>We are already running 4.2.20 - is there another release? release number is same, but binary is different. but minor difference. when run that command, you get the latest binary which may just fix this particular issue.

lsws web admin -> Actions -> Real-Time Stats->"Http Used" also you can calculate this number by parse /tmp/lshttpd/.rtreport*

so now it's clear and confirmed the root cause.

this is same as apache. http://httpd.apache.org/docs/2.2/mod/core.html#errordocument ErrorDocument 403 "Sorry can't allow you access today" should always work either in .htaccess or httpd.conf

no since you need opcache, so just enable it. disable LVE is to resolve the issue you reported in above #5 post.

can you try: put RewriteEngine Off to top of public_html/cgi-bin/.htaccess see if the error message will be gone. just a workaround for test purpose.

ok. let's take a look anyway.

please post 2188th ~ 2190th lines of /home/public_html/cgi-bin/.htaccess let's see what they are first