• 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.

Resolved Cgroups enabled, graceful apache restart doesn't work

karam

Basic Pleskian
So, although am not sure if that's the problem, but we've changed nothing but buying cgroups extension, we directly noticed the problem of apache graceful restart.
As soon as we add any subdomain to any other domains, EVERY domain will have gateway problem for brief seconds.

I would like to ask someone using cgroups for confirming the same behavior. Thank you.
 
There are no known problems with cgroup and Apache graceful restart.
If you can clearly reproduce the problem and describe it in detail with error messages in the logs, then open the report here Reports
 
Changing the subdomain requires an Apache reload/restart. Is your GracefulShutdownTimeout still the same? If it's too short, queued reqs will be cut off.

Edit: too tired. Meant adding a subdomain makes a vhost change

- check apache logs.
 
Changing the subdomain requires an Apache reload/restart. Is your GracefulShutdownTimeout still the same? If it's too short, queued reqs will be cut off.

Edit: too tired. Meant adding a subdomain makes a vhost change

- check apache logs.
I see, well my current GracefulShutdownTimeout as shown in httpd.conf file is 3
I didn't change it at all.

I'll do more investigation on this, but thanks for the information you provided.
 
Apache restart intervall should no be less than 120 seconds. A potential system timeout for an Apache kill should not be less than 30 seconds on low-load systems, and not less than 2 minutes on high load systems to give the web server enough time for shutdown and restart.
 
Back
Top