I think this turned out to be an IP address that was attached to eth0 that
had actually been moved. Those kadmind.log errors were correlated with the
connection problems though (always were present when a failure like this
occurred), if that is useful info.
Chris
On Wed, Aug 22, 2018 at 08:09 G
On 08/18/2018 01:53 AM, Chris Hecker wrote:
> I just got this again today, this time instead of EBUSY, the libkadm5
> client got "Cannot resolve network address for admin server in requested
> realm (43787576)". Same "The referenced context has expired" stuff in
> kadmind.log. I'm confused about
I just got this again today, this time instead of EBUSY, the libkadm5
client got "Cannot resolve network address for admin server in requested
realm (43787576)". Same "The referenced context has expired" stuff in
kadmind.log. I'm confused about the kadmind.log lines...I can see the
client having
I have a long-running daemon that reads a kadm5 admin key from a file
keytab into a memory keytab before dropping privs, and then when the
kadm5 connection drops (using checks for KADM5_RPC_ERROR), it loops and
tries to reconnect with kadm5_init_with_skey. This works fine, with 1.9
it would stay
