Your message dated Tue, 10 Apr 2018 10:59:19 +0200
with message-id <20180410085919.3l4n4wrt3ym2v...@percival.namespace.at>
and subject line Re: #892610: Address already in use /etc/init.d/pdns-recursor 
restart
has caused the Debian Bug report #892610,
regarding Address already in use /etc/init.d/pdns-recursor restart
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.)


-- 
892610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pdns-recursor
Version: 4.0.4-1+deb9u3+b1

When restarting pdns-recursor with the initscript, "/etc/init.d/pdns-recursor 
restart", we sometimes get an Address already in use Exception:
Mar 11 06:55:09 recurse01 pdns_recursor[30857]: Exception: Resolver binding to 
server socket on port 53 for 0.0.0.0: Address already in use 

This is problematic whenever this is done automatically and it never comes up 
again. Effectivly resulting in no pdns-recursor running.
This does not happen always, for example when trying to reproduce it right now, 
it restarts correctly. 
It seems to happen while being in heavy use or running for a while longer.

Whenever we run "/etc/init.d/pdns-recursor stop", wait a few seconds and 
"/etc/init.d/pdns-recursor start" again it always works. 
So it seems like a timing issue, being sometimes too fast starting 
pdns-recursor again before the socket is completely closed. 

$ cat /etc/debian_version
9.4

$ uname -a
Linux recurse01 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u2 (2018-02-21) x86_64 
GNU/Linux

$ dpkg -l |grep sysvinit
ii  sysvinit-core                2.88dsf-59.9                   amd64        
System-V-like init utilities
ii  sysvinit-utils               2.88dsf-59.9                   amd64        
System-V-like utilities

$ dpkg -l |grep systemd
ii  libpam-systemd:amd64         232-25+deb9u2                  amd64        
system and service manager - PAM module
ii  libsystemd0:amd64            232-25+deb9u2                  amd64        
systemd utility library
ii  python-systemd               233-1                          amd64        
Python 2 bindings for systemd
ii  systemd                      232-25+deb9u2                  amd64        
system and service manager
ii  systemd-shim                 10-3                           amd64        
shim for systemd

--- End Message ---
--- Begin Message ---
Apparently solved by switching init to systemd.

--- End Message ---

Reply via email to