Re: BIND 9.16.25 "file descriptor exceeds limit" messages

Anand Buddhdev wrote: > > The server has many IP addresses. In named.conf, there are 129 IPv6 addresses > in the "listen-on-v6" option and 128 IPv4 addresses in the "listen-on" option. > The server begins running, but then repeatedly emits this log: > > general: error: socket: file descriptor

Re: BIND 9.16.25 "file descriptor exceeds limit" messages

Hi Ondrej, It is 1024. I see named logging this: adjusted limit on open files from 4096 to 1048576 I thought there was no need to set LimitNOFILE=1048576 in the systemd unit file. Am I mistaken? Regards, Anand On 28/01/2022 14:47, Ondřej Surý wrote: Hi Anand, what is your open files

Re: BIND 9.16.25 "file descriptor exceeds limit" messages

Hi Anand, what is your open files limit before starting the server? (ulimit -n) Ondrej -- Ondřej Surý (He/Him) ond...@isc.org My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. > On 28. 1. 2022, at 14:33, Anand

BIND 9.16.25 "file descriptor exceeds limit" messages

I just tried to start BIND 9.16.25 on a server with 88 vCPUs, running CentOS 7. Systemd is used to start BIND, and it emits the following: general: notice: starting BIND 9.16.25 (Extended Support Version) general: notice: running on Linux x86_64 3.10.0-1160.24.1.el7.x86_64 #1 SMP Thu Apr 8

Re: Bind 9, dnssec, and .key .private files physical deletion after the key id becomes deleted from zone (the key becomes outdated)

Hi Mark! Very thankful again for your time. Sorry for answering so late, but I was not at the office yesterday. I answer below in blue for instance... El 2022-01-27 02:56, Mark Andrews escribió: > DNSSEC involves lots of timing / co-ordination points and if any of them get > delayed for any