• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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: 6
  • Server_ausfall.jpg
    Server_ausfall.jpg
    53.7 KB · Views: 7
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