• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved After Plesk-Update 18.0.69 Update 3 mariadbd high memory usage - every time - also after every server restart

mcac

Basic Pleskian
Server operating system version
Almalinux 8.10
Plesk version and microupdate number
18.0.69 Update 3
Since today one of our servers have issues with high memory usage of mariadbd. I have checked all steps https://support.plesk.com/hc/en-us/...TM1MjgkbzU5JGcxJHQxNzQ2Njk5MzIyJGozNiRsMCRoMA..

There are no error-logs.
There are no slow querries.
Performance boost executed
restarts executed
it is enough free disk space

After every restart of mariadbd the memory usage of mariadbd is 74 % and more.

I don't know what is the reason. I did not find any reasons in this forum.

The server works not stable because of this high memory usage.

What can I do.

The issues began tonight after automatically Plesk Update. At 3.45 o clock i got the message, that

Plesk Obsidian 18.0.69 Update 3 was installed​

After the time the MySQL server does not run correctly. (Many hours gone) After a server restart, the mysql server runs, but with many memory usage.
 
Reason found:
There was a entry in /etc/mysql/my.cnf with high innodb_buffer_pool_size. Entry deleted and service restarted and now the high memory usage is obsolet.
I don't know, why there was no problems before. I think, the update was not the reason.
 
Back
Top