FS#77370 - [dnscrypt-proxy] testing/2.1.3-1 won't start via systemd

Attached to Project: Community Packages
Opened by Christian Seemann (csmnn) - Friday, 03 February 2023, 14:50 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 23 May 2023, 04:28 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
dnscrypt-proxy testing/2.1.3-1 will drop core on start via systemd. It does not matter if it is on boot or later manually.

Startup works fine, if started in a root-shell:
[root@s0 dnscrypt-proxy]# /usr/bin/dnscrypt-proxy --config /etc/dnscrypt-proxy/dnscrypt-proxy.toml

Log-excerpt of failed systemd-start:
Feb 03 15:37:15 s0 systemd-coredump[42058]: [🡕] Process 42051 (dnscrypt-proxy) of user 62582 dumped core.

Stack trace of thread 42051:
#0 0x0000559ddcb40c4e n/a (dnscrypt-proxy + 0x11dc4e)
#1 0x0000559ddcbf905b n/a (dnscrypt-proxy + 0x1d605b)
#2 0x0000559ddcbf7e4f n/a (dnscrypt-proxy + 0x1d4e4f)
#3 0x0000559ddcc2412e n/a (dnscrypt-proxy + 0x20112e)
#4 0x0000559ddcb83468 n/a (dnscrypt-proxy + 0x160468)
#5 0x0000559ddcb833b1 n/a (dnscrypt-proxy + 0x1603b1)
#6 0x0000559ddcb833b1 n/a (dnscrypt-proxy + 0x1603b1)
#7 0x0000559ddcb75e13 n/a (dnscrypt-proxy + 0x152e13)
#8 0x0000559ddcba5d21 n/a (dnscrypt-proxy + 0x182d21)
ELF object binary architecture: AMD x86-64
Feb 03 15:37:15 s0 systemd[1]: dnscrypt-proxy.service: Main process exited, code=dumped, status=31/SYS
Feb 03 15:37:15 s0 systemd[1]: dnscrypt-proxy.service: Failed with result 'core-dump'.

Additional info:
* testing/dnscrypt-proxy 2.1.3-1

Steps to reproduce:
* Upgrade to 2.1.3-1
* Stop all running instances of dnscrypt-proxy
* Start via systemctl restart dnscrypt-proxy

On 2.1.2-1 the systemd-start works as expected.
This task depends upon

Closed by  Toolybird (Toolybird)
Tuesday, 23 May 2023, 04:28 GMT
Reason for closing:  Fixed
Additional comments about closing:  dnscrypt-proxy 2.1.3-2
Comment by Toolybird (Toolybird) - Friday, 03 February 2023, 22:41 GMT
This smells like an upstream problem which should be reported there. Could you please get a backtrace with debug symbols [1]?

[1] https://wiki.archlinux.org/title/Debugging/Getting_traces#Debuginfod
Comment by Christian Seemann (csmnn) - Friday, 03 February 2023, 23:35 GMT
Here is the backtrace with debug symbols.

I'm not so sure about it being an upstream-problem. It looks to me like the unit-files are not from there.

I never provided a backtrace before. If my attachement is not helpful, I'll happily provide more information!
   230204_dnscrypt-proxy_coredum... (5.3 KiB)
Comment by loqs (loqs) - Saturday, 04 February 2023, 00:05 GMT
Assuming syscall 6 is lstat. What if you add lstat to SystemCallFilter's allow-listing?
Comment by David Runge (dvzrv) - Saturday, 04 February 2023, 00:05 GMT
@csmnn: Thanks for the report and the backtrace.

I think this is related to the service restricting one of the syscalls that dnscrypt-proxy needs.
Please check whether 2.1.3-2 fixes this for you!
Comment by Christian Seemann (csmnn) - Saturday, 04 February 2023, 00:13 GMT
@dvzrv: Thanks! With 2.1.3-2 the service starts without any complications.
Comment by loqs (loqs) - Saturday, 04 February 2023, 00:20 GMT
setrlimit is the @resources group which was not allowed under the more restrictive call filter settings.