#878289 dnssec-trigger: dies when unbound is restarted

Package:
dnssec-trigger
Source:
dnssec-trigger
Description:
reconfiguration tool to make DNSSEC work
Submitter:
Julien Cristau
Date:
2021-07-31 07:00:04 UTC
Severity:
important
#878289#5
Date:
2017-10-12 08:27:29 UTC
From:
To:
Hi,

it looks like when unbound stops (e.g. because it's being upgraded),
dnssec-triggerd just dies, never to come back on its own.

e.g. from my logs on buster this morning:

Oct 12 10:08:18 tomate dnssec-triggerd[966]: [966] info: dnssec-trigger
0.13 stop
Oct 12 10:08:18 tomate dnssec-trigger-script[31627]: Recovering
/etc/resolv.conf...

2017-10-12 10:08:18 upgrade unbound:amd64 1.6.5-1 1.6.6-1
2017-10-12 10:08:18 status half-configured unbound:amd64 1.6.5-1
2017-10-12 10:08:22 status unpacked unbound:amd64 1.6.5-1
2017-10-12 10:08:22 status half-installed unbound:amd64 1.6.5-1
2017-10-12 10:08:22 status half-installed unbound:amd64 1.6.5-1
2017-10-12 10:08:23 status unpacked unbound:amd64 1.6.6-1
2017-10-12 10:08:23 status unpacked unbound:amd64 1.6.6-1
[...]
2017-10-12 10:08:46 configure unbound:amd64 1.6.6-1 <none>
2017-10-12 10:08:46 status unpacked unbound:amd64 1.6.6-1
2017-10-12 10:08:46 status unpacked unbound:amd64 1.6.6-1
2017-10-12 10:08:46 status unpacked unbound:amd64 1.6.6-1
2017-10-12 10:08:46 status unpacked unbound:amd64 1.6.6-1
2017-10-12 10:08:46 status unpacked unbound:amd64 1.6.6-1
2017-10-12 10:08:46 status unpacked unbound:amd64 1.6.6-1
2017-10-12 10:08:46 status unpacked unbound:amd64 1.6.6-1
2017-10-12 10:08:46 status unpacked unbound:amd64 1.6.6-1
2017-10-12 10:08:46 status half-configured unbound:amd64 1.6.6-1
2017-10-12 10:08:47 status installed unbound:amd64 1.6.6-1

Cheers,
Julien
#878289#10
Date:
2021-07-31 06:56:32 UTC
From:
To:
私に戻ってください。
Please get back to me.