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

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