incremental propagation gets stuck with UPDATE_FULL_RESYNC_NEEDED

Dave Steiner steiner at
Wed May 1 17:43:49 EDT 2013

On 4/29/2013 7:34 PM, Nico Williams wrote:
>> Any ideas why (1) it thinks it needs to do a full resync (kproplog shows one new
>> update on the master), and (2) why it's not doing the full resync?  What can I
>> check to see why it's not working.
> Can you truss/strace the kadmind (and follow fork and exec) and see
> what's happening?  It's probably a misconfiguration that will be come
> evident as soon as you see open(2) return some ENOENT in the
> truss/strace output.
> Nico
> --

Nothing from the truss stood out as a problem although I did get the following 
(probably from the kprop):

15522:  lstat64("/tmp/kproptktCIaquE", 0xFFBFF770)      Err#2 ENOENT
15522:  unlink("/tmp/kproptktCIaquE")                   Err#2 ENOENT

which seems kind of odd.

I'm wondering about my ports.  I start the kpropd on the slave with '-P 860' and 
have the 'iprop_port =860' in the kdc.conf files on both master and slave.  Is 
that correct?


More information about the Kerberos mailing list