Centos 7.7 openlitespeed restart error

vacancy

Verified User
Hello there

After installing centos 7.7 on my Directadmin installed server, I see an error in rewrite_confs and openlitespeed restart.

Code:
[root@server custombuild]# ./build rewrite_confs
Checking to ensure /usr/local/lsws/ssl.crt/server.ca is set.
Using 51.77.1xx.xx for your server IP
Restarting openlitespeed.
Job for litespeed.service invalid.
Code:
[root@server custombuild]# systemctl status litespeed
● litespeed.service - The LiteSpeed HTTP Server
   Loaded: loaded (/etc/systemd/system/litespeed.service; enabled; vendor preset: disabled)
   Active: activating (start) since Sun 2019-09-29 08:37:31 UTC; 55s ago
  Process: 3255 ExecStart=/usr/local/lsws/bin/lswsctrl start (code=exited, status=0/SUCCESS)
 Main PID: 9947 (code=exited, status=255)
   CGroup: /system.slice/litespeed.service
           ├─1634 lsphp
           ├─1638 lsphp
           ├─1639 lsphp
           ├─1640 lsphp
           ├─1641 lsphp
           └─1642 lsphp

Sep 29 08:37:31 server.xxxxx.com systemd[1]: Starting The LiteSpeed HTTP Server...
Sep 29 08:37:31 server.xxxxx.com lswsctrl[3255]: [OK] Send SIGUSR1 to 1554
Sep 29 08:37:33 server.xxxxx.com systemd[1]: Refusing to accept PID outside of service control group, acquired through unsafe symlink chain: /tmp/lshttpd/lshttpd.pid
Sep 29 08:37:33 server.xxxxx.com systemd[1]: Refusing to accept PID outside of service control group, acquired through unsafe symlink chain: /tmp/lshttpd/lshttpd.pid
Sep 29 08:38:01 server.xxxxx.com systemd[1]: Unit litespeed.service cannot be reloaded because it is inactive.
 
Last edited:

vacancy

Verified User
I've discovered new things.

Openslitespeed is not triggered when the SSL certificate is installed and the certificate is not active on the site.

There must be something in Centos 7.7 that restricts rewrite_confs operations.

I did some research and found a bug in polkit module in centos 7.7. I downgraded the polkit 0.112-22.el7 version that came with Centos 7.7 to the 0.112-18.el7 version. I restarted the server and all of the problems resolved.

https://bugzilla.redhat.com/show_bug.cgi?id=1753037
 
Last edited:

zEitEr

Super Moderator
Good catch. I've noticed the same bug as mentioned by the link. I hope they will fix it soon. Thanks.
 
Top