Discussion:
Unbound
Add Reply
s***@web.de
2018-10-31 20:41:10 UTC
Reply
Permalink
Hello,

when I start unbound Nameserver via shell then all work fine. But since
few weeks it start not with systemd anymore.

When I start with systemd in netstat -tulpe saw only the SSH Service.
From shell the name service also see in netstat -tulpe.

Have someone idea what I do wrong?

Nice Day & Thanks
Silvio

Log
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] notice: init module 0: subnet
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] notice: init module 1: validator
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] notice: init module 2: iterator
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] info: start of service (unbound 1.8.1).
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] info: service stopped (unbound 1.8.1).
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip rate>
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
Oct 31 21:28:59 rb2 systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Oct 31 21:28:59 rb2 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 3.
Oct 31 21:28:59 rb2 systemd[1]: Stopped Unbound DNS Resolver.
Oct 31 21:28:59 rb2 systemd[1]: Started Unbound DNS Resolver.
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] notice: init module 0: subnet
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] notice: init module 1: validator
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] notice: init module 2: iterator
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] info: start of service (unbound 1.8.1).
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] info: service stopped (unbound 1.8.1).
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip rate>
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 4.
Oct 31 21:29:00 rb2 systemd[1]: Stopped Unbound DNS Resolver.
Oct 31 21:29:00 rb2 systemd[1]: Started Unbound DNS Resolver.
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] notice: init module 0: subnet
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] notice: init module 1: validator
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] notice: init module 2: iterator
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] info: start of service (unbound 1.8.1).
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] info: service stopped (unbound 1.8.1).
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip rate>
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Oct 31 21:29:00 rb2 systemd[1]: Stopped Unbound DNS Resolver.
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Start request repeated too quickly.
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Failed with result 'start-limit-hit'.
Oct 31 21:29:00 rb2 systemd[1]: Failed to start Unbound DNS Resolver.
Joan Figueras via arch-general
2018-10-31 21:26:43 UTC
Reply
Permalink
Post by s***@web.de
Hello,
when I start unbound Nameserver via shell then all work fine. But since
few weeks it start not with systemd anymore.
When I start with systemd in netstat -tulpe saw only the SSH Service.
From shell the name service also see in netstat -tulpe.
Have someone idea what I do wrong?
Nice Day & Thanks
Silvio
Log
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] notice: init module 0: subnet
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] notice: init module 1: validator
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] notice: init module 2: iterator
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] info: start of service (unbound 1.8.1).
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] info: service stopped (unbound 1.8.1).
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip rate>
Oct 31 21:28:59 rb2 unbound[1020]: [1020:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
Oct 31 21:28:59 rb2 systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Oct 31 21:28:59 rb2 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 3.
Oct 31 21:28:59 rb2 systemd[1]: Stopped Unbound DNS Resolver.
Oct 31 21:28:59 rb2 systemd[1]: Started Unbound DNS Resolver.
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] notice: init module 0: subnet
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] notice: init module 1: validator
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] notice: init module 2: iterator
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] info: start of service (unbound 1.8.1).
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] info: service stopped (unbound 1.8.1).
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip rate>
Oct 31 21:28:59 rb2 unbound[1023]: [1023:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 4.
Oct 31 21:29:00 rb2 systemd[1]: Stopped Unbound DNS Resolver.
Oct 31 21:29:00 rb2 systemd[1]: Started Unbound DNS Resolver.
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] notice: init module 0: subnet
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] notice: init module 1: validator
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] notice: init module 2: iterator
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] info: start of service (unbound 1.8.1).
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] info: service stopped (unbound 1.8.1).
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip rate>
Oct 31 21:29:00 rb2 unbound[1025]: [1025:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Oct 31 21:29:00 rb2 systemd[1]: Stopped Unbound DNS Resolver.
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Start request repeated too quickly.
Oct 31 21:29:00 rb2 systemd[1]: unbound.service: Failed with result 'start-limit-hit'.
Oct 31 21:29:00 rb2 systemd[1]: Failed to start Unbound DNS Resolver.
Hello Silvio,

I'm using this mod for a while, and still works:

$ diff -u /usr/lib/systemd/system/unbound.service
/etc/systemd/system/unbound.service
--- /usr/lib/systemd/system/unbound.service    2018-10-13
03:59:39.000000000 +0200
+++ /etc/systemd/system/unbound.service    2018-08-23 00:04:06.204320620
+0200
@@ -5,7 +5,7 @@
 After=network.target

 [Service]
-ExecStart=/usr/bin/unbound
+ExecStart=/usr/bin/unbound -d
 ExecReload=/bin/kill -HUP $MAINPID
 Restart=alway


Best regards

Joan
Genes Lists via arch-general
2018-10-31 22:40:27 UTC
Reply
Permalink
Yeh the defaults were changed a while ago ...
Try add this to your unbound.conf

do-daemonize: no

See if that fixes things.


On 10/31/18 4:41 PM, ***@web.de wrote:
David Runge
2018-11-01 09:48:12 UTC
Reply
Permalink
Post by s***@web.de
Hello,
when I start unbound Nameserver via shell then all work fine. But
since few weeks it start not with systemd anymore.
You do want to check your configuration changes on update.
Updates are not unattended processes!

Find changed configurations:

sudo find /etc -type f -regextype egrep -regex '.*(pacnew|pacsave)'

Diff them (individually):

sudo vimdiff /path/to/original /path/to/original.pacnew

Best,
David
--
https://sleepmap.de
Ismael Bouya
2018-11-01 09:51:31 UTC
Reply
Permalink
Hey there,
Post by David Runge
sudo find /etc -type f -regextype egrep -regex '.*(pacnew|pacsave)'
sudo vimdiff /path/to/original /path/to/original.pacnew
Note that pacdiff (from pacman-contrib package) does that in a more
"friendly" manner.

Kind regards,
--
Ismael
David Runge
2018-11-01 09:59:14 UTC
Reply
Permalink
Post by Ismael Bouya
Post by David Runge
sudo find /etc -type f -regextype egrep -regex '.*(pacnew|pacsave)'
sudo vimdiff /path/to/original /path/to/original.pacnew
Note that pacdiff (from pacman-contrib package) does that in a more
"friendly" manner.
Oh no, my crappy DIY scripts become obsolete! :D

You are abolutely right. I was just to lazy to use it :)
Thanks for the hint!

Best,
David
--
https://sleepmap.de
Ralph Corderoy
2018-11-01 10:05:02 UTC
Reply
Permalink
Hi,
Post by Ismael Bouya
Post by David Runge
sudo find /etc -type f -regextype egrep -regex '.*(pacnew|pacsave)'
sudo vimdiff /path/to/original /path/to/original.pacnew
Note that pacdiff (from pacman-contrib package) does that in a more
"friendly" manner.
And there's lots of information about the topic on
https://wiki.archlinux.org/index.php/Pacman/Pacnew_and_Pacsave for the
OP.

If editing foo.conf for the first time, I `cp -a foo.conf{,.orig}'
before editing so I still have the package's original version. Then
I've three files to diff when foo.conf.pacnew arrives later.

foo.conf.orig foo.conf My changes last time.
foo.conf.orig foo.conf.pacnew What the package has changed.

This can make it easier to work out the changes required to foo.conf.
foo.conf.pacnew then becomes foo.conf.orig, ready for next time.

diff3(1) can also help.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Loading...