Remove LiteSpeed completely

#1
Hi
I am trying to remove LiteSpeed but there some error when remove it

I want to remove LiteSpeed completely and back to Apache

I am using trial version of LiteSpeed

uninstall Litespeed using the following commands:

Code:
/usr/local/lsws/admin/misc/cp_switch_ws.sh apache

/usr/local/lsws/admin/misc/uninstall.sh
I get this error

Code:
root@server ~]# /usr/local/lsws/admin/misc/cp_switch_ws.sh apache
Detected Plesk Environment
LiteSpeed is running, stop it first.
Redirecting to /bin/systemctl stop lsws.service
LiteSpeed Stopped.
Removed symlink /etc/systemd/system/multi-user.target.wants/lshttpd.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/lshttpd.service to /usr/lib/systemd/system/lshttpd.service.
Redirecting to /bin/systemctl start httpd.service
Job for lshttpd.service failed. See "systemctl status lshttpd.service" and "journalctl -xe" for details.
[ERROR] Apache is not up within 30 secs. Please check the log file.
[root@server ~]#

Code:
[root@server ~]# /usr/local/lsws/admin/misc/uninstall.sh

WARNING:

All sub directories under "/usr/local/lsws"
created during installation will be removed!
However, conf/ and logs/ can be optionally preserved.
If you want to preserve any file under the other sub-directories created
by installation script, please backup before proceeding.

Manually created sub-directories under "/usr/local/lsws"
will not be touched.

Do you want to uninstall LiteSpeed Web Server? [y/N]y

LiteSpeed web server is running, it must be stopped in order to continue
uninstallation.

Would you like to stop it now? [Y/n]Y

Detected Plesk Environment
LiteSpeed is running, stop it first.
Redirecting to /bin/systemctl stop lsws.service
LiteSpeed Stopped.
Redirecting to /bin/systemctl start httpd.service
[ERROR] Apache is not up within 30 secs. Please check the log file.
touch: cannot touch ‘/etc/disablecsp/litespeed’: No such file or directory
touch: cannot touch ‘/etc/disablecsp/litespeed’: No such file or directory
[OK] litespeed: stopped.

Do you want to keep server configuration files? [y/N]N

Do you want to keep server log files? [y/N]N

LiteSpeed Web Server has been successfully uninstalled.
[root@server ~]#

Still Apache down

[root@server ~]# service httpd restart
Redirecting to /bin/systemctl restart httpd.service
Job for lshttpd.service failed because the control process exited with error code. See "systemctl status lshttpd.service" and "journalctl -xe" for details.
[root@server ~]#

Unable to start service: Unable to manage service by apache_control_adapter: ('start', 'web'). Error: INFO: [Wed Jul 15 13:24:24 CEST 2020]: Service: httpd, Action: start Trying to start service httpd... activating Jul 15 13:24:29 server.hostname.com systemd[1]: Failed to start LiteSpeed HTTP Server. Jul 15 13:24:29 server.hostname.com systemd[1]: Unit lshttpd.service entered failed state. Jul 15 13:24:29 server.hostname.com systemd[1]: lshttpd.service failed. ***** problem report ***** Warning: start service httpd failed /usr/local/psa/admin/sbin/pleskrc execution failed: Job for lshttpd.service failed because the control process exited with error code. See "systemctl status lshttpd.service" and "journalctl -xe" for details.
My server still down till now

I hope anyone can help me

Thanks
 

Pong

Administrator
Staff member
#2
This is a ticket for the same topic. Removing LSWS from plesk is very easy but it will need to follow the right process. For example, first step is to switch to apache.
Code:
/usr/local/lsws/admin/misc/cp_switch_ws.sh apache
if "[ERROR] Apache is not up within 30 secs. Please check the log file." Apache could not be started, it is not a LiteSpeed issue at all. it may caused by bad apache configuration. You will need to fix it first before any further step to remove LSWS. ( There is no harm to leave LSWS there without removing since after switching to apache, LSWS has no effect at all and /usr/local/lsws is taking very small space.

If Apache can not be started, you can also console Plesk support. It is out of the LiteSpeed support scope to fix your plesk Apache issue.
 
Top