Differences

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

Link to this comparison view

Both sides previous revision Previous revision
litespeed_wiki:troubleshooting:litespeed_is_running_but_systemd_status_inactive [2018/02/28 19:40]
Jackson Zhang
litespeed_wiki:troubleshooting:litespeed_is_running_but_systemd_status_inactive [2018/02/28 21:09] (current)
Lisa Clarke Proofreading
Line 1: Line 1:
-====== LiteSpeed is running ​but systemd ​status inactive ​======+====== LiteSpeed is Running ​but systemd ​Status Inactive ​======
  
-Sometimes, you may experience a wired error. ​Litespeed ​processes are running, but system status shows inactive.+Sometimes, you may experience a weird error. ​LiteSpeed ​processes are running, but system status shows inactive.
  
   ps aux|grep http   ps aux|grep http
Line 8: Line 8:
   nobody ​   8847  0.5  0.1 208280 144056 ?       ​Sl ​  ​03:​58 ​  1:09 litespeed (lshttpd)   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)   nobody ​   8848  5.1  0.3 396704 224876 ?       ​Sl ​  ​03:​58 ​ 10:50 litespeed (lshttpd)
-  ​+
   systemctl status lshttpd.service ​   systemctl status lshttpd.service ​
   ● lshttpd.service - LiteSpeed HTTP Server   ● lshttpd.service - LiteSpeed HTTP Server
Line 16: Line 16:
    ​CGroup:​ /​system.slice/​lshttpd.service    ​CGroup:​ /​system.slice/​lshttpd.service
  
-Sometimes it may be caused by shared memory issue.+Sometimes it may be caused by shared memory issue. 
   [/​dev/​shm/​lsws]$ ls -alt ; date   [/​dev/​shm/​lsws]$ ls -alt ; date
   total 3536   total 3536
Line 38: Line 39:
   drwxrwxrwt 6 root   ​root ​      500 Jan  5 00:20 ../   drwxrwxrwt 6 root   ​root ​      500 Jan  5 00:20 ../
   ​   ​
-It seems some old files dated "Feb 10" still there. ​How to fix it?+In this case, it seems that some old files dated "Feb 10" ​are still there. ​Here's how to fix it:
  
- ​Remove files in the directory **/​dev/​shm/​lsws** with the command ​and restart ​Server+ ​Remove ​all of the files in the ''​/​dev/​shm/​lsws''​ directory ​and restart ​the server with the following commands:
  
-<​code>​rm -rf /​dev/​shm/​lsws</​code>​ +  ​rm -rf /​dev/​shm/​lsws 
-<​code>​service lsws restart</​code>​+  service lsws restart
  
-The issue is resolved and systemd status ​shows the right status:+The issue is resolved and systemd status ​is correct:
  
   systemctl status lshttpd.service   systemctl status lshttpd.service
  • Admin
  • Last modified: 2018/02/28 21:09
  • by Lisa Clarke