Package: pdns-server
Version: 4.4.1-1
Severity: normal

Hello,

on installation of pdns-server the pdns.service is automatically
started. However in my case port 53 is already bound and so it fails to
start. (That might also happen if port 53 isn't blocked because the
default config isn't suitable to successfully run pdns? I didn't check.)

Because of

        Restart=on-failure
        RestartSec=1
        StartLimitInterval=0

in pdns.service the systemd tries to start pdns once per second and for
each try logs something like:

        Nov 07 21:41:55 algol systemd[1]: Starting PowerDNS Authoritative 
Server...
        Nov 07 21:41:55 algol pdns_server[2329737]: Loading 
'/usr/lib/x86_64-linux-gnu/pdns/libbindbackend.so'
        Nov 07 21:41:55 algol pdns_server[2329737]: This is a standalone pdns
        Nov 07 21:41:55 algol pdns_server[2329737]: Listening on controlsocket 
in '/run/pdns/pdns.controlsocket'
        Nov 07 21:41:55 algol pdns_server[2329737]: UDP server bound to 
0.0.0.0:53
        Nov 07 21:41:55 algol pdns_server[2329737]: UDP server bound to [::]:53
        Nov 07 21:41:55 algol pdns_server[2329737]: Unable to bind to TCP 
socket 0.0.0.0:53: Address already in use
        Nov 07 21:41:55 algol pdns_server[2329737]: Fatal error: Unable to bind 
to TCP socket
        Nov 07 21:41:55 algol systemd[1]: pdns.service: Main process exited, 
code=exited, status=1/FAILURE
        Nov 07 21:41:55 algol systemd[1]: pdns.service: Failed with result 
'exit-code'.
        Nov 07 21:41:55 algol systemd[1]: Failed to start PowerDNS 
Authoritative Server.
        Nov 07 21:41:56 algol systemd[1]: pdns.service: Scheduled restart job, 
restart counter is at 23.
        Nov 07 21:41:56 algol systemd[1]: Stopped PowerDNS Authoritative Server.

to the journal. If you don't notice this immediately and stop the
service this effectively spams your journal in a very short time.

IMHO the above mentioned settings are not suitable as a default for a
distribution's package even if the default configuration worked. It
should be an administrator's choice to configure such a behaviour.

Best regards
Uwe

-- System Information:
Debian Release: 11.8
  APT prefers oldstable-security
  APT policy: (500, 'oldstable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-19-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pdns-server depends on:
ii  adduser                         3.118+deb11u1
ii  libboost-program-options1.74.0  1.74.0-9
ii  libc6                           2.31-13+deb11u7
ii  libcurl4                        7.74.0-1.3+deb11u10
ii  libgcc-s1                       10.2.1-6
ii  libluajit-5.1-2                 2.1.0~beta3+dfsg-5.3
ii  libp11-kit0                     0.23.22-1
ii  libsodium23                     1.0.18-1
ii  libsqlite3-0                    3.34.1-3
ii  libssl1.1                       1.1.1w-0+deb11u1
ii  libstdc++6                      10.2.1-6
ii  libsystemd0                     247.3-7+deb11u4

Versions of packages pdns-server recommends:
ii  pdns-backend-bind  4.4.1-1

Versions of packages pdns-server suggests:
ii  pdns-backend-bind [pdns-backend]   4.4.1-1
ii  pdns-backend-pgsql [pdns-backend]  4.4.1-1

-- Configuration Files:
/etc/powerdns/pdns.conf [Errno 13] Permission denied: '/etc/powerdns/pdns.conf'

-- no debconf information

Reply via email to