Anyone else noticed this? I noticed it on one server at first, but it keeps appearing and now it's on another server as well. If I'm not the only one, it's worth putting in a ticket.
What happens is, if you run systemctl status lshttpd you will see something like lshttpd.service: Scheduled restart job, restart counter is at 351.. The openlitespeed process is actually running fine, but the systemd process seems to think it died, attempts a restart, which fails because it already exists, and it gets stuck in an endless loop of restarts. I've seen restart counters of >5000 without a second of downtime, but the restart process eats up a bit of CPU.
To temporarily fix it, find the running openlitespeed process, kill it, and the systemd process spawns a new one and it will be working fine again for 2-12 hours or so before going off the rails again. These two servers were added fresh to the estate and have only ever seen V12.
Anyone experiencing the same?
