<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Unbound V1.9.1<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On Windows the following line is not useable:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> # use SO_REUSEPORT to distribute queries over threads.<o:p></o:p></p><p class=MsoNormal> # so-reuseport: no<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>When the number of events is greater than 64 Unbound generates these errors (This will happen all the time):<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>28/04/2019 14:44:17 C:\Program Files\Unbound\unbound.exe[1352:1] error: event_add failed. in cpsl.<o:p></o:p></p><p class=MsoNormal>28/04/2019 14:44:17 C:\Program Files\Unbound\unbound.exe[1352:1] error: event_add failed. in cpsl.<o:p></o:p></p><p class=MsoNormal>28/04/2019 14:44:17 C:\Program Files\Unbound\unbound.exe[1352:1] error: event_add failed. in cpsl.<o:p></o:p></p><p class=MsoNormal>28/04/2019 15:18:38 C:\Program Files\Unbound\unbound.exe[1352:1] error: event_add failed. in cpsl.<o:p></o:p></p><p class=MsoNormal>28/04/2019 15:18:38 C:\Program Files\Unbound\unbound.exe[1352:1] error: event_add failed. in cpsl.<o:p></o:p></p><p class=MsoNormal>28/04/2019 15:18:38 C:\Program Files\Unbound\unbound.exe[1352:1] error: event_add failed. in cpsl.<o:p></o:p></p><p class=MsoNormal>28/04/2019 15:18:38 C:\Program Files\Unbound\unbound.exe[1352:1] error: event_add failed. in cpsl.<o:p></o:p></p><p class=MsoNormal>28/04/2019 15:18:38 C:\Program Files\Unbound\unbound.exe[1352:1] error: event_add failed. in cpsl.<o:p></o:p></p><p class=MsoNormal>28/04/2019 15:18:38 C:\Program Files\Unbound\unbound.exe[1352:1] error: event_add failed. in cpsl.<o:p></o:p></p><p class=MsoNormal>28/04/2019 15:18:38 C:\Program Files\Unbound\unbound.exe[1352:1] error: event_add failed. in cpsl.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Can the log level at which these are generated be raised so that they do not clog up the log file when logging is set to the minimum value?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>When Unbound starts it uses root hints to gather all the root servers as part of its initialisation process. Most times I see these errors in the log file for all the root servers in the root.hints file.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>28/04/2019 14:42:10 C:\Program Files\Unbound\unbound.exe[1352:0] notice: sendto failed: Network is unreachable.<o:p></o:p></p><p class=MsoNormal>28/04/2019 14:42:10 C:\Program Files\Unbound\unbound.exe[1352:0] notice: remote address is 192.33.4.12 port 53<o:p></o:p></p><p class=MsoNormal>28/04/2019 14:42:10 C:\Program Files\Unbound\unbound.exe[1352:0] notice: sendto failed: Network is unreachable.<o:p></o:p></p><p class=MsoNormal>28/04/2019 14:42:10 C:\Program Files\Unbound\unbound.exe[1352:0] notice: remote address is 192.112.36.4 port 53<o:p></o:p></p><p class=MsoNormal>28/04/2019 14:42:10 C:\Program Files\Unbound\unbound.exe[1352:0] notice: sendto failed: Network is unreachable.<o:p></o:p></p><p class=MsoNormal>28/04/2019 14:42:10 C:\Program Files\Unbound\unbound.exe[1352:0] notice: remote address is 193.0.14.129 port 53<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>All the above sort of errors occur within 1 second or so of Unbound starting.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Would it be an idea to change these errors to a higher logging level and at the minimal logging have a couple of lines like:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='text-indent:36.0pt'>Initialising root hints<o:p></o:p></p><p class=MsoNormal style='text-indent:36.0pt'>Root hints initialisation complete<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This would help to reduce the number of errors at low level logging. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Just thoughts…<o:p></o:p></p></div></body></html>