1GB limit for a website => crash entire MariaDB server if limit exceeds

SYSTEM INFORMATION
OS type and version Debian 11
Virtualmin version 7.10.00

Scenario:
An user attempted to load files on a virtual server (Wordpress) exceeding quota limit (1GB) and
MariaDB went crazy.

Log:
May 08 17:08:04 mariadbd[130398]: 2024-05-08 17:08:04 0 [Warning] Could not increase number of max_open_files to more than 32768 (request: 128206)
May 08 17:08:04 mariadbd[130398]: 2024-05-08 17:08:04 0 [Note] Starting MariaDB 10.5.23-MariaDB-0+deb11u1 source revision 6cfd2ba397b0ca689d8ff1bdb9fc4a4dc516a5eb as>
May 08 17:08:26 mariadbd[130731]: 2024-05-08 17:08:26 0 [ERROR] InnoDB: preallocating 573440 bytes for file ./***/wp_posts.ibd failed with er>
[hundreds of lines, around 10 per second]
May 08 17:08:31 mariadbd[130731]: 240508 17:08:31 [ERROR] mysqld got signal 6 ;

And MariaDB crashed for entire server. Dozens of sites down.

Fixed:
Fixed by giving more quote to website and repairing hundreds of tables on other sites hosted on server :frowning: .

Well, that’s disturbing. I’m not sure it is something WM/VM can control though. We’ve seen instances of the DB being killed by OOM (out of memory) killer. How much physical and virtual memory do you have?

1 Like

64GB RAM, 4GB Virtual memory.

I was having the same issue. Idk what’s the reason behind it.

Thought this was solved?

Have you tried the OP’s solution to the problem?

Sorry what is the OP’s solution?

In Virtualmin, when a user reaches their disk quota limit (for example, by uploading files) and concurrently, there is an attempt to write to an InnoDB table in MariaDB, the table can become corrupted. MariaDB will then attempt to repair the corrupted table by trying to allocate disk space. However, it won’t find the needed space due to the disk quota limit being reached. This situation causes multiple repair instances to initiate, which can lock MariaDB, affecting all other sites on the server and essentially causing a complete halt.

When someone says “Fixed” it suggests pretty conclusively that it has been “Solved”.

But I, probably like you, and everyone on here, would rather they would use the “Solved” option rather than simply editing the original post.

I appreciate your point about the terminology used, like ‘Fixed’ versus ‘Solved’. However, beyond the semantics of the words, my main hope is that the issue itself will be effectively resolved. :slight_smile:

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.