Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1069124 > unrolled thread

Bug#993359: Update systemd unit to raise memlock limit for io_uring support

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#993359: Update systemd unit to raise memlock limit for io_uring support MichaIng <micha@dietpi.com> - 2021-08-31 13:20 +0200
    Bug#993359: Update systemd unit to raise memlock limit for io_uring support Geoff <efrim@azylum.org> - 2021-08-31 14:40 +0200

#1069124 — Bug#993359: Update systemd unit to raise memlock limit for io_uring support

Package: mpd
Version: 0.22.6-1

Hey guys,

with v0.22, MPD introduced support for io_uring kernel interface, which 
has been enabled for the Debian package with v0.22.3-1 as well.

The problem is that for making use of it, the default memlock limit on 
Debian of 64 KiB is too small, and the daemon hence throws an exception, 
using a fallback:
-------
Failed to initialize io_uring: io_uring_queue_init() failed: Cannot 
allocate memory
-------

The memlock limit can be raised via systemd unit, which has been done 
upstream: 
https://github.com/MusicPlayerDaemon/MPD/blob/v0.22.x/systemd/system/mpd.service.in#L19-L20
But this change obviously wasn't applied to the Debian package.

Applying this directive solves the exception, so I suggest to apply it 
to the Debian package as well.

Further references:
- https://github.com/MusicPlayerDaemon/MPD/issues/972
- https://github.com/MichaIng/DietPi/issues/4690

Best regards,

Micha

[toc] | [next] | [standalone]

#1069132

Hi Micha !

31/08/2021, MichaIng wrote:
> The memlock limit can be raised via systemd unit, which has been done
> upstream: https://github.com/MusicPlayerDaemon/MPD/blob/v0.22.x/systemd/system/mpd.service.in#L19-L20
> But this change obviously wasn't applied to the Debian package.

Systemd unit file used in the package comes from upstream with a minor patch [0].
Then I'm pretty sure LimitMEMLOCK config is present in bullseye MPD 0.22.6-1.

I just made a plain install of bullseye (amd64 VM), here is what I got:

     $ systemctl cat mpd.service | grep LimitMEM
     LimitMEMLOCK=64M

     $ systemctl show mpd.service | grep LimitMEM
     LimitMEMLOCK=67108864
     LimitMEMLOCKSoft=67108864

I did not reproduce the “Failed to initialize io_uring” error either.

I confused here, please have a look at /usr/lib/systemd/system/mpd.service,
LimitMEMLOCK should be there on a vanilla install.

Do you have any fragments in /etc/systemd/system/mpd.service.d that could interfere?

Cheers
k

[0] https://sources.debian.org/src/mpd/0.22.6-1/systemd/system/mpd.service.in/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web