che2 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 w
On Tue, Dec 04, 2018 at 08:21:26AM +1100, Mark Andrews wrote:
> Add ‘database “rbt64”;’ to the dynamic zone configurations. It looks like
> you are
> overflowing the 32 bit serial number.
This was thought of as highly improbable when rbt64 was removed and
uint32_t was settled on for the type of
;>>
>>> 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 an
P 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
nning)
> 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:
>
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)
--
*Ism
6 matches
Mail list logo
