named (ns5) dies silently in mkeys test
The named.run
ends with:
06-Dec-2019 12:51:53.331 sockmgr 0x7fba32bca020 thread 0: watcher got message -5 for socket 512
06-Dec-2019 12:51:53.331 sockmgr 0x7fba32bca020 thread 0: watcher got message -2 for socket -1
06-Dec-2019 12:51:53.331 managed-keys-zone: Verifying DNSKEY set for zone '.' using DS 262/8: success
06-Dec-2019 12:51:53.331 managed-keys-zone: Initializing automatic trust anchor management for zone '.'; DNSKEY ID 262 is now trusted, waiving the normal 30-day waiting period.
06-Dec-2019 12:51:53.331 validating ./DNSKEY: no DNSKEY matching DS
06-Dec-2019 12:51:53.331 set_refreshkeytimer: managed-keys-zone: enter
06-Dec-2019 12:51:53.331 managed-keys-zone: next key refresh: 06-Dec-2019 12:51:53.331
06-Dec-2019 12:51:53.331 zone_settimer: managed-keys-zone: enter
and the system test log is:
[...]
I:mkeys:check key refreshes are resumed after root servers become available (31)
rndc: connect failed: 10.53.0.5#9709: connection refused
I:mkeys:failed
[...]
I:mkeys:ns5 died before a SIGTERM was sent
R:mkeys:FAIL
E:mkeys:Fri Dec 6 12:52:00 UTC 2019