cPFence UI is Here – Security Management, Now with a Mouse!
Version 3.3.35 (23rd February 2025)
Added
- cPFence Owl now keeps a watchful eye on your critical server services!
Stay ahead of downtime with real-time monitoring for MySQL, Web Server, DNS, and Main Control Panel services. cPFence Owl will:
Instantly notify you when any of these services go down.
Attempt to restart the service once immediately.
If unsuccessful, it will automatically retry after one hour to prevent endless restart loops.
Be the first to know when issues strike and let cPFence handle recovery efforts for you.
- MonitorPro UI Editor – smarter, simpler domain management at your fingertips:
You can now manage your MonitorPro list directly from the UI. Easily add, edit, or remove monitored domains and modify Keyword Monitoring without manually editing configuration files.
Improved
- WAF rules have been optimized for better performance, fully adapting to the new Enhance v12 architecture.
Fixed
- Resolved an issue where cPFence was not detecting OpenLiteSpeed (OLS) / LiteSpeed Web Server on some servers.
- Edited
Instantly notify you when any of these services go down.
I'm getting about hourly email notifications regarding openlitespeed being down and restarted from only one server that's dedicated to one client, small VPS. I doubt that openlitespeed has been down though, as the websites on it have been running smooth for over a year without complaints.
Every "Current Processes output" attached with the email also just shows it running with long "elapsed" times. So I'm a bit confused about what's going on there.
Yes, we noticed this on one of our test servers today. It seems that OLS is crashing and restarting itself repeatedly for some odd reason, causing the service to stay in an "activating" state instead of the expected "active" state. I haven’t had time to investigate further, but I fixed it by running:
systemctl stop lshttpd
systemctl disable lshttpdThen:
systemctl enable lshttpd
systemctl start lshttpdYou can verify if it has stabilized by watching its state:
watch -n 1 'systemctl show lshttpd --property=ActiveState --value'- Edited
After that it also keeps flipping from Active to Activating, with an openlitespeed (lscgid) process popping up every few seconds. However, the original openlitespeed process stays active, with the long elapsed time intact and the websites keep working all the time no matter what. Weird. Could be something misconfigured in the systemd file for openlitespeed.
Try this after stopping and disabling OLS:
pkill -9 lshttpdThen enable it back and see if that helps. Not sure what’s causing the issue, but it seems like something that needs to be fixed in v12, though I could be wrong. Might investigate it further when time allows.
Anyway, the next version of cPFence Owl will ignore the "Activating" state for OLS, at least for now.
- Edited
Version 3.3.36 (24th February 2025)
Added
- Owl now monitors AppCD service:
The Owl module now includes real-time monitoring for the AppCD service, ensuring it stays online along with other critical services.
Improved
- Further optimizations to WAF rules for the Enhance v12 architecture to prevent conflicts with certain pages and plugins.
- The Owl module will now disregard the “Activating” state for the OLS web server and will no longer flag it as down.
Check out our latest blog post :
IPv6 Security & Database Scanning: Why cPFence Leads the Way
cPFence Not sure what’s causing the issue, but it seems like something that needs to be fixed in v12, though I could be wrong. Might investigate it further when time allows.
To me it most looked like the openlitespeed process was getting detached from the lshttpd systemd process, hence it's attempting restarts, which fail because it's already running. I noticed as well that the systemctl status lshttpd was different between servers in terms of prestart commands related to the swap, could be a remnant of the fix that was pushed earlier.
Killing the running and working disconnected openlitespeed process allowed the systemd process to restart it under its own wings so to say, and it stopped the cycle. A systemctl daemon-reload && systemctl reload lshttpd on all servers then caused them to all show the same status, and no restarts. Perhaps the enhance fix should have forced the daemon-reload and systemctl reload.
Try this:
systemctl stop lshttpd
systemctl disable lshttpd
pkill -9 lshttpdThen verify if the processes are gone:
netstat -tulnp | grep :7080If not, kill it manually:
kill -9 <PID> # Get the PID from the netstat command aboveVerify again:
netstat -tulnp | grep :7080Once the process is gone, run these:
systemctl reset-failed lshttpd
systemctl enable lshttpd
systemctl start lshttpdBlah... the issue resurfaced today on the server that was stable since running those commands.
Btw, what is cPFence downloading every hour? Seems to add up to about 2.5GB per server per day. Not huge or anything, but would it be possible to make this once a day or so? Or would there be potential downsides to that?