Bug#1025535: mariadb-server-10.5: Systemd mariadb.service and LimitNOFILE=32768
> Thanks for reporting https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025535 > > This systemd file is inherited from upstream and not customized in > Debian. Have you considered contributing a fix upstream, or checking > if this is already reported at jira.mariadb.org? I didn't get any reply on my message above. It would be great if you could contribute this fix directly to upstream systemd files (see https://github.com/MariaDB/server/tree/main/support-files).
Bug#1025535: mariadb-server-10.5: Systemd mariadb.service and LimitNOFILE=32768
Thanks for reporting https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025535 This systemd file is inherited from upstream and not customized in Debian. Have you considered contributing a fix upstream, or checking if this is already reported at jira.mariadb.org?
Bug#1025535: mariadb-server-10.5: Systemd mariadb.service and LimitNOFILE=32768
Hi! Latest version of MariaDB in Debian unstable/testing/Bookworm is 10.11.2. You might want to consider testing it. If you want to contirbute in the open source way to fix this or any other issue, see https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian on how to submit a Merge Request! If you have time to help, please consider these (in order of importance): 1. Review current open MRs at https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests 2. Review items highlighted by Debian QA systems (Lintian, builds etc) and submit a fix to improve the quality: https://tracker.debian.org/pkg/mariadb 3. Review what testing we have at https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines and think about potential gaps - CI is very important as it is the only way we can prevent regressions in a scalable way 4. Review/follow-up on existing bugs that currently need more information: https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=mariadb&src=mariadb-10.6&src=mariadb-10.5&src=mariadb-10.3&src=mariadb-10.1 MariaDB and C++ skills are useful, but not required. For example reviewing the NEWS for 10.11 requires no coding skills: https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/37 My request for help from debian-devel in https://lists.debian.org/debian-devel/2023/02/msg00272.html did not get many responses, so the future of this package depends on how active the users and people who previously reported bugs are in participating in the maintenance of the package. - Otto
Bug#1025535: mariadb-server-10.5: Systemd mariadb.service and LimitNOFILE=32768
Package: mariadb-server-10.5 Version: mariadb-server Severity: minor Dear Maintainer, unit /lib/systemd/system/mariadb.service contains line: LimitNOFILE=32768 That do not allow set a cust value of open_files_limit in [mysqld] section. I.e. [mysqld] open_files_limit= 10 does not have any effect: MariaDB [(none)]> SHOW VARIABLES LIKE 'open_files_limit'; +--+---+ | Variable_name| Value | +--+---+ | open_files_limit | 32768 | +--+---+ 1 row in set (0.001 sec) if you change LimitNOFILE=32768 in /lib/systemd/system/mariadb.service into: LimitNOFILE=infinity LimitMEMLOCK=infinity after a systemctl daemon-reload && systemctl restart mariadb.service you get 32768 as default but it is possible change value of open_files_limit MariaDB [(none)]> SHOW VARIABLES LIKE 'open_files_limit'; +--++ | Variable_name| Value | +--++ | open_files_limit | 10 | +--++ finally I suggest to analyze if remove LimitNOFILE=32768 is safe but at least, change the comment that is misleading [...# Number of files limit. previously [mysqld_safe] open-files-limit...] TIA Alessandro - Lota
