Search results

You should check which php.ini is used from a phpinfo() page output, and update that file. Also, if CageFS is used, you should update the php.ini inside the cage.

You need to check memory usage of each process to find out which process uses a lot of memory. tmp file does not matter.

like that firewall block the port.

If you see a lsphp5 process running as root user, it is the suEXEC daemon mode. Yes, it is working.

If the type of page can be detected via rewrite rule, you can use rewrite rule to set the expire time. for the rewrite rule order, it does not matter.

For question 1, yes, it is the same protocol. you need to update the skeleton after updating lsphp as well.

It is not vulnerable as it is linked against OpenSSL 0.9.8

should be fixed now.

4.2.9 has been released to address this.

there is no x86_64 package for standard release. maybe something is wrong with your installation if you do use LSWS enterprise. remove /usr/local/lsws/autoupdate/release then try again.

Please upgrade to 4.2.9 with /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.9

Maybe you were not using the Apache binary wrapper mode? http://www.litespeedtech.com/docs/webserver/config/general#autoReloadApacheConf

Do you have any of the checkbox for "httpd" unchecked under "Service Configuration"->"Service Manager"?

Does restarting LSWS fixes it?

Are you using Enterprise edition? standard edition wont work with more than 5 vhosts in the httpd.conf.

Are you using native LSWS configuration or still load vhosts from Apache configuration? First, you need to make sure .htaccess was loaded in the debug logging. Make sure .htaccess permission is set correctly so it can be read by server process, need to make it world readable. try touch...

check output of /usr/local/lsws/fcgi-bin/lsphp5 -i see if it the mysql header/lib is updated and match. If it is different to the phpinfo() page you got under a user account, you need to update the CageFS template to use the new lsphp5 binary, the old one is still used in the cage. Assuming...

You need to run easyApache first to let cPanel update header/library, then build matching PHP. If you are not using cPanel, you need to manually update mysql header file to match the lib. then build PHP. If you build php from Admin console, you need to make sure the updated header files are used.

For cPanel user, run easyApache, then build matching PHP should fix the problem.

It is a cpanel issue, not related to litespeed, cpanel itself has its built-in web server. switch back to apache and try it again. you will get the same result.