• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Websites stop working until I restart apache and nginx

Is there a high cpu load when the website goes down? What processes are causing it? Is there a high RAM usage at that time? You can watch the load "live":
Code:
# MYSQL_PWD=`cat /etc/psa/.psa.shadow` watch "uptime && echo "\ " && ps aux | sort -nrk 3,3 | head -n 20 && echo "\ " && mysqladmin proc status -u admin"
 
There is no high CPU or memory usage. In fact, when the site goes down, we have to restart the Apache server every time. Until then, the website keeps going up and down intermittently.
 
When the outage occurs, have you tried to restart the PHP-FPM service instead of restarting Apache? If CPU and RAM are good, there is a chance that there is actually no issue with Apache. How do Apache processes behave when an outage occurs? E.g. what is "strace" showing on the processes? Are they actively doing anything? Or are they really dead?
 
No, we have not tried restarting the PHP-FPM service, but it is currently running on the server. How can we determine the actual root cause of this issue? Is it related to PHP-FPM or Apache?
 
What state are Apache (httpd, apache) processes in when Apache seems to be down? Did you try to "strace" any of them? Are they just orphans or are they doing anything? Are they consuming RAM and CPU power? If they are consuming CPU power, what are they doing? Does strace give any clues (mostly it reveals the name of some website(s) that a process is currently handling, e.g. by mentioning file names)?
 
Back
Top