Your message dated Sat, 21 Jan 2017 19:44:40 -0500
with message-id <20170122004440.cc5jfdujwpi2u7yo@gambit>
and subject line Re: Bug#849631: dnscrypt-proxy
has caused the Debian Bug report #849631,
regarding dnscrypt-proxy 1.8.1-4 fails to start
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
849631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnscrypt-proxy
Version: 1.7.0+dfsg-1
Severity: serious
Tags: upstream
Justification: serious

Dear Maintainer,

   * What led up to the situation?
   After upgrade dnscrypt-proxy, it wan't start anymore.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     Working as before.
   * What was the outcome of this action?
   dnscrypt-proxy.service and dnscrypt-proxy.socket stop working.
   I get these output in journalctl:
   Dec 28 22:13:03 debian systemd[1]: dnscrypt-proxy.service: Service
   hold-off time over, scheduling restart.
   Dec 28 22:13:03 debian systemd[1]: dnscrypt-proxy.service: Start
   request repeated too quickly.
   Dec 28 22:13:03 debian systemd[1]: dnscrypt-proxy.socket: Unit
   entered failed state.
   Dec 28 22:13:03 debian systemd[1]: dnscrypt-proxy.service: Unit
   entered failed state.
   Dec 28 22:13:03 debian systemd[1]: dnscrypt-proxy.service: Failed
   with result 'start-limit-hit'.
   
   And if I feed dnscrypt-proxy command with the configuration file, I
   get in terminal:
   Dec 28 22:13:01 debian dnscrypt-proxy[1694]: Wed Dec 28 22:13:01 2016
   [INFO] + DNS Security Extensions are supported
   Dec 28 22:13:01 debian dnscrypt-proxy[1694]: Wed Dec 28 22:13:01 2016
   [INFO] + Provider supposedly doesn't keep logs
   Dec 28 22:13:01 debian systemd[1]: dnscrypt-proxy.service: Service
   hold-off time over, scheduling restart.

   * What outcome did you expect instead?
   Running dnscrypt-proxy.service and dnscrypt-proxy.socket.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (150, 'testing'), (100, 'stable'), (5, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dnscrypt-proxy depends on:
ii  adduser              3.115
ii  init-system-helpers  1.46
ii  libc6                2.24-8
ii  libltdl7             2.4.6-2
ii  libsodium18          1.0.11-1
ii  libsystemd0          232-8

dnscrypt-proxy recommends no packages.

Versions of packages dnscrypt-proxy suggests:
ii  resolvconf  1.79

-- Configuration Files:
/etc/default/dnscrypt-proxy changed:
DNSCRYPT_PROXY_LOCAL_ADDRESS=127.0.2.1:53
DNSCRYPT_PROXY_RESOLVER_NAME=dnscrypt.org-fr
DNSCRYPT_PROXY_OPTIONS=""

/etc/dnscrypt-proxy/dnscrypt-proxy.conf changed:
ResolverName=dnscrypt.org-fr
ResolversList /usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv
Daemonize yes
PidFile /var/run/dnscrypt-proxy.pid
User _dnscrypt-proxy
LocalAddress 127.0.2.1:53
EphemeralKeys yes
MaxActiveRequests 250
LogFile /var/log/dnscrypt-proxy.log
LogLevel 7
BlockIPv6 yes


-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.8.1-4

Thanks, closing this then for now.

* peter.ne...@yahoo.co.uk (peter.ne...@yahoo.co.uk) wrote:
> Hallo Eric
> after a complete purge of dnscrypt-proxy files and a reinstall of version 
> 1.8.1-4 it appears to be working correctly.
> I have only needed to alter the :
> etc/dnscrypt-proxy/dnscrypt-proxy.conf
> 
> to change to my preferred  DNSCRYPT_PROXY_RESOLVER_NAME=
> thanks for your help
> Peter

-- 
Eric Dorland <e...@kuroneko.ca>
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to