Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#58714 - [dnscrypt-proxy] Socket and service create conflicts when bind to the same port

Attached to Project: Community Packages
Opened by Tommy Schmitt (spinka) - Thursday, 24 May 2018, 15:18 GMT
Last edited by David Runge (dvzrv) - Friday, 25 May 2018, 10:50 GMT
Task Type Bug Report
Category Packages
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 1
Private No

Details

Description:

Unfortunately after https://bugs.archlinux.org/task/58661 there are conflicts when both socket and service are enabled:
https://github.com/jedisct1/dnscrypt-proxy/issues/463
https://bbs.archlinux.org/viewtopic.php?pid=1787379

It seems that supporting both socket activation and standalone service at the same time isn't feasible. Maybe listening to different address like 127.0.2.1 in one unit would help but it will create redundancy at the same time (one of them won't be used). I think you should either revert back to old upstream units (socket activation) or drop socket unit completely.

The quick workaround is to disable socket.
This task depends upon

Closed by  David Runge (dvzrv)
Friday, 25 May 2018, 10:50 GMT
Reason for closing:  Not a bug
Additional comments about closing:  This is more of a documentation issue.
Please refer to the wiki!
Comment by David Runge (dvzrv) - Friday, 25 May 2018, 10:50 GMT
@spinka: You either use socket activation, or you use the service file (the default now). I updated this in the wiki [1]. There are still a lot of recommendations and setup things from v1.x in there... if I find more time today, I'll revise them as well.

When using socket activation, you will have to use an empty set for listen_addresses (`listen_addresses = [ ]` as documented in the configuration file), when using the service file directly, you will have to take care of setting up the listening addresses and ports in the configuration file (or use the defaults).

[1] https://wiki.archlinux.org/index.php/DNSCrypt#Configuration

Loading...