Re: BIND 'max-cache-size' Value on FreeBSD-13.0

2021-09-08 Thread Mark Tinka 

2.5 days in, and 9.11 is still running good, with no crashing.

Safe to say that this memory leak is definitely an issue with 9.16.

Mark.

On 9/6/21 19:30, Mark Tinka wrote:

So I've decided to downgrade our busiest resolvers to bind911-9.11.35.

Mark.


___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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

2021-09-08 Thread Richard T.A. Neal 
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 
Sent: 08 September 2021 8:13 am
To: Richard T.A. Neal ; bind-us...@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




___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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

2021-09-08 Thread G.W. Haywood via bind-users 

Hi there,

On Wed, 8 Sep 2021, Sami Leino wrote:


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?


Have you tried searching something like "windows processor affinity"?

--

73,
Ged.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

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

2021-09-08 Thread Sami Leino 
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


Lähettäjä: bind-users  Puolesta Sami Leino
Lähetetty: torstai 19. elokuuta 2021 12.58
Vastaanottaja: Richard T.A. Neal ; bind-us...@isc.org
Aihe: VS: BIND 9.16.19 or any version newer than 9.16.15 does not start on 
Windows Server 2019

Hi Richard,

I did put up brand new, similar Windows 2019 server with 6 vCPU 's. And the 
newest release 9.16.20 starts there without problems, so this issue is really, 
like you addressed, with the vCPU count.

I hope the bug will be corrected in the future releases, so the 8 vCPU Name 
Server can be upgraded also. Thank you for pointing the problem for me!

BR, Sami Leino / Q-Net Oy


Lähettäjä: bind-users 
mailto:bind-users-boun...@lists.isc.org>> 
Puolesta Richard T.A. Neal
Lähetetty: torstai 19. elokuuta 2021 9.39
Vastaanottaja: bind-us...@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,

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.

From: Sami Leino mailto:sami.le...@qnet.fi>>
Sent: 19 August 2021 6:48 am
To: Richard T.A. Neal 
mailto:rich...@richardneal.com>>; 
bind-us...@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, 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 
mailto:bind-users-boun...@lists.isc.org>> 
Puolesta Richard T.A. Neal
Lähetetty: keskiviikko 18. elokuuta 2021 18.38
Vastaanottaja: bind-us...@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,

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 a starting point.

Best,

Richard.

From: bind-users 
mailto:bind-users-boun...@lists.isc.org>> On 
Behalf Of Sami Leino
Sent: 18 August 2021 10:56 am
To: bind-us...@isc.org
Subject: BIND 9.16.19 or any version newer than 9.16.15 does not start on 
Windows Server 2019

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 start BIND: Windows could not start the ISC BIND service on 
Local Computer. Error 1067: The process terminated unexpectedly.

Rollback to version 9.16.15 and process starts normally. Named-checkconf does 
not return anything.

Any ideas, what could be the problem?


C:\DNS\bin>dig -v
DiG 9.16.19

C:\DNS\bin>net start "isc bind
The ISC BIND service is starting.
The ISC BIND service could not be started.

More help is available by typing NET HELPMSG 3523.

Only this version works:

C:\DNS\bin>dig -v
DiG 9.16.15

C:\DNS\bin>net start "isc bind
The ISC BIND service is starting.
The ISC BIND service was started successfully.



Br,

Sami Leino
Järjestelmäasiantuntija
+358 40 823 8680
sami.le...@qnet.fi






Q-Net Oy
Yrittäjänkatu 17
65380 VAASA
www.qnet.fi



[cid:image001.png@01D7A49A.1E7DF8D0]


[cid:image002.png@01D7A49A.1E7DF8D0]-[cid:image003.png@01D7A49A.1E7DF8D0]






___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users