Search results

I have put latest 3.3.23 release package on your server, it works fine.

working on it.

goldgoat.tar is a 12GB file, without Large file support, stat() function will fail. Our 4.0b3 has large file support for 32bit OS, you can give it a try.

OK, the puzzle is solved, the memory limit is inherit from lshttpd when PHP is not started in suEXEC mode, under cPanel/WHM plugin, cPanel set the memory limit to 256MB, so when lshttpd started from WHM plugin, all lsphp processes get 256MB memory limit. Even after you restart LSWS from web...

how about command sudo -u apache ls .../goat/ if get permission denied, it is a permission problem, otherwise, we have to look somewhere else.

trying to reproduce the problem in our lab.

Looks like a permission problem, maybe the user that lshttpd run as has no permission to check file status under goat/ directory.

I checked the server, for some reason, the memory limit for the lsphp5 processes was set to 256M regardless what is configuration value in php.ini and LSWS. We need to investigate more.

Thank your for the bug report. "The problem with graceful restart from web console" has been fixed in the latest 4.0b3 release package (today).

You can use a VPS license. other regular license can be used as well.

It should work. You can enable rewrite log by adding RewriteLogLevel 9 to the <VirtualHost .... > section for that vhost in httpd.conf Rewrite log will be in lsws/conf/error.log or /usr/local/apache/logs/error_log when used with cPanel. Once we get the log, we can pinpoint the problem.

It should work, at least it should display a 404 error page. Have you checked the reply with firebug? What do you get with litespeed? With Litespeed, you can do it in another way. Only put header("status: 404" ); in PHP, then add a custom 404 error page pointing to 404.html .

If you can PM me a temp root access, and tell me how to reproduce the problem, I can take a look for you.

Open web console, and change server level script handler for "php4" from "lsphp4" to "lsphp5".

Just create a phpinfo() page under the admin folder to verify if xcache get loaded or not. Also, you may want to disable PHP suEXEC to make all PHP processes to share the same cache memory if your server is not for shared hosting.

Are you sure the memory limit in php.ini has been set to a higher value? check the phpinfo() page.

Are you using any PHP opcode cache? Try disabling it see if it helps or not.

Maybe I should take a look at your server.