it's out since 4.1.13
http://www.litespeedtech.com/litespeed-web-server-release-log.html
cPanel whm plugin: Added a script to build matching php from command line.
usage:
cd /usr/local/cpanel/whostmgr/docroot/cgi/lsws
php cmd_buildmatchingphp.php
Sorry, haven't replied you timely. In fact we're working on it ...
Please force re-install 4.1.13, by our lab tests, /home/user/.htaccess now works like /home/user/public_html/.htaccess
please test and confirm.
please comment out all extensions:
extension=eaccelerator.so
zend_extension = "/usr/local/IonCube/ioncube_loader_lin_5.3.so"
and test again. if no 503 error, then add the extension one by one, to identify which extension is the cause.
do you have
extension=eaccelerator.so
in php.ini ? it's also opcode cache. same advice as before: only keep one.
please list all of your extensions in php.ini if still 503 error.
"Europe/Berlin" is ok per http://php.net/manual/en/timezones.europe.php
should not need this:
extension=timezonedb.so
the 503 error may relate to this extension. please comment it out to see if the error disappears.
you can create it --- /usr/local/lsws/lsphp5/lib/php.ini
in cPanel, if you build matching php, lsphp5 should use same php.ini -- /usr/local/lib/php.ini
hi, I did test,
for included rules,
<IfModule mod_litespeed.c>
# litespeed stuff here
</IfModule>
working in litespeed and ignored by apache, so yours just ok.
also tested, following OK too:
<IfModule litespeed>
# litespeed stuff here
</IfModule>
still the php extension's issue.
did testing with following extensions in /usr/local/lib/php.ini:
zend_extension="/usr/local/Zend/lib/Optimizer-3.3.9/php-5.2.x/ZendOptimizer.so"
zend_extension="/usr/local/IonCube/ioncube_loader_lin_5.2.so"
extension="ixed.5.2.lin"...
in /usr/local/apache/logs/stderr.log, there are lots of error "Cannot load module 'XCache' because conflicting module 'eAccelerator' is already loaded in Unknown on line 0"
commented out /usr/local/lib/php.ini following lines:
extension="xcache.so"
extension="ixed.5.2.lin"
restarted...
maybe conntrack issue. when ab tests very slow, please check:
#sysctl net.ipv4.netfilter.ip_conntrack_max
#sysctl net.ipv4.netfilter.ip_conntrack_count