Just assign different value for "Max connections" to the different backend, like "60" connections to server1, "40" connections to "server2", LSLB will use that as "weight" for different backend.
Not sure you are asking about a cloud solution or just want to spread load among multiple lshttpd processes (n-cpu license) in one server.
If you want a cloud solution, you have to use shared storage.
Maybe do a fresh reinstallation, the admin console should work properly.
Try run /path/to/lsws/fcgi-bin/lsphp5 from command line see if you get any error.
If I/O wait is very high, it may affect the lshttpd, please try "strace -tt -T -p <pid_lshttpd>" see what is going on.
AIO in 4.1 will solve this issue.
check phpinfo() page for the open_basedir configuration. adjust the configuration in apache httpd.conf or php.ini.
If you used apache with suphp, open_basedir never worked.
You have to allow symbolic link in your LSWS configuration.
Only the error message uses a wrong path, the wrong path is due to failed symbolic check, when it passes, there is no problem.
if "RAILS_GEM_VERSION" >= 2.3.0, new code with the rack adapter is used, otherwise, the older version of railsrunner is used.
new code uses "ActiveRecord::Base.connection_handler.clear_active_connections!"
Can it be fixed by restarting LSWS?
LSWS resolve symbolic link when read configuration, but does not update the link if changed. Will have it addressed in 4.1 release branch.