Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:troubleshooting:litespeed_is_running_but_systemd_status_inactive [2018/02/28 19:24]
Tihomir created
+++ litespeed_wiki:troubleshooting:litespeed_is_running_but_systemd_status_inactive [2018/02/28 19:40]
Jackson Zhang
@@ Line 1: / Line 1: @@
 ====== LiteSpeed is running but systemd status inactive ======
-If you have problem updating LiteSpeed WebServer through control panel (like cPanel, DirectAdmin) or the status is inactive but LiteSpeed is running you can do:
+Sometimes, you may experience a wired error. Litespeed processes are running, but system status shows inactive.
-. Login to your server through ssh.
+  ps aux|grep http
+  root      8806  0.2  0.1 190080 143460 ?       S    03:58   0:36 litespeed (lshttpd)
+  root      8809  0.0  0.0  18256   568 ?        S    03:58   0:00 httpd (lscgid)
+  nobody    8847  0.5  0.1 208280 144056 ?       Sl   03:58   1:09 litespeed (lshttpd)
+  nobody    8848  5.1  0.3 396704 224876 ?       Sl   03:58  10:50 litespeed (lshttpd)
+  systemctl status lshttpd.service
+  ● lshttpd.service - LiteSpeed HTTP Server
+   Loaded: loaded (/etc/systemd/system/lshttpd.service; enabled; vendor preset: disabled)
+   Active: failed (Result: exit-code) since Thu 2018-02-22 03:55:26 CET; 3h 35min ago
+   Main PID: 29752 (code=killed, signal=KILL)
+   CGroup: /system.slice/lshttpd.service
-. Remove files in the directory **/dev/shm/lsws** with the command:
+Sometimes it may be caused by shared memory issue.
+  [/dev/shm/lsws]$ ls -alt ; date
+  total 3536
+  -rw------- 1 nobody nobody  147456 Feb 23 04:58 .store.0.shm
+  -rw-r----- 1 root   nobody 2637824 Feb 23 04:06 .quicshmdata.shm
+  -rw-r----- 1 root   nobody    8192 Feb 23 04:01 .quicshmmap.lock
+  -rw-r----- 1 root   nobody    8192 Feb 23 04:01 .quicshmdata.lock
+  -rw------- 1 nobody nobody  262144 Feb 22 23:02 .store.1.shm
+  -rw------- 1 nobody nobody  212992 Feb 22 20:32 .store.2.shm
+  -rw------- 1 nobody nobody   98304 Feb 21 14:49 .store.3.shm
+  -rw------- 1 nobody nobody    8192 Feb 21 07:40 .cachemanidx.lock
+  -rw------- 1 nobody nobody  147456 Feb 15 01:59 .cachemanidx.shm
+  -rw-r----- 1 root   nobody   32768 Feb 12 20:54 .quicshmmap.shm
+  -rw------- 1 nobody nobody    8192 Feb 10 00:29 .store.2.lock
+  -rw------- 1 nobody nobody    8192 Feb 10 00:28 .store.1.lock
+  -rw------- 1 nobody nobody    8192 Feb 10 00:23 .store.3.lock
+  -rw------- 1 nobody nobody    8192 Feb 10 00:22 .store.0.lock
+  drwxr-x--- 2 nobody nobody     360 Feb 10 00:22 ./
+  -rw------- 1 nobody nobody    8192 Feb 10 00:22 adns_cache.lock
+  -rw------- 1 nobody nobody   16384 Feb 10 00:22 adns_cache.shm
+  drwxrwxrwt 6 root   root       500 Jan  5 00:20 ../
+It seems some old files dated "Feb 10" still there. How to fix it?
+ Remove files in the directory **/dev/shm/lsws** with the command and restart Server
 <code>rm -rf /dev/shm/lsws</code>
+<code>service lsws restart</code>
-.1 Restart LiteSpeed WebServer
+The issue is resolved and systemd status shows the right status:
-. Update Litespeed Webserver to the latest version with command:
-<code>/usr/local/lsws/admin/misc/lsup.sh -f -v <version number></code>
-You can get version number from this page ( https://www.litespeedtech.com/products/litespeed-web-server/release-log ).
-==== Example ====
-<code>/usr/local/lsws/admin/misc/lsup.sh -f -v 5.2.4</code>
+  systemctl status lshttpd.service
+  ● lshttpd.service - LiteSpeed HTTP Server
+   Loaded: loaded (/etc/systemd/system/lshttpd.service; enabled; vendor preset: disabled)
+   Active: active (running) since Fri 2018-02-23 07:35:46 CET; 9s ago
+  Process: 1620 ExecStart=/usr/local/lsws/bin/lswsctrl start (code=exited, status=0/SUCCESS)
+  Main PID: 1639 (litespeed)
+   CGroup: /system.slice/lshttpd.service
+           ‣ 1639 litespeed (lshttpd)