Re: zone_journal_compact: could not get zone size: not found

You need to ask FreeIPA people and your vendor (but my guess is that the dyndb plugin provided by RH doesn’t provide this method).--Ondřej Surý — ISC (He/Him)My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.On 8. 7. 20

Re: zone_journal_compact: could not get zone size: not found

Running gdb showed that the "not found" comes from this piece of code isc_result_t dns_db_getsize(dns_db_t*db, dns_dbversion_t*version, uint64_t*records, uint64_t*bytes) { REQUIRE(DNS_DB_VALID(db)); REQUIRE(dns_db_iszone(db)); if(db->methods->getsize!= NULL) { return((db->methods->getsize)(db, ve

Re: netstat showing multiple lines for each listening socket

On Mon, Jul 8, 2024 at 7:52 AM Tom Marcoen (EXT) via bind-users wrote: > > I observe the same behaviour. I have similar output for TCP/53 on the > loopback and public IP addresses. The IP addresses and port numbers are the > same, but the fd (file descriptors?) are different. I assumed different

Re: zone_journal_compact: could not get zone size: not found

On 08-07-2024 13:42, Greg Choules wrote: Hi Kees. Hi Greg, thanks for the quick reply. A few questions: - What version of BIND are you running? 9.16.23 (in centos that is 32:9.16.23-15.el9) - How large (number of RRs) are your zones? My main zone (renamed to example.com) is about 800 RRs (

RE: netstat showing multiple lines for each listening socket

I observe the same behaviour. I have similar output for TCP/53 on the loopback and public IP addresses. The IP addresses and port numbers are the same, but the fd (file descriptors?) are different. I assumed different threads of the same process. # named -V | grep ^BIND BIND 9.18.26 (Extended S

Re: zone_journal_compact: could not get zone size: not found

Hi Kees. A few questions: - What version of BIND are you running? - How large (number of RRs) are your zones? - What is the peak rate of dynamic updates? - Do you have "max-journal-size" configured to anything? - Are you perhaps getting short on disc storage in the place where BIND keeps its files?

zone_journal_compact: could not get zone size: not found

Hi, At the moment I have three FreeIPA systems (replicas), recently installed with CentOS 9-Stream. All three of these show this message at irregular intervals. Jul 03 07:50:44 iparep5.example.com named[541]: zone example.com/IN: zone_journal_compact: could not get zone size: not found Jul 03

Re: netstat showing multiple lines for each listening socket

Hi Robert, it's the same PID for all lines, parent process is systemd. The lines in the netstat output are exact duplicates (same IP, port and PID). Other tools like ss show the same, so it's not a problem with netstat. It's the same bahaviour on different machines, some upgraded from Debian <

Re: netstat showing multiple lines for each listening socket

That's correct. Since BIND 9.16, `named` binds to individual addresses instead of "any" because it needs to send responses back from the same address and it's just easier this way. Cheers, -- Ondřej Surý (He/Him) ond...@isc.org My working hours and your working hours may be different. Please do

Re: netstat showing multiple lines for each listening socket

Some diagnostics is needed. When you reboot, does it show it up multiple binds to the same port? Can your run netstat -tP to identify the process ID (are they the same or different). There may also be other options to provide more diagnostics. -Trying to determine if you are really binding

netstat showing multiple lines for each listening socket

Hello, we have been running some BIND nameservers on Debian-based systems for many years. Until (including) Debian 10 with BIND 9.11.5, netstat always showed only one line per listening socket, e.g. tcp0 0 10.x.x.x:53 0.0.0.0:* LISTEN 1234/named tc