FS#73466 - [murmur] service crashes when client connect

Attached to Project: Community Packages
Opened by Daniel Jenssen (Daerandin) - Sunday, 23 January 2022, 11:12 GMT
Last edited by David Runge (dvzrv) - Monday, 24 January 2022, 15:44 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
David Runge (dvzrv)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

When murmur is run as a systemd service with the provided service file, it will crash when a client connects. Running murmurd directly works without issues.

I tracked down the issue to the SystemCallFilter lines in /usr/lib/systemd/system/murmur.service

In particular if I comment out the line:

SystemCallFilter=~@resources @privileged

Then everything works. Another solution I discovered was to switch the order of the two SystemCallFilter lines so that the aforementioned line appears first. In my working file, the two lines appear in this order:

SystemCallFilter=~@resources @privileged
SystemCallFilter=@system-service

I can only assume that this works because @system-service enables some required system calls that are prohibited by "~@resources @privileged"
This task depends upon

Closed by  David Runge (dvzrv)
Monday, 24 January 2022, 15:44 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with 1.4.230-2
Comment by Magnus Groß (vimpostor) - Monday, 24 January 2022, 13:29 GMT
I can confirm the same problem and can confirm the proposed solution to be working. Attached is a stack trace from the crash.
   stacktrace.txt (9.6 KiB)
Comment by Daniel Jenssen (Daerandin) - Monday, 24 January 2022, 14:54 GMT
I forgot to specify the package version in the bugreport, so for clarity this is about murmur version 1.4.230-1

The package was still in testing when I reported this issue, but I see it has been moved from community-testing to the community repo.
Comment by David Runge (dvzrv) - Monday, 24 January 2022, 15:29 GMT
@Daerandin: Thanks for the report and the assessment of the issue.

I will fix this in a pkgrel bump.

Loading...