Search results

How busy is your server? Have you changed any PHP related configuration? Have you build PHP binary matching your Apache mod_php? Do you get anything in the MySQL log file?

LiteSpeed Web Server 3.3.19 has been released This release is mainly to fix a bug that prevent LSWS from reloading license key after the key file being updated. Download LiteSpeed Web Server View Version History

You do not need to wait till the old license expire, you may not aware that we add 7 days to license expire date as grace period. When you pay your license on time, there should have about 7 days left on your old license when it gets updated to the new expire date, usually around 37 days. So, if...

Let you admin to check if there is any cron job which restarts LSWS every hour. LSWS wont restart by itself.

Sorry about that, it is due to a bug introduced recently that LSWS failed to reload the license key after it being updated, we have fixed the problem in 3.3.19 release, it will be available today.

What happened when you try to start LSWS? Output? Log?

You need to find out what code produces this And get rid of it.

The function has been built into LSWS already, you do not need to compile anything, just add the configuration, it will work.

The output is not useful as it does not show the first request being processed by it. You need to set "Max connections" to 2, so a parent RailsRunner.rb process will be started, then you strace that process.

Looks like some part of your rails application write to STDOUT (file descriptor 1) directly via low level I/O functions, it breaks LSAPI protocol. Since all ruby processes are fork off the parent one, you just do strace -f -p <pid_of_parent> So, you can check the first request.

It is hard to say what causes it to crash without a core file. Please check error.log and stderr.log . If you knew which request cause lsphp5 to crash, you can try strace the PHP process. Please upgrade to 3.3.18, or to be released 3.3.19 package.

Please read the document first. It pretty much match the configuration in mod_geoip, so you can read mod_geoip document as well.

Just configure it under LSWS web console. http://www.litespeedtech.com/docs/webserver/config/general/#geolocationDB It will set the same environment variables just like Apache mod_geoip.

if /bin/ directory does not exist on your server, it will not be blocked, LiteSpeed does not block requests results in 404. You can check the audit_log for requests being blocked.

Since "$VH_ROOT" is "/www/$VH_NAME", should not php_admin_value error_log /www/$VH_ROOT/logs/php_errors.log be php_admin_value error_log $VH_ROOT/logs/php_errors.log ? If the directory /www/www/$VH_NAME/logs/php_errors.log does not exist, the log file will not be created. You can verify...

It will take another month or two, depends on the stabilities of those new features added.

The modsecurity audit log generated by LSWS is not compatible with mod_security whm plugin yet. it works, just that the blocked requests are not shown from the plugin. Yes, you need to switch back to Apache temporarily when you need to rebuild Apache/PHP with easyapache.

Your need to reinstall zlib, since it is a 64bit Linux, it should use /usr/lib64/libz.* instead of /usr/lib/libz.*

Maybe you need increase the memory limit, in both php.ini and the lsphp? external application from LSWS web console.

You really need to look into the config.log to find out why libxml test failed. Is that possible that the problem is related to "--enable-simplexml"? Just a wild guess.