Issue WARN: Cannot store disk usage for DB 238

[Dave W]

Server operating system version

CentOS Linux release 7.9

Plesk version and microupdate number

Plesk Obsidian 18.0.57.5

Greetz,

Anyone seen this;

Run

plesk sbin statistics --calculate-one --domain-name=domain.tld

get a ton of;

WARN: Cannot store disk usage for DB 204: domain 305 does not exist
WARN: Cannot store disk usage for DB 205: domain 305 does not exist
WARN: Cannot store disk usage for DB 206: domain 305 does not exist
WARN: Cannot store disk usage for DB 207: domain 312 does not exist
WARN: Cannot store disk usage for DB 208: domain 315 does not exist
WARN: Cannot store disk usage for DB 209: domain 313 does not exist

We use an external Mariadb server.

D.

 

[Peter Debik]

Looks like a database inconsistency. It can probably be resolved by running plesk repair db -y.

 

[Kniar]

Same problem and plesk repair db didn't fix it.

 

[Peter Debik]

What version of MariaDB are you using? The problem is only known for 5.x version so far. What is the setting of the variable "innodb_file_per_table"?

 

[Kniar]

# mysql -V
mysql Ver 15.1 Distrib 5.5.68-MariaDB, for Linux (x86_64) using readline 5.1

MariaDB [(none)]> SHOW VARIABLES LIKE 'innodb_file_per_table';
+-----------------------+-------+
| Variable_name | Value |
+-----------------------+-------+
| innodb_file_per_table | OFF |
+-----------------------+-------+

I updated Plesk from 18.0.57 to 18.0.58 and this fixed the problem.

 

[Peter Debik]

There are two underlying issues that need fixing: For one, the 5.5 version of MariaDB is more than just outdated. This will cause trouble in the future with other aspects of the software, too. For example you will need to convert your server to Alma 8 soon, because CentOS 7.9 is out of life. This won't work with MariaDB 5.5. Make sure to upgrade to MariaDB 10.5 and then - in a second step - from 10.5 to 10.11. Do not attempt to upgrade directly. Please check out this KB article on how to upgrade MariaDB: https://support.plesk.com/hc/en-us/...-5-to-5-6-5-7-or-MariaDB-5-5-to-10-x-on-Linux

The second is the innodb_file_per_table setting. I think the "OFF" can be the cause for the issue described above. It should be "ON" if I remember correctly. But again, with the upgrade to the newer MariaDB version this may no longer be required.