Search results

3.3.14 package has been uploaded, it should be the most one in term of cPanel compatibilities. Please give it a try.

3.3.14 package has been uploaded, it should have fixed this problem, please give it a try.

LSWS does not support virtualdocumentroot directive yet. You can archive the same result with rewrite rule.

In order to make cPanel happy, LSWS 3.3.13 write its own pid to Apache pid file, it may have side effect with other control panels, other control panel may be able to get pid of lshttpd and kill it when it want to restart Apache. We will have it addressed in 3.3.14 release.

If it is in RoR log, you should trouble shoot the internal redirect code, maybe need to terminate the request properly.

If the browser receive the redirect response, a external redirect is used, not internal redirect. Maybe you should try def sendfile @name = session[:jobname] + ".zip" filename = ":public/download/" + @name headers["x-litespeed-Location"] = filename end

Nothing to worry about, you can remove those vhost templates if you want.

Are you using "Override Restart HTTP script" option? cPanel may try to start Apache somehow and messed up the PID file. Looks like the "replace Apache httpd" option is more reliable for now.

lswatch.sh is a watchdog script, it has not be used by default. You start start it manually if you want to keep lshttpd running regardless.

switch to Apache just do service lsws stop service httpd start The /script/restartsrv_httpd should work with either LSWS or Apache, or both.

3.3.13 has been officially released. it should be fine now.

Install wireshark and sniff the traffic see if you can find out anything.

Latest official 3.3.13 package should have fixed the cPanel kill lshttpd problem.

LiteSpeed Web Server 3.3.13 has been released This release is mainly to address a few minor bugs and improved cPanel compatibilities. Attention cPanel users: LSWS should make cPanel happy now and won't be brutally killed during cPanel update or during adding/removing user account. All three...

Yes, LiteSpeed uses persistent connection between web server and external app process, so LS keep tracking state of connection.

$VH_ROOT/conf/ should be owned by the user that lshttpd run as.

LiteSpeed always try to use the minimum number of processes and assign request to the most recently used process.

You can use a rewrite rule to test GEOIP_COUNTRY_CODE just like with mod_geoip http://www.maxmind.com/app/mod_geoip

kill lswatch.sh

Looks like cPanel still able to kill lshttpd somehow, so the replace httpd binary is till the best choice. We need to do more test.