• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Question MariaDB Warning for "Could not increase number of max_open_files to more than 32768 (request: 80555)"

Azurel

Silver Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
18.0.68#2
Today I restartet MariaDB and found in /var/log/messages this lines:
Apr 4 09:19:48 web1 systemd[1]: Stopped MariaDB 10.11.11 database server.
Apr 4 09:19:48 web1 systemd[1]: Starting MariaDB 10.11.11 database server...
Apr 4 09:19:48 web1 mariadbd[11927]: 2025-04-04 9:19:48 0 [Warning] Could not increase number of max_open_files to more than 32768 (request: 80555)
Apr 4 09:19:48 web1 systemd[1]: Started MariaDB 10.11.11 database server.

I found this article too https://support.plesk.com/hc/en-us/...e-number-of-max-open-files-to-more-than-16384

However, the article seems to be incorrect. Because:
Search for
# egrep -r LimitNOFILE /lib/systemd/system/m*
/lib/systemd/system/mariadb.service:LimitNOFILE=32768
/lib/systemd/system/[email protected]:LimitNOFILE=32768
/lib/systemd/system/mysqld.service:LimitNOFILE=32768
/lib/systemd/system/mysql.service:LimitNOFILE=32768
and all this files says:
It's not recommended to modify this file in-place, because it will be overwritten during package upgrades.

It would be nice if someone could enter a correct description
 
Can't edit post because short edit limit.

It should point to folder /etc/systemd/system/mariadb.service.d create new file like "custom_limits.conf" put in it a value you need. I have 128GB RAM so I add:
[Service]
LimitNOFILE=250000

After that call
# systemctl daemon-reload
# systemctl restart mariadb

Check with
# systemctl status mariadb

Warning is gone.
 
Back
Top