<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:"Segoe UI Symbol";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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;}
span.Shkpostityyli20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 2.0cm 70.85pt 2.0cm;}
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="FI" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">So I also verify that this problem with vCPU (8) is fixed in the 9.16.21 release.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">THANK YOU! ( </span><span lang="EN-US" style="font-family:"Segoe UI Symbol",sans-serif">❛</span><span lang="EN-US"> ͜</span><span lang="EN-US">ʖ </span><span lang="EN-US" style="font-family:"Segoe UI Symbol",sans-serif">❛</span><span lang="EN-US">
)</span><span lang="EN-US" style="font-family:"Segoe UI Emoji",sans-serif">✌</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:FI">T. Sami Leino / Q-Net Oy<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="mso-fareast-language:FI">Lähettäjä:</span></b><span style="mso-fareast-language:FI"> bind-users <bind-users-bounces@lists.isc.org>
<b>Puolesta </b>Richard T.A. Neal<br>
<b>Lähetetty:</b> torstai 9. syyskuuta 2021 2.16<br>
<b>Vastaanottaja:</b> bind-users@isc.org<br>
<b>Aihe:</b> RE: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Hi Sami,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I’m sorry but I’ve tried to do that again this evening but I can’t get it to work.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">named.exe can take command line arguments to limit the number of vCPUs it will use, but I can’t get this to work when running named.exe as a service.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">It *<b>should</b>* be the case that you can edit the following Registry Key:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\named<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Then set “Image Path” to be:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">C:\BIND\bin\named.exe -n 7<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">That would tell named to run using only 7 vCPUs. But that doesn’t work for me, it still refuses to start the service.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I’m sorry that I’ve been unable to find a way to assist further. This is being tracked in the ISC BIND Gitlab at the following link:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><a href="https://gitlab.isc.org/isc-projects/bind9/-/issues/2837">https://gitlab.isc.org/isc-projects/bind9/-/issues/2837</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I may be mis-reading but I *<b>think</b>* they’ve identified a fix which is waiting to be merged into the codebase, possibly in time for the next release.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">In the mean time as a manual workaround you can start named from the command line as follows (but I can’t find a way to automate this so it’s not reliable, and you’d need to do it every time the server (re)boots. Aram
Sargsyan came up with this workaround in the ticket referenced above, and I’ve confirmed that it works on an 8-core test VM that I created:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">C:\> sc start named -n 7<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-GB">Richard.<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:EN-GB">From:</span></b><span lang="EN-US" style="mso-fareast-language:EN-GB"> Sami Leino <<a href="mailto:sami.leino@qnet.fi">sami.leino@qnet.fi</a>>
<br>
<b>Sent:</b> 08 September 2021 8:13 am<br>
<b>To:</b> Richard T.A. Neal <<a href="mailto:richard@richardneal.com">richard@richardneal.com</a>>;
<a href="mailto:bind-users@isc.org">bind-users@isc.org</a><br>
<b>Subject:</b> VS: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal">Hi Richard,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">I will return to this problem with 8 vCPU count. You wrote earlier that there could be a way to have BIND run a specific number of vCPU cores?</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Because with the current setup we cannot change the server’s vCPU count.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:FI">BR, Sami Leino / Q-Net Oy</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
</div>
</body>
</html>