Search results

If you run /scripts/restartsrv_httpd from command line, will it restart? maybe we need to login to your server to take a look, something is not right.

Looks working fine, you can try create another account see if LSWS got restarted. cpanel apache graceful restart will trigger /usr/local/apache/bin/httpd -k graceful then trigger LSWS to restart.

run command /usr/local/apache/bin/httpd -k graceful from a terminal, see what you got. It should restart LSWS. but on your server it will fail, need to find out why.

Maybe because /tmp partition is full, not being removed.

should trigger a graceful restart, but lsrestart.log does not show the restart. Maybe it is due to /tmp/lshttpd directory being removed constantly? so, failed.

That means that lsphp5 process crashed when you access /phpmyadmin, you can check stderr.log or PHP error_log if you can locate that. When you access /phpMyAdmin-4.1.6-all-languages directly, different set of lsphp5 process was used. Maybe one lsphp5 process group is in suEXEC mode, the other...

It means that cPanel restarts the server successfully, LSWS should be restarted by that time. You can check /usr/local/lsws/logs/lsrestart.log and ap_cmd_param.log The timestamp of last restart should matches. Maybe browser cached the cPanel default page, uses wget or curl to test the new...

Can you please check /usr/local/cpanel/logs/safeapacherestart_log, see if anything log after adding an account?

We want to know why it does not happen to Apache? Those directives are ignored by Apache because it is for non-exist Apache module? Please send us a sample, we will try to fix it from the root.

try /usr/local/lsws/bin/lshttpd -v if it shows Standard, you may need to do echo "4.2.11-ent" > /usr/local/lsws/autoupdate/release /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.11

It it happen only to specific URLs under certain account, It could be caused by <Location ...> <LocationMatch ...> directive added somewhere. You can create a helloworld or phpinfo test script using different name, put it in different folder, see if you can access it. If possible, send a...

Open a file is expensive as we have to go through all the security checks, so LiteSpeed will keep the file open when it was serving to someone, we already added logic to close the file as soon as LiteSpeed done serving that file. We will revisit it in our 5.0 release see if anything more we...

When you test it, you should use a PHP script, LiteSpeed wont filter static file usually. Turn on ModSecrity Debug Log to find out what happened.

Are you using Apache httpd.conf configuration file to configure the vhost, or using LSWS native configuration through our WebAdmin console? If you use native configuration, you may look into using vhost template.

You only need one opcode cache, do not try to use APC and eAccelerator at the same time. APC might be more stable. For PHP 5.5 you may need to use Zend opcache. eAccelerator may not be compatible with PHP 5.4 . ioncube uses prebuilt PHP extension from their site, please follow guide on their...

For the link you can turn it off with http://www.litespeedtech.com/docs/webserver/config/general#hideSigInErrorPage For admin PHP problem, it is because a FreeBSD security feature. If you set the problem will be fixed. We will turn off the PID checking for FreeBSD.

Please change the log level of server and admin console to "DEBUG" http://www.litespeedtech.com/docs/webserver/config/general#log_logLevel http://www.litespeedtech.com/docs/webserver/config/adminserver#vhlog_logLevel toggle debug logging, try to reproduce the problem to get full debug log for...

Please check log for message like at INFO level, if the rewrite rule works properly, otherwise, need to make sure the rewrite rule can block those URL.

It is a bug related to HTTP proxy, your rails setup uses mongrels backend. It has been fixed in latest 4.2.10 build.

I may need to temp root access to take a look, please send more detail information to bug@litespeed... All rails application got that error? does the path exist?