Arch Linux

qupfer

Member

Registered: 2014-04-02

Posts: 14

Something changed in unbound startup behaviour?

Hi, I run unbound on my arch system and yesterday, after a reboot, its not starting anymore during startup
I saw in the /etc/unbound directory an new (minimalistic) unbound.conf.pacnew so I think there was an update.

Until yesterday, unbound startes with systemd, which is just running unboundwithout parameter (ExecStart=/usr/bin/unbound). The journal ist not very useful.

Aug 08 08:14:07 plex.07q.de systemd[1]: Started Unbound DNS Resolver.
Aug 08 08:14:09 plex.07q.de unbound[351]: [351:0] info: start of service (unbound 1.7.3).
Aug 08 08:14:10 plex.07q.de unbound[351]: [351:0] info: service stopped (unbound 1.7.3).
Aug 08 08:14:10 plex.07q.de systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
[...]
Aug 08 08:14:12 plex.07q.de systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Aug 08 08:14:12 plex.07q.de systemd[1]: Stopped Unbound DNS Resolver.
Aug 08 08:14:12 plex.07q.de systemd[1]: unbound.service: Start request repeated too quickly.
Aug 08 08:14:12 plex.07q.de systemd[1]: unbound.service: Failed with result 'start-limit-hit'.
Aug 08 08:14:12 plex.07q.de systemd[1]: Failed to start Unbound DNS Resolver.

So, I tried to start it thourh command line, and it worked again. But I recognized, that unbound starts in daemon mode. I also remembered, that systemd does not like daemons.
So I add "do-daemonize: no" to the configuration file and after that, all works fine agian.

So, I'm curois why it worked before. Because it seems that daemon mode was "default" befor the update.
But maybe, its related to this change? But to be honest. I have no idea :-)
7 August 2018: Wouter
    - Fix #4142: unbound.service.in: improvements and fixes.
      Add unit dependency ordering (based on systemd-resolved).
      Add 'CAP_SYS_RESOURCE' to 'CapabilityBoundingSet' (fixes warnings
      about missing privileges during startup). Add 'AF_INET6' to
      'RestrictAddressFamilies' (without it IPV6 can't work). From
      Guido Shanahan.

Thanks for your explanations ;-)

Last edited by qupfer (2018-08-09 09:03:20)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,559

Re: Something changed in unbound startup behaviour?

The package log makes it very clear why it was changed and what is different from before. If you had merged your .pacnew files like you were supposed to, you wouldn't have had a problem.

Last edited by Scimmia (2018-08-09 09:04:32)

qupfer

Member

Registered: 2014-04-02

Posts: 14

Re: Something changed in unbound startup behaviour?

Mh, thanks for your reply. But not sure, which log do you mean.
I found this:
https://git.archlinux.org/svntogit/comm … a914556f65

But in this, they are also remove the "-d" flag from the servie file. I take a look in a backup from June, and on my system, there is not "-d" flag in the service file.

Everette88

Member

Registered: 2018-02-17

Posts: 41

Re: Something changed in unbound startup behaviour?

They removed pidfile from systemd unit

-PIDFile=/run/unbound.pid

nl6720

The Evil Wiki Admin

Registered: 2016-07-02

Posts: 596

Re: Something changed in unbound startup behaviour?

Look at the change to the conf file: https://git.archlinux.org/svntogit/comm … a914556f65 .

russ0r

Member

Registered: 2008-03-29

Posts: 26

Re: Something changed in unbound startup behaviour?

Just had the same problem because I'm a terrible human being for not checking my .pacnew files.

The solution is to set:

do-daemonize: no

in /etc/unbound/unbound.conf