• 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 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 Out of memory but plenty of memory

Thank you all, I'll think about migrating to something else. In any case a dedicated server is way an overkill.
The current host has told me they guarantee the 8GB 100%, no matter what.

Besides, I checked with the online mySQL calculator and with current settings (i.e., 2GB innodb_buffer_pool_size) I reach just 3.2GB.

What about upgrading to Almalinux 9 as an attempt of last resort? How complex is that?

If that's the case, then it's likely an abusive or malicious bot/vulnerability sniffer that causes your memory usage to surge so much that OS invokes the OOM killer to avoid kernel panic so you might want to check access logs if you want to try and track it down.

Almalinux 9 is solid and has a great long runway!
 
Hi all, I wanted to provide some sort of a conclusion on this issue : after various attempts described here and more, the best progress was obtained by disabling firewalld (while keeping the Plesk firewall. I think I could have made the opposite choice too). It was difficult to believe, but having two active firewalls - which I was not aware of - messes us the system. It is now 10 days without a crash a 5 since I last restarted MariaDB and things look quite stable : no OOM messages, no segfault or php-fpm crashes. Fingers crossed.

The strange thing is that I was (unconsciously) running the 2 firewalls with CentOs and never had any issue. Almalinux looks a bit more sensitive on that, obviously.
 
Back
Top