• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Issue Apache & PHP-FPM Memory Usage Growing Exponentially

stevewest15

New Pleskian
Server operating system version
CentOS 7.9.x
Plesk version and microupdate number
18.0.48
Hi,

Recently (since mid-Sept 2022), on all of our Plesk servers, I've been seeing the same issue w/ Apache & PHP-FPM memory usage growing exponentially. Prior to mid-Sept 2022, Apache PHP-FPM was stable (as you can see from the attached Plesk_Monitoring_Services_12months.png).

Not much has changed across the servers besides Plesk updates and routine OS updates (CentOS 7.9.x). On the impacted servers, we haven't added any new websites or email services. The only change I can recall recently is the deactivation of PHP 7.4 (due to EOL security updates) and the switching of most client websites (WordPress) to PHP 8.0.x or 8.1.x).

Any ideas about what could be causing the Apache PHP-FPM memory increase? See attachments for additional details.

Thank you,

SW
 

Attachments

  • Plesk_Monitoring_Memory_12months.png
    Plesk_Monitoring_Memory_12months.png
    209.8 KB · Views: 22
  • Plesk_Monitoring_Overview_12months.png
    Plesk_Monitoring_Overview_12months.png
    152.9 KB · Views: 17
  • Plesk_Monitoring_Services_12months.png
    Plesk_Monitoring_Services_12months.png
    497 KB · Views: 20
  • Plesk_PHP_Settings.png
    Plesk_PHP_Settings.png
    96.6 KB · Views: 18
  • ps_aux.png
    ps_aux.png
    809.9 KB · Views: 16
It could be a memory leak in one of the PHP scripts or a bot attack on your server.
Did you check the logs to see what's going on?

Code:
# tail -f /var/www/vhosts/system/*/logs/error_log

# tail -f /var/www/vhosts/system/*/logs/proxy_access_ssl_log
 
Back
Top