Custombuild not showing Litespeed

codes9

Verified User
Joined
Sep 5, 2019
Messages
73
I've recently upgraded OpenLitespeed to Litespeed on one of our Hosting servers.

The upgrade process initially failed due to some licensing key issues and Custom build would revert back to Apache & Php-Frm. I resolved this issue with Litespeed.

I installed Litespeed several times, and got errors from Custombuild about Litespeed not being selected, then when I select it it would revert back to Php-Frm and complain about that. I also set the options.conf file manually. But this also did not work out.

Bash:
cd /usr/local/directadmin/custombuild
./build update
./build set webserver litespeed
./build set php1_mode lsphp
./build set php2_mode no
./build set php3_mode no
./build set php4_mode no
./build litespeed
./build php n

Custombuild keeps showing this on the Remove Software tab:
LiteSpeed LiteSpeed is installed, but not enabled
PHP 7.3 PHP 7.3 is installed, but not enabled

In the end I used the Litespeed script to install it on DirectAdmin.
Bash:
bash <( curl https://get.litespeed.sh ) my-license-key-went-here
At first Litespeed's service would not start. Litespeed Support assisted with this and the service now runs as expected.

However Custombuild has not changed it's behaviour. So I can't set PHP versions or update Litespeed using custom build.
Directadmin also reports:

The service 'php-fpm72' on server 21.atservice.co.za is currently down

What I've done to try and resolve this:
  1. If I select php mode lsphp it complains that litespeed is not enabled.
  2. If I select litespeed it complains that php-frm is not compatible.
  3. If I change options.conf by hand it is changed in the background while I edit it and after I save it.

@smtalk Have you seen such behaviour before?

Logfiles:

/usr/local/directadmin/custombuild/custombuild.log
Code:
2020-10-15 17:45:13 : Apache 2.4.46 installed
2020-10-15 17:45:44 : LiteSpeed 5.4.10 installed
2020-10-15 17:45:47 : called: litespeed
2020-10-15 19:20:11 : LiteSpeed removed
2020-10-15 19:20:12 : LiteSpeed removed
2020-10-15 19:20:12 : LiteSpeed removed
2020-10-15 19:20:13 : PHP 5.6 removed
2020-10-15 19:20:13 : LiteSpeed removed
2020-10-15 19:20:13 : LiteSpeed removed
2020-10-15 19:20:14 : PHP 7.2 removed
2020-10-15 19:20:14 : PHP 7.2 removed
2020-10-15 19:20:14 : PHP 7.2 removed
2020-10-15 19:20:15 : PHP 7.4 removed
2020-10-15 19:20:15 : PHP 7.4 removed
2020-10-15 19:20:15 : PHP 7.4 removed
2020-10-15 19:20:15 : PHP 7.4 removed
2020-10-15 19:23:38 : Apache 2.4.46 installed
2020-10-15 19:23:39 : called: apache
2020-10-15 19:28:21 105.244.33.249: Apache 2.4.46 installed
2020-10-15 19:28:50 105.244.33.249: LiteSpeed 5.4.10 installed
2020-10-15 19:28:53 105.244.33.249: called: litespeed
2020-10-15 19:38:57 : Apache 2.4.46 installed
2020-10-15 19:38:59 : called: apache
2020-10-15 19:39:05 105.244.33.249: Apache 2.4.46 installed
2020-10-15 19:39:38 105.244.33.249: LiteSpeed 5.4.10 installed
2020-10-15 19:39:42 105.244.33.249: called: litespeed
2020-10-15 19:57:19 : Apache 2.4.46 installed
2020-10-15 19:57:21 : called: apache
2020-10-15 20:02:42 : Apache 2.4.46 installed
2020-10-15 20:02:43 : called: apache
2020-10-15 20:05:42 : Apache 2.4.46 installed
2020-10-15 20:05:43 : called: apache
2020-10-15 20:06:09 105.244.33.249: Apache 2.4.46 installed
2020-10-15 20:06:21 105.244.33.249: LiteSpeed 5.4.10 installed
2020-10-15 20:06:22 105.244.33.249: called: litespeed
2020-10-15 19:38:57 : Apache 2.4.46 installed
2020-10-15 19:38:59 : called: apache
2020-10-15 19:39:05 105.244.33.249: Apache 2.4.46 installed
2020-10-15 19:39:38 105.244.33.249: LiteSpeed 5.4.10 installed
2020-10-15 19:39:42 105.244.33.249: called: litespeed
2020-10-15 19:57:19 : Apache 2.4.46 installed
2020-10-15 19:57:21 : called: apache
2020-10-15 20:02:42 : Apache 2.4.46 installed
2020-10-15 20:02:43 : called: apache
2020-10-15 20:05:42 : Apache 2.4.46 installed
2020-10-15 20:05:43 : called: apache
2020-10-15 20:06:09 105.244.33.249: Apache 2.4.46 installed
2020-10-15 20:06:21 105.244.33.249: LiteSpeed 5.4.10 installed
2020-10-15 20:06:22 105.244.33.249: called: litespeed
2020-10-15 21:24:15 105.244.33.248: secure_phpini: /usr/local/php73/lib/php.ini secured
2020-10-15 21:24:17 105.244.33.248: called: rewrite_confs
 
Last edited:
Custom build would revert back to Apache & Php-Frm
No, it's LiteSpeed doing this.

I installed Litespeed several times, and got errors from Custombuild about Litespeed not being selected, then when I select it it would revert back to Php-Frm and complain about that. I also set the options.conf file manually. But this also did not work out.
I think it endlessly tries to switch back to apache, I'd suggest reporting this to LiteSpeed support. It's their script :)

However Custombuild has not changed it's behaviour. So I can't set PHP versions or update Litespeed using custom build.
Is webserver=litespeed selected?
 
No, it's LiteSpeed doing this.


I think it endlessly tries to switch back to apache, I'd suggest reporting this to LiteSpeed support. It's their script :)


Is webserver=litespeed selected?
Yes webserver=litespeed is selected unless I change php1_mode to lsphp then the config changes after saving it to: webserver=apache
 
php1_mode should be set to lsphp. It could be a bug in LiteSpeed scripts if it's reverting you back :)
 
Thanks. I've escalated this to them.

I've turned off all but php1_mode to minimize the game of whack-a-mole that has ensued. But it does keep reverting to php-frm

Will keep you posted.
 
@smtalk Litespeed seem to have resolved most things. However I now have a continual error about PHP-FPM:

The service 'php-fpm72' is currently down.

I'm unable to start the php-fpm72 service. And I'm unsure if I'm supposed to be able to. I had Openlitespeed installed on this box prior to Installing Litespeed.

Litespeed Support seem to think this is a Directadmin issue even though it's their script.

I'm not sure what I can do about this from Custombuild or Directadmin without affecting litespeed and switching to Apache.

Any hints about how I can resolve this issue?
 
What do you get if you run this?
Code:
cd /usr/local/directadmin/custombuild
./build set_fastest
./build clean
./build update
./build php
./build rewrite_confs
 
@smtalk Litespeed seem to have resolved most things. However I now have a continual error about PHP-FPM:



I'm unable to start the php-fpm72 service. And I'm unsure if I'm supposed to be able to. I had Openlitespeed installed on this box prior to Installing Litespeed.

Litespeed Support seem to think this is a Directadmin issue even though it's their script.

I'm not sure what I can do about this from Custombuild or Directadmin without affecting litespeed and switching to Apache.

Any hints about how I can resolve this issue?
You may just take it out of /usr/local/directadmin/data/admin/services.status
 
Back
Top