Greg Hudson wrote:
> /dev/random starvation explains the clock skew errors (kadmind isn't
> processing the kpropd authentication attempts until much later than they
> were sent) but doesn't really explain to me why your full dump
> connections are sometimes timing out. kdb5_util load does not read
On 06/17/2015 09:26 AM, Leonard J. Peirce wrote:
> The cause of kprop hanging was the MTU setting on our CentOS VMs.
Thanks, that is good to know.
> Unrelated to this I did notice something interesting. After reloading
> the database with kdb5_util kadmind naturally forces a full resync of our
>
