On 31/10/18 21:41, siefke_listen@web.de wrote:
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