Search results

You need to increase the "Process soft/hard limit" under "Ruby Rails" tab.

Please post the the rules that does not work.

Does it mean SMF kill the process with "-9"? That would explain the unexpected signal 9. LSWS does graceful restart/stop, which will try to finish all the pending requests before exiting. Will investigate the "Process dumped core" issue. it does not show which process dumped core. If lshttpd...

There is always a lshttpd running as "root". That's normal.

No worry, the installer won't destruct your server. ;) It will prompt you with what kind of operation would you like. Update is the default. You can click "ENTER" all the way to the end.

About our license and CPU, please check http://www.litespeedtech.com/support/forum/showthread.php?t=1660 You can use 1-CPU to 4-CPU license on your server without any problem. It is up-to you. The trial license is a 2-CPU license equivalent. We offer volume discount, please contact sales.

Signal 9 is SIGKILL, strange. Will you get that whenever you restart the enterprise edition?

LSWS only apply suEXEC for a few commonly used script handler definitions for PHP. We will change the code to look for script handler start with "php" instead.

lshttpd itself is monitoring it. the right way to switch to apache is: service lsws stop sleep 1 /usr/local/apache/bin/httpd uninstall service httpd start Will make this available in the final 3.3.8 package. If you start LSWS, the wrapper will be installed again, if configuration is "Using...

the updated 3.3.8 package should work well now. At least, it works on Vivek's server. Also, when LSWS proxy to backend Apache, this wrapper should be able to control both Apache and LSWS, ffeingol, you can give it a try if you want to, you do not have to use this feature though.

.net support will be in our 4.0 release.

No, it will not change your current configuration. Just do a update.

Please contact bug @ ... for further investigation.

I will check your server if possible.

OK, everyone, please download and try 3.3.8 release. Just change the version number in the download link. Two configuration options to change, "Auto Reload on Change" to "Use Apache binary wrapper", set "Apache Binary Path" to where the Apache httpd is. This should install the wrapper script...

If you did not download 3.3.7 release manually, you may use the older one. bin/lswsctrl has been updated to make it work properly.

Just use *.domain.com in the listener to vhost mapping.

better use our internal redirect function instead. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed:wiki:feature:internal_redirect

No need to apply this patch for users who proxy back to Apache.

./httpd_ls_bak ./httpd_ls_bak -k start -DSSL should work. Our automated solution will automatically apply/remove the patch based on "Port Offset/IP Offset" configuration in LSWS.