Hi Sami,
Could you try changing the number of vCPUs to either 6, 7, 9, or 10 and see if
it then starts OK? If that works then you can either leave it like that or we
can help you with a way to have BIND run a specific number of vCPU cores while
you put the VM back to 8 vCPUs.
Best,
Richard.
Hi Richard, and thanks for your reply.
This Windows server 2019 runs on VMware and has 8 vCPU 's. Although any version
newer than 9.16.15 just doesn't want to start. I just tried the newest release
9.16.20 also, with exactly same problem.
BR, Sami Leino / Q-Net Oy
Lähettäjä: bind-users Puole
Hi BIND users all.
I'm thinking about BIND Version migration for 9.11.X to 9.16.X.
Also, I'm about to check the different default config value and config
parameters for the purpose of that now.
I would like to ask you all.
Are there any other points of observe carefully when migrating versions?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
https://www.five-ten-sg.com/mapper/bind contains links to the source
rpm, and build instructions. This .src.rpm contains a .tar.gz file with
the ARM documentation, so the rpm rebuild process does not need sphinx-
build and associated dependencies.
-
Hi Sami,
There's presently an issue where the ISC BIND service (v9.16.19) won't start on
a Windows server with either 8 or 12 vCPUs. How many CPUs (or vCPUs) are in
this Windows Server?
I didn't find that older versions were exhibiting the same issue so it might
not be that, but it's at least
Hello,
Our NS3.qnet.fi which is Windows Server 2019, does not start ISC Bind process
with any newer version than 9.16.15
I have tried to update to 9.16.17 , 9.16.18 and the latest 9.16.19, all those
versions refuse to start. Nothing reasonable in event viewer. Always same error
when trying to
6 matches
Mail list logo
