Just created the issue #758 in gitlab.
Don't have the core dumps.

*Ismael *
On 12/3/18 7:14 PM, Mark Andrews wrote:

On 4 Dec 2018, at 8:59 am, Ismael Suarez Maldonado <[email protected]> 
wrote:

This in named.conf??

Don't see any database config in our setup.

This is configured as a caching server which does not have any zones.
The error comes from “newversion” (dns_db_newversion()) which is only called on
dynamic zones though those include the zone maintaining the managed keys for
DNSSEC and slave zones.

Rather than continue this here can you open a issue of on gitlab.isc.org and
if you still have a core dump can you include the stack backtrace from it.

Ismael
On 12/3/18 5:21 PM, Mark Andrews wrote:
Add ‘database “rbt64”;’ to the dynamic zone configurations.  It looks like you 
are
overflowing the 32 bit serial number.


On 4 Dec 2018, at 3:36 am, Ismael Suarez Maldonado <[email protected]>
  wrote:

Hi to all.

We have to DNS cache servers that have failed (after some time/days running) 
with the following error. Afterwards we can start the service with no errors. 
This is afecting our clients as we are an ISP and would like to get to the root 
cause of this.

Error:
Dec  2 16:04:20 wdnscache2 named[8617]: rbtdb.c:1497: fatal error:
Dec  2 16:04:20 wdnscache2 named[8617]: RUNTIME_CHECK(rbtdb->next_serial != 0) 
failed
Dec  2 16:04:20 wdnscache2 named[8617]: exiting (due to fatal error in library)

Bind version: 9.11.5
System OS: CentOS 7.5.1804 (Core)


--
Ismael

This email was scanned by Bitdefender
_______________________________________________
Please visit
https://lists.isc.org/mailman/listinfo/bind-users
  to unsubscribe from this list

bind-users mailing list

[email protected]
https://lists.isc.org/mailman/listinfo/bind-users

This email was scanned by Bitdefender

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

bind-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to