Search results

You should reinstall LSWS from scratch.

You need to remove the symbolic link /opt/lsws/add-ons/awstats, rename /opt/lsws/add-ons/awstats-7.3 to /opt/lsws/add-ons/awstats . I have no idea on how to log a PHP variable (username) into access log. Can you do that with Apache?

It was generated by PHP curl extension, the data written to file handle 2 (stderr).

Your PHP code is CPU intensive, make sure you have a working PHP opcode cache. If you use off shelf application like wordpress, joomla, should review the plugins used, avoid poorly written plugin that uses a lot server resource, looking into application's cache solution. If you wrote your own...

The log shows that the custom error page is the source of the problem. Please disable the related "ErrorDocument 404 ..." directive, see if it can help.

You may need to try to reproduce the problem yourself, if you can, then turn on debug logging, check debug log entries relates to your IP. You may need to strace the PHP process processing your request to find out what exactly happens.

You create two vhosts, one for regular http, one for https, so cache for those vhosts wont be mixed together.

netstat -anp | grep 7080 Maybe you should just reinstall LSWS.

Please try "killall -9 litespeed", then try start LSWS.

Please check error log, make sure /tmp is not full.

just restart LSWS if /tmp directory exists, everything will be recreated. If /tmp does not exist, you need to create it.

It is a feature for enterrpise edition though.

looks like "DirectoryIndex" configuration was not applied. Clear the /dev/shm/lsdiskcache , see if it is due to staled cache copy or not?

http://blog.litespeedtech.com/2013/06/07/litespeed-web-server-as-reverse-proxy-template/ answer to your question is at the end of the blog post.

Glad that we figured it out. :-)

If it still behave like that after clicking "Force reinstall", you may need to manually download 4.2.19 package again, unpack, run install.sh, select "Upgrade", all configurations wont be changed. no need to reinstall from scratch.

Just click "Force reinstall" link under "Version Manager" page, Your output looks like the older build is still in use. There should be only "472", "473" should not be started. Only one lsphp5 process started by litespeed process.

please check related discussion. http://www.litespeedtech.com/support/forum/threads/header-set-access-control-allow-origin.8346/

Please try "df -i" to check inode usage, should be related to disk quota.

It turns out to be a problem with MACOSX package, addressed in latest 4.2.19 build.