In Progress UPS-428 - Ubuntu litespeed not working

[vacancy]

Hi

After installing litespeed on the server with Ubuntu, when we want to make a litespeed switch, litespeed is not active because the httpd module is not recognized.

[email protected]:/usr/local/lsws/admin/misc# ./cp_switch_ws.sh lsws
Detected cPanel WHM Environment
Failed to stop httpd.service: Unit httpd.service not loaded.
./cp_switch_ws.sh: 449: RETRY--: not found
./cp_switch_ws.sh: 449: RETRY--: not found
./cp_switch_ws.sh: 449: RETRY--: not found
./cp_switch_ws.sh: 449: RETRY--: not found
./cp_switch_ws.sh: 449: RETRY--: not found
./cp_switch_ws.sh: 449: RETRY--: not found

 

[cPRex]

Hey hey! I've confirmed this behavior and opened case CPANEL-39952 with our developers. I'll be sure to post a reply here once I have an update!

 

[cPRex]

Update - I've spoken directly with Litespeed about this since they are the ones that maintain the script. They are going to get that resolved on their side, so we've changed the case to UPS-428 to reflect that it won't be handled by cPanel development.

 

[vacancy]

Is there a case update on the cpanel side regarding this issue?

Litespeed switch operation still cannot be performed on Ubuntu servers.

I also reported the problem to litespeed, but they could not produce a solution.

[email protected]:/usr/local/lsws/admin/misc# ./cp_switch_ws.sh lsws
Detected cPanel WHM Environment
Failed to stop httpd.service: Unit httpd.service not loaded.
Apache Stopped.
---
metadata:
command: configureservice
reason: Enabled monitoring for httpd.
result: 1
version: 1
Failed to start httpd.service: Unit httpd.service not found.
LiteSpeed is not up within 30 secs, try again by removing /tmp/lshttpd/.
Failed to start httpd.service: Unit httpd.service not found.
[ERROR] LiteSpeed is not up within 60 secs, please check the error log and try again.

 

[cPRex]

I've reached out to the team and I'll let you know what I find out! It's important to note that "UPS" cases mean "upstream" so we don't have much control over how those happen.

 

[cPRex]

@vacancy - I reached out to Litespeed and they said this should no longer be happening on new servers. If you could send me the output of "journalctl -xe" that could be helpful, or they said if you create a ticket with them directly they would fix it quickly.