• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Apache2 keeps restarting..

Erjen

New Pleskian
My Apache2 service restarts just random. I tried a lot, following a lot of guides (configured graceful reload instead of restart, changed Apache restart interval etc, rebooted the server etc.).

But it just keeps restarting. Sometimes in 15 minutes, sometimes it takes an hour but at least every hour..
The error logs says just this: [mpm_prefork:notice] [pid 18192] AH00169: caught SIGTERM, shutting down
So something is triggering the restart. Memory usage etc. is just fine. And during restarts, no one is making changes in Plesk. It happens every hour, even at night.

Anyone an idea what is triggering it?
 
This can be caused by a lot of things. One of the most frequent causes is resource overuse, e.g. too many httpd processes/instances running. I suggest to monitor the numberr of httpd instances, maybe it gives you an idea what is happening
# ps aux | grep sbin/httpd | grep -v grep | wc -l
If they are constantly increasing until the SIGTERM is monitored, you could try to use
# strace -p <pid>
to look into a process to see what it is doing to investige the issue further.

It could maybe help, too, to monitor what the top 20 (or another number) processes are doing, like
# watch "ps aux | sort -nrk 3,3 | head -n 20"
Maybe you have one or two that are constantly requiring a lot of CPU attention, then that's the point to look further.
 
None of it was an issue, but thanks a lot for your time and response.
In the end, I configured Nginx as a reverse proxy. All problems gone now :( very strange but solved.
 
Back
Top