Hello,
Today I noticed a machine running Unbound 1.9.2 had gotten itself into
an odd state.
Running "unbound-control status" would just hang, and even after
removing all client queries from the machine one of the CPUs in the
server was still fully busy in 100% user time in top:
Recently I got the same 100% CPU behavior as yours with unbound 1.10 and 1.9.6. Did you resolve the problem?
Patrik Lundin via Unbound-users <unbound-users@nlnetlabs.nl> 于2019年9月23日周一 下午5:12写道：
Unfortunately no, I am not sure how to reproduce it and have not seen
the problem since. Have you been able to recreate the problem on demand?