VS: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019

[Sami Leino]

So I also verify that this problem with vCPU (8) is fixed in the 9.16.21 release.

THANK YOU! ( ❛ ͜ʖ ❛ )✌

T. Sami Leino / Q-Net Oy


Lähettäjä: bind-users <bind-users-bounces at lists.isc.org> Puolesta Richard T.A. Neal
Lähetetty: torstai 9. syyskuuta 2021 2.16
Vastaanottaja: bind-users at isc.org
Aihe: RE: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019

Hi Sami,

I’m sorry but I’ve tried to do that again this evening but I can’t get it to work.

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.

It *should* be the case that you can edit the following Registry Key:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\named

Then set “Image Path” to be:
C:\BIND\bin\named.exe -n 7

That would tell named to run using only 7 vCPUs. But that doesn’t work for me, it still refuses to start the service.

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:
https://gitlab.isc.org/isc-projects/bind9/-/issues/2837

I may be mis-reading but I *think* they’ve identified a fix which is waiting to be merged into the codebase, possibly in time for the next release.

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:

C:\> sc start named -n 7

Best,

Richard.

From: Sami Leino <sami.leino at qnet.fi<mailto:sami.leino at qnet.fi>>
Sent: 08 September 2021 8:13 am
To: Richard T.A. Neal <richard at richardneal.com<mailto:richard at richardneal.com>>; bind-users at isc.org<mailto:bind-users at isc.org>
Subject: VS: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019

Hi Richard,

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?

Because with the current setup we cannot change the server’s vCPU count.

BR, Sami Leino / Q-Net Oy




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20210917/d54cfe32/attachment.htm>