unbound:remote control failed ssl crypto

[4o4rh]

Got up this morning and discovered, unbound was down.
Restarted, and it crashed after first boot and then rebooted again.
Now the system is up, I see in the logs

Concerning to see a message like "remote control" in the log and a port from the local host.

Jun 30 06:41:59 	filterdns 	15055 	failed to resolve host keys.gnupg.net will retry later again. 
Jun 30 06:41:29 	unbound 	17234 	[17234:0] info: service stopped (unbound 1.12.0).
Jun 30 06:41:29 	unbound 	17234 	[17234:0] error: remote control failed ssl crypto error:00000000:lib(0):func(0):reason(0)
Jun 30 06:41:29 	unbound 	17234 	[17234:0] notice: failed connection from 127.0.0.1 port 41235
Jun 30 06:41:29 	unbound 	17234 	[17234:0] info: start of service (unbound 1.12.0).
Jun 30 06:41:29 	unbound 	17234 	[17234:0] notice: init module 0: iterator

[jimp]

"remote control" just means that something called unbound-control which happens from the base system for various reasons. Sometimes for making config adjustments, sometimes for getting status, etc.

I haven't seen it fail in quite that way, though.

Did you happen to get a crash dump or other logs from when you say it crashed and rebooted?

We should have a public RC snapshot soon (today, possibly) which will be a much better testing data point. All the public RC images right now have known issues in pf which can lead to instability and slowness.

[jimp]

There is a new snapshot up now (2.5.2.r.20210629.1350) which should be much better to test on. Update and give it a try.