• 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.

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