I had the named process fail this past weekend on two secondaries running BIND
9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.13. It seems that logrotate.d is calling
the following script at the time of the failure.
/var/named/data/named.run {
missingok
su named named
create 0644 named named
Is there any good source of documentation on containerizing an authoritative
BIND instance in a Kubernetes cluster?
The main part I’m trying to grasp is how to dynamically horizontally scale the
cluster and keep the BIND notify process working between the containers.
Thanks,
Peter
--
Visit
I don’t mean to hijack the thread, but I think this is related. I also use the
BIND python modules. In particular, I'm using it to update my catalog zones as
described here: https://kb.isc.org/docs/aa-01401
This document has several references to BIND 9.18 without any mention of the
BIND
if the problem continues.
Thanks so much for your help!
From: Greg Choules
Date: Monday, August 1, 2022 at 6:21 PM
To: White, Peter
Cc: bind-users@lists.isc.org
Subject: Re: Bind 9.11/RHEL7 Server Freezes FUTEX_WAKE_PRIVATE
CAUTION: This email originated from outside of Penguin Random House. Please
I’m running BIND 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.9 (Extended Support
Version) on RHEL 7 in a chroot jail.
As of late, at times running some rndc commands are causing my server to lock
up. It’s usually an “rndc addzone” that triggers the issue. I’ll also mention
that I have recently started
5 matches
Mail list logo