Probably a last note on this topic for now: See the earlier mentioned MariaDB bug report too. In order to get this working, you should use a new secomp profile or run unconfined with docker run --security-opt=seccomp:unconfined. That is no great advice for Docker users. You have the choice of degraded performance or lower security. Marcel ________________________________ Van: Koha-devel <koha-devel-bounces@lists.koha-community.org> namens Marcel de Rooy via Koha-devel <koha-devel@lists.koha-community.org> Verzonden: donderdag 6 maart 2025 14:54 Aan: Koha-devel <koha-devel@lists.koha-community.org> Onderwerp: Re: [Koha-devel] io_uring_queue_init failed with MariaDB 10.11.6 / Koha 23.11 Update: Getting a little bit closer. I opened a bug report with MariaDB. https://jira.mariadb.org/browse/MDEV-36234 And an older report was linked https://jira.mariadb.org/browse/MDEV-24883 It shows that io_uring and liburing were added on 10.6 (So my previous 10.5 did not have the issue.) Disabling native aio could definitely lower performance. If you have 10.6+, please check your logs ! ________________________________ Van: Koha-devel <koha-devel-bounces@lists.koha-community.org> namens Marcel de Rooy via Koha-devel <koha-devel@lists.koha-community.org> Verzonden: donderdag 6 maart 2025 11:37 Aan: Koha-devel <koha-devel@lists.koha-community.org> Onderwerp: [Koha-devel] io_uring_queue_init failed with MariaDB 10.11.6 / Koha 23.11 Hi all, I have switched from 22.11 to 23.11 while upgrading the MariaDB server from 10.5.23 to 10.11.6 (in a Docker container based on the official mariadb image from Docker hub. I am now seeing this warning in docker logs: 2025-03-06 11:14:44 0 [Warning] mysqld: io_uring_queue_init() failed with errno 1 2025-03-06 11:14:44 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF Have been searching and tested with more memory and raising memlock with --ulimit in the docker run statement, but to no avail yet. You can check if MariaDB disabled this setting in your setup with mysql: show variables like 'innodb_use_native_aio'; If it is still ON, you are probably good. Anyone else seeing this issue or have any further clues? Thanks, Marcel