Search results

looks like need extra step to enable core dump for suid processes the core file should be created under the same directory where the php script is. strace should tell you whether a core dump file has been created or not.

maybe a permission problem. only root user can read it?

Right now the cache module does not monitor the disk usage, user can clear up the cache directory regular with a cron job if needed. Should give enough disk space for it. We may add the feature to clean it up. Cache file will stay on the disk until it was removed regardless lshttpd process...

try reset the username password with lsws/admin/misc/admpass.sh

Like Tony said, there might be compatibility issues with PHP modules. If there is a problem, you will see some error/warning messages when you run lsws/fcgi-bin/lsphp5 -i

Or if defined?(ActiveRecord::Base) if defined?(ActiveRecord::Base.clear_active_connections!) ActiveRecord::Base.clear_active_connections! else ActiveRecord::Base.connection.disconnect! ActiveRecord::Base.connection.reconnect! end end while LSAPI.accept != nil...

How about this if defined?(ActiveRecord::Base) if defined?(ActiveRecord::Base.clear_active_connections!) ActiveRecord::Base.clear_active_connections! else ActiveRecord::Base.connection.disconnect! @reconnect = true ActiveRecord::Base.establish_connection end end

check the php.ini path in output of "php -i"

Please run "ulimit -a" from a php script to make sure that core file size limit is not 0.

Make sure the same php.ini is used by cli and lsphp5

Get rid of the "E" flag since you do not set any new environment variable.

not possible.

For downloaded file, permission 644 should be fine. The problem is in Suhosin patch for PHP 5.2.8, the expanded directory is actually for 5.2.7 .

Your problem probably is a configuration issue.

http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:license:all_about_licenses

Yes, it is what it does.

http://www.litespeedtech.com/how-tos.html#qa_dos

4.0rc1 support large file.

Yes, I think suphp does not honor the open_basedir protection.

fix is in latest 4.0rc1 build.