Search results

You should downgrade eaccelerator and suhosin to the older version. eAcc 0.9.6-rc1 is in beta, and optimizer is removed if you read the release log.

Yes, you can do that. You still need to change the owner of configuration files to lsadm, otherwise, it cannot be changed via web console. The purpose of this is to prevent the user/group that lshttpd run as to access any configuration file, only the web console can.

the latest release require you to login via ssh to start the build script manually as instructed on the screen.

Are you using a control panel? For cPanel, our WHM plugin will take care of everything. The key for a smooth migration is to use the same PHP version for Apache and LSWS, so extensions built for Apache PHP will work without problem with LSWS PHP. Only when Apache is using the thread-safe...

You can get 4.0.6 which is stable. If you want to switch between 4.0.10 and other version, you need to run the installer and do a manual upgrade. That's because the admin console uses suEXEC in 4.0.10 release.

Feedbacks on 4.0.10 has been very reliable in term of 503 errors.

Is it random or consistent with certain request. If it is consistent, it must be a problem with your PHP. Also, you should disable opcode cache during the trouble shooting.

No, the update will not change any configuration.

You need to update the file ownership and permission as the admin console is running in suEXEC mode with 4.0.10. make the configuration file owned by "lsadm" and make sure lsadm user/group can access the directory holding the configuration file.

Tried a new build on that server. looks like it is working much better now. Monitored it for a while, only one site get 408 errors and I think it is real. Please download 4.0.10 again and upgrade your other servers and give us some feedback.

May I login to check one of the server?

Are you using the x86_64 edition? It might be related to a recent change, we will have a new build today, see if it help or not.

Yes, all bug fixes are in latest 4.1RC1 build. Memory usage was provided by web server process, it causes some trouble, so we disabled it for now, maybe will be added later.

restart LSWS from command line see if everything back to normal. /path/to/lsws/bin/lswsctrl restart

You should to do one upgrade at a time, at this point it is hard tell it is a PHP issue or LSWS issue. What is your "Max Connections" for lsphp5? maybe you should tune it down.

The DB connection must be closed after Rails application initialization bofore forking children process to serve requests. Works for MySQL, may have issue with oracle, so you may need to close it explicitly at the end of initialization code of your app.

add www.domain.com to the listener to vhost mapping.

It is the order of appended query string and the one from request URL. Fixed in updated 4.0.10 binary. Thanks for the bug report.

Sometimes, the browser will cache a page having problem, make sure to clear browser cache. If need, please submit a support ticket with temp login, we will take a look.

Is it random? Usually it will be cached by browser. Please try a command line tool and dump the response header as well. I usually use "lynx -mime_header <url>".