Search results

you need to verify parent directory permission with sudo -u nobody touch /var/lshttpd/swap/tempfile download the latest 4.1.12 build see if it work properly or not. It should help with the CPU usage issue with your server.

If you set "Swap Directory" http://www.litespeedtech.com/docs/webserver/config/general/#swappingDir to a new location, make sure the directory exists, and has write permission for the user that litespeed run as.

It is likely that the process' virtual memory has been exhausted Please check output of ulimit -v set it to unlimited in /etc/security/limits.conf, then restart LSWS. Also check the number of available inode for the /tmp partition.

I guess you use fcgi env as storage of temp variables, it wont affect LSAPI request/response in any way, so it is not implemented in LSAPI. You need to implement your own storage for that purpose. a hash associate array is recommended.

This issue should have been addressed in our 4.1.11 release. It is caused by bug in cookie handling code.

If it still happen with 4.1.11, please send a link to download the whole log file to bug@litespeed..., we need to investigate.

could be running out of space in swap directory. move http://www.litespeedtech.com/docs/webserver/config/general/#swappingDir to a partition with enough free disk space.

We have 11.32 in our lab as well, but we do not have this issue. Are you sure that suPHP is enabled in cPanel? switch back to Apache see if you have PHP running as the desired user id. If you are sure that apache work properly, but LSWS does not, please contact bug@litespeed... we may need to...

Please do force reinstall, should be fixed now.

You need to verify it with "id" command in a PHP script. Common shared script are running as nobody, like our directory index script, it is normal to see some PHP process running as nobody, however, it does not mean that all scripts were running as nobody, PHP script under user's public_html...

thanks for the heads up.

Please test it with a simple PHP script running "id" command to verify it. Is it a new installation? Does it only happen with 4.1.11? have you tried with older release?

which version of LSWS were you using? If you switch back to the older version, will the problem disappear?

Please try the latest build of 4.1.10.

Looks like apache reply does not have any response header, just response body directly. can you confirm it? we certainly can change LiteSpeed response accordingly.

One of our customer has success with the following PHP code. <?php ignore_user_abort(true);//avoid apache to kill the php running ob_start();//start buffer output echo "show something to user"; session_write_close();//close session file on server side to avoid blocking other requests...

the crash has been fixed in lsapi_main.c, please try rebuild you lsphp5 binary. PHP LSAPI packages has been updated. The reason why it does not do a chdir like cli-php will take more time to figure out.

SSL Client verification is a rarely used feature, it only supported in LSWS native configuration. Apache has tons of features, and new modules added by third party, we only support the most commonly used features. You can configure the SSL vhost in LSWS native configuration with SSL listener...

Modsecurity rule like SecRule &ARGS "@gt 1000" could do it.

you should enable tcp_syncookies in order for making tcp_max_syn_backlog effective. It should not be set too high.