• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Troubleshooting high memory usage of Apache & PHP-FPM

elbobo

New Pleskian
Server operating system version
Debian 11.9
Plesk version and microupdate number
Plesk Obsidian v18.0.57_build1800231218.09 os_Debian 11.0
Hello!

I have Plesk Obsidian 18.0.57 Web Pro Edition installed on a VM with 8 GB of RAM and I am currently hosting 26 domains. During the last month I am having outages because of high memory utilization from Apache and PHP-FPM according to Plesk's messages and sometimes even the server reboots.

How can I go about to find the root cause?
What I would like to do is first get statistics of every domains consumption for a small period of time, then find how much the total memory consumption from all domains as a percentage of the whole memory and then perhaps start to limit memory consumption for specific domains.
 
Are you able to SSH or login to Plesk while the incidents are occurring or is this an "after hours" type of scenario each time?
 
Have you tried to upgrade Plesk? You cloud also try to upgrade the OS but first you have to update to the latest Plesk version
Bash:
plesk installer upgrade plesk stable
https://support.plesk.com/hc/en-us/...-upgrade-procedure-on-Linux-server-with-Plesk
In case this related to an high amount of traffic, have you tried to use nginx caching?
You could watch your logs or use "btop" to see whats going on.
Bash:
tail -f /var/www/vhosts/*/logs/*log

Maybe you want to try a dedicated PHP handler, you could isolate the process better.

 
Back
Top