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

Question WP+NGINX=HIGH APACHE MEMORY USAGE??

cloudbridge

Basic Pleskian
Hello pleskians,

Yesterday I encountered a problem that one of the server nodes was updated and then problems with RAM usage started. I tried to enable fpm to use only apache, served by NGINX, NGINX + CACHE ON. PHP versions, but I am using just the latest 7.3.1

2 days before node updates

One site (which is a news portal) uses a lot of RAM and a few days ago it wasn't. As soon as you change from NGINX to APACHE, the RAM usage is automatically reduced, but overnight it has risen from 1.5 GB to 7GB.

I upload a picture of what happens when I reset NGINX to APACHE and restore it as it was.
Rojmxtg

Maybe someone has encountered that and could advise?

Plesk Onyx
Version 17.8.11 Update # 40, last updated on Feb 15, 2019 09:56 PM
 

Attachments

  • Screenshot_1.jpg
    Screenshot_1.jpg
    105 KB · Views: 18
One suggestion without know the root cause of your issue: PHP-FPM 7.3 is buggy, downgrade to 7.2.
Forwarded to devs - PHP 7.3 FPM dies without a trace

However, you should also analyze your access_log and error_log files of the site that is using much RAM. Frequently this is caused by brute force attacks or long or infinitely long running PHP scripts.

Hi Peter,
do you know if 7.3.3. is still "buggy"? (Forwarded to devs - PHP 7.3 FPM dies without a trace).
Thanx a lot in advance!
 
We've not been offering it to customers due to the issues, I don't know what the status is. But I have not read in any release notes about fixes of the issue.
 
Back
Top