Search results

RailsRunner.rb in 4.0.10 should be compatible with all version of Rails.

It is on our to-do list. :)

Try adding the following code to lsws/fcgi-bin/RailsRunner.rb ActiveRecord::Base.connection_handler.clear_active_connections! if defined?(ActiveRecord::Base.connection_handler) just below ActiveRecord::Base.clear_active_connections! if defined?(ActiveRecord::Base) around...

looks like your server is under attack or not something causes the traffic surge. Is it back down now? If it is attack, you should implement some anti-DDoS configuration. http://www.litespeedtech.com/how-tos.html#qa_dos

You can configure a vhost natively in LSWS with the same domain as cPanel's vhost configuration, the vhost configured natively has higher priority. You need to create the listener and add the binding in LSWS as well.

no sample here, please check the fastcgi web site, it is standard. Basically you need to define a FCGI authorizer external app in LSWS.

If you can get the MySQL adapter object, you can try calling "disconnect!" http://api.rubyonrails.org/classes/ActiveRecord/ConnectionAdapters/MysqlAdapter.html#M001996 at the end of your App initialization routine.

The MySQL connection is because in your App initilization code accessing DB. It is due to internal change in Rails, used to be able to close MySQL connection, but cannot with your version of Rails. Restart does not matter.

command should be.

You can write a FCGI authorizer using LDAP in perl.

I think this is the connection to MySQL, should be closed.

I have been investigating some issues on your server.

Mysql connection was not closed before ruby process forked, so if one process close the connection, the other processes will get the error. To verify this, you can "lsof -p <pid_of_ruby_process>", check the mysql unix socket, all of them must be referencing to the same one, and the parent ruby...

Another note on W3 Total Cache, looks like everything is still served by PHP, just cached by memcache or something. it is slower than WP super cache, if you do not need to keep everything dynamic or any specific need for features in W3 Total Cache, WP super cache is a better choice for busy blog...

Max idle time and connection keepalive timeout should not be set. Initial request timeout should be around 60. What you see probably is normal as LSWS uses minimum number of persistent PHP processes to serve all requests, CPU utilization may looks like for indivudal process, but the overall...

I do not know, not likely cPanel does that. But it is in user's home directory owned by that user, so they should have no problem accessing those files.

For log rotation, you can set the rotation point higher, and rotate it with your cron job, just "mv ..." will work, then create the log file with correct permission. If you know how to customize cPanel's vhost template, you can add a php_value error_log .... directive to the vhost template.

You should upgrade to 4.0.10, or upgrade your WHM plugin cd /usr/src wget http://www.litespeedtech.com/packages/cpanel/lsws_whm_plugin_install.sh sh ./lsws_whm_plugin_install.sh rm -f lsws_whm_plugin_install.sh

It is not recommended and the risk is on your own, but if you really want, you can change files/directories owned by lsadm back to the old user account. restart LSWS. Or, you can run the installer of the older release, do a manual upgrade, you can back to the older release. you will stuck with...

I think there is somehting that LSWS does not like in the AJP packet sent by flup-ajp, so web server side closed the connection. If it can be reproduced with certain URL, you can grep 503 error in access log see if it only happen to certain URL. You can use tcpdump to capture the data exchanged...