Search results

Have you restart LSWS after the change? the rewrite log is in the main log lsws/logs/error.log at "INFO" level, so the server log level should be set to "INFO" or "DEBUG".

The 500 error is generated by Rails. Maybe something is missing for the LSAPI rail setup, missing environment variables, etc. Please check rails log files.

The configuration looks all right, anything logged into lsws/logs/error.log about "nlcman"?

No, the user that owns httpdocs.

With Apache configuration, the user's home directory set in /etc/password is used as vhost root, not the document root set in the httpd.conf.

If you still have IDLE cpu cycles on that server, you can increase the "Max Connection", if not, increase "Max Connection" may not help much, you probably need to upgrade the server CPU or use cluster if it is CPU bound. You need to make your rails application run as fast as it can. Using all...

Can you please post the VBSEO rewrite rules in the .htaccess file. I think it should work well, you can also turn on the rewrite log by adding "RewriteLoglevel 9" to the vhost section of that virtual host. Please post the rewrite logging messages.

in this week if everything goes well.

Please be patient, fix to your problem is in upcoming 3.3 release. The security issue must be addressed immediately.

Should not be any problem with the upgrade. And you can always revert back if you want.

You can try memcache add-on for vB. LSWS configuration wise, you can check our anti-DDoS feature in our HOWTO documentation.

LiteSpeed Web Server 3.2.4 has been released to address a security flaw Download LSWS: http://www.litespeedtech.com/product...rver/download/ Changelog for LiteSpeed Web Server 3.2.4: Fixed a bug that may expose the source code of PHP or other scripts.All LiteSpeed user should upgrade to...

You can lower the max connection if there is no requests being queued most time in the WaitQ from the real time statistic report.

mcrypt installation is not complete. Please try yum install mcrypt-devel or install mcrypt package from source.

Yes, we can update to PHP5 anytime if we want to, but we still prefer PHP4, as it is faster with smaller binary.

Since the root directory has been changed to /opt, so the path to lsphp should be /lsws/fcgi-bin/lsphp, no /opt/lsws/... Another tool to debug this is to use "strace" under the chroot, copy strace to the jail then do chroot /opt strace /lsws/fcgi-bin/lsphp <you_test_php_script>

Step 5 is the configuration, just add the configuration parameter you need. And do steps follow it after the configuration change. Repeat till you get a PHP binary meet you need.

Please consult the PHP manual regarding respect extensions, you need to add corresponding configuration parameter to enable them when you compile your own PHP binary.

Yes, the performance of DB will affect the web server. Since PHP need to wait for new results from DB queries. Make sure your DB server is in good shape and SQLs are optimized.

try this command from command line chroot /opt /lsws/fcgi-bin/lsphp It should tell you the missing library in the chroot jail, then copy those files over to the jail.