Arch Linux

@jrnewell: Thanks for the report.

However, as you have not provided any logs or any details I can neither understand what's going on nor reproduce it.
Additionally, the service works here and I have just upgraded to 2.0.43.

Please read the wiki article on bug reporting guidelines [1] and provide a more useful bug report next time.

[1] https://wiki.archlinux.org/index.php/Bug_reporting_guidelines

● dnscrypt-proxy.service - DNSCrypt-proxy client
Loaded: loaded (/usr/lib/systemd/system/dnscrypt-proxy.service; enabled; vendor preset: disabled)
Active: failed (Result: signal) since Tue 2020-06-23 21:35:52 MSK; 8min ago
Docs: https://github.com/jedisct1/dnscrypt-proxy/wiki
Process: 377 ExecStart=/usr/bin/dnscrypt-proxy --config /etc/dnscrypt-proxy/dnscrypt-proxy.toml (code=killed, signal=SYS)
Main PID: 377 (code=killed, signal=SYS)

июн 23 21:35:31 computer dnscrypt-proxy[377]: [2020-06-23 21:35:31] [NOTICE] - 186ms qualityology.com
июн 23 21:35:31 computer dnscrypt-proxy[377]: [2020-06-23 21:35:31] [NOTICE] - 239ms freetsa.org
июн 23 21:35:31 computer dnscrypt-proxy[377]: [2020-06-23 21:35:31] [NOTICE] - 300ms publicarray-au
июн 23 21:35:31 computer dnscrypt-proxy[377]: [2020-06-23 21:35:31] [NOTICE] - 305ms jp.tiar.app
июн 23 21:35:31 computer dnscrypt-proxy[377]: [2020-06-23 21:35:31] [NOTICE] - 335ms publicarray-au2
июн 23 21:35:31 computer dnscrypt-proxy[377]: [2020-06-23 21:35:31] [NOTICE] - 672ms scaleway-fr
июн 23 21:35:31 computer dnscrypt-proxy[377]: [2020-06-23 21:35:31] [NOTICE] Server with the lowest initial latency: sth-dnscrypt-se (rtt: 22ms)
июн 23 21:35:31 computer dnscrypt-proxy[377]: [2020-06-23 21:35:31] [NOTICE] dnscrypt-proxy is ready - live servers: 35
июн 23 21:35:52 computer systemd[1]: dnscrypt-proxy.service: Main process exited, code=killed, status=31/SYS
июн 23 21:35:52 computer systemd[1]: dnscrypt-proxy.service: Failed with result 'signal'.

@ljgdasfhk: Have you tried raising the log-level for dnscrypt-proxy?

I have not experienced any such behavior, so I can't really reproduce it.
The service has been running very reliably on several machines for me so far (unmodified).
In what context are you using the service? How are you starting it? On what kind of machine are you running it?
With what other services are you running it in conjunction (e.g. caching DNS resolver)?

Do you see any output in `coredumpctl list` in regards to this crash?
What exact steps have you taken to resolve the issue? Did those help?

Did you contact upstream about your issues?

Also, which version of the package are you using?
Output of `dnscrypt-proxy -version`.

Most of these questions are already mentioned in the bug reporting guidelines [1].
I am a bit tired of repeating myself here...

[1] https://wiki.archlinux.org/index.php/Bug_reporting_guidelines

Hi David, I didn't reopen the ticket. But I want to reply to my original ticket. Unfortunately, for me at least, the only error message from the logs I got was the error message in the description of the ticket. It is not very verbose. That being said, my problem went away with this update that had a change to the ownership in the systemd service file: https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/dnscrypt-proxy&id=91d213972e2e355d021a10406a42e079e1bd4a3a. I thought you made that update to the service file in response to my ticket but I guess it was just a coincidence so I didn't really follow up. So far it has been rock solid so for me. I apologize i didn't give more info at the outset.

@jrnewell: I see! I have added that SystemCallFilter for the log file issues discussed in  FS#66147 .

Did you use an external log file instead of syslog (e.g. the journal), too? Maybe in your case these problems were related.

David, yes that is correct. I was using a log file and syslog disabled. I recently migrated from Ubuntu with dnscrypt manually installed, so I had the github config file that didn't have syslog turned on.