Unbound 1.13.0rc4 pre-release Sleep/Wake issue.

[RayG]

Hi Jaap

Thanks for your reply.

Yes that is one way around the issue. Not ideal but certainly possible. I
have set the logging to max but I suspect that this may interfere with
whatever is going on. I was hoping to see a failure when I woke the system
this afternoon. Alas it worked this time. I will continue to keep the
logging at max and see if I can catch it at some point. The other thing I
forgot to mention last night was that as well as using DNSSEC I am using
forwarding and DoT. That with the TLS aspects will also expect the clock to
be correct. The clock is the only thing I can think of that may be causing
the issue. There is just not enough logging at level 1 logging to see errors
like that and at the max level it is possible that programmatic timings
alter and the issue slips through the net.

We will see what if anything I can capture over the next few days.

RayG

-----Original Message-----
From: Jaap Akkerhuis <jaap at NLnetLabs.nl> 
Sent: 04 December 2020 23:33
To: RayG <rgsub1 at btinternet.com>; RayG via Unbound-users
<unbound-users at lists.nlnetlabs.nl>
Subject: Re: Unbound 1.13.0rc4 pre-release Sleep/Wake issue.

 RayG via Unbound-users writes:

 > This is a multipart message in MIME format.
 >
 > I think I have some thoughts on this issue. I had it happen again just  >
before writing this email.
 >
 > It seems to happen after the system has been asleep for a long time,
hours.
 > When it wakes up it cannot get its act together and everything fails.
 > I tried something tonight that resolved the problem:
 > Unbound_control.exe flush_infra all
 > This does something that causes unbound to sort itself out. And
everything  > works again.

As work around you can try to run thus unbound_control after wake up using
the method as suggested in
<https://sumtips.com/how-to/run-program-windows-wakes-up-sleep-hibernate/>

	jaap