litespeed.service failed because a configured resource limit was exceeded

codes9

Verified User
Joined
Sep 5, 2019
Messages
15
I've rebuilt rewrite configurations and I've been digging in the logs. Came across this tidbit when rebuilding. I'm unsure how to increase resource limits or troubleshoot this issue.

./build rewrite_confs

Checking to ensure /usr/local/lsws/ssl.crt/server.ca is set.
Using 157.245.40.8 for your server IP
PHP has been secured.
Defaulting to Comodo WAF SecDefaultAction...
Restarting openlitespeed.
Job for litespeed.service failed because a configured resource limit was exceeded. See "systemctl status litespeed.service" and "journalctl -xe" for details.

#> systemctl status litespeed.service -l
Dec 19 15:46:06 server19 systemd[1]: Starting The LiteSpeed HTTP Server...
Dec 19 15:46:06 server19 lswsctrl[19535]: [OK] Send SIGUSR1 to 24600
Dec 19 15:46:08 server19 systemd[1]: Refusing to accept PID outside of service control group, acquired through unsafe symlink chain: /tmp/lshttpd/lshttpd.pid
Dec 19 15:46:08 server19 systemd[1]: Refusing to accept PID outside of service control group, acquired through unsafe symlink chain: /tmp/lshttpd/lshttpd.pid
Dec 19 15:46:08 server19 systemd[1]: Failed to start The LiteSpeed HTTP Server.
Dec 19 15:46:08 server19 systemd[1]: Unit litespeed.service entered failed state.
Dec 19 15:46:08 server19 systemd[1]: litespeed.service failed.
Dec 19 15:47:01 server19 systemd[1]: Unit litespeed.service cannot be reloaded because it is inactive.
 

bdacus01

Verified User
Joined
Jul 22, 2017
Messages
672
Location
Murfreesboro
Maybe this helps


 

codes9

Verified User
Joined
Sep 5, 2019
Messages
15
Hi Brent, Thanks a lot for those informative links. I'll put them on my shortlist of very useful info.

Does not look like a memory issue like the message suggests initially. I found some mod security files referred to in the error where missing.

But after removing mod security I now have a new error when restarting OLS:

Refusing to accept PID outside of service control group, acquired through unsafe symlink chain: /tmp/lshttpd/lshttpd.pid

I notice this is related to a service still running after OLS changed from Initd to systemd

Seems like this change has not been incorporated into the ./build rewrite_confs

I just executed /usr/local/lsws/bin/lswsctrl start

Looks like everything is running now
 

codes9

Verified User
Joined
Sep 5, 2019
Messages
15
Just in case anyone has issues restarting OLS due to PID error

 
Top