• 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 Cache is growing. Server is no longer accessible.

straddi

Basic Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
Plesk Obsidian 18.0.68 Update 2
I hope you can help me.
As the image below shows, my cache is starting to grow and fill up the RAM. This means the server is inaccessible from the outside and essentially shuts down. After a restart, the problem is resolved for a while, but then it starts all over again.
I've already disabled cron jobs and put installed programs into maintenance mode, but that doesn't help.
How can I find out which program is using the cache?
Shouldn't Debian or Plesk solve the problem themselves by freeing up cache for this case?
 

Attachments

  • Cache-laeuft-voll.jpg
    Cache-laeuft-voll.jpg
    38.4 KB · Views: 8
  • Server_ausfall.jpg
    Server_ausfall.jpg
    53.7 KB · Views: 9
Hi

Install plugin Fail2Ban and configure it as it’ll likely be your Plesk login page being attacked which is happening to most Plesk installations.
 
Cache is not used by programs or processes. It is related to I/O. Linux loads as much I/O data as possible to cache because it's much faster than reading from storage. A lot of cache is normally not a problem and shouldn't bring the system down. The OS should manage it automatically, like you mentioned.

This sounds more like something is taking a massive amount of I/O, which increases cache, and it eventually overloads the server. What's the CPU and disk usage like?
 
Back
Top