• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Slab Memory Creeps Up Over Time

pould

Basic Pleskian
Hi all,

This may not be a Plesk problem after all, but would welcome anyone's input.

I have a VPS with a leading provider, running Plesk on Centos. In the Advanced Memory monitor on the Plesk FrontEnd I can see that after the server is restarted the Slab Memory starts to creep up slowly until it reaches a peak maxing out the total memory on the VPS.

Running cat /proc/meminfo via SSH confirms that the Slab Memory size reported on the Plesk front end is a true reading.

This looks like a memory leak somewhere and I would welcome any advice on how to track it down.

Thanks,

P+
 
Memory is only freed when it is needed for other processes. Until then, it is possible that all memory is "used".
 
Thanks - the issue is that the slab memory creeps up over the course of a few hours. I'm looking for advice that is either (i) telling me that this is normal for Plesk and explaining why or (ii) telling me a good way to find out where the memory leak is coming from.
 
Back
Top