incremental propagation gets stuck with UPDATE_FULL_RESYNC_NEEDED

[Dave Steiner]

I've turned on incremental propagation for my two test Kerberos machines but 
continually tries to do a full sync but doesn't.

Apr 29 16:50:40 host1 kadmind[19112](Notice): Request: iprop_get_updates_1, 
UPDATE_FULL_RESYNC_NEEDED; Incoming SerialNo=0; Outgoing SerialNo=N/A, success, 
client=kiprop/host2.rutgers.edu at DEFAULT_REALM, 
service=kiprop/master1.rutgers.edu at DEFAULT_REALM, addr=XXX.XX.XXX.XX
Apr 29 16:50:40 host1 kadmind[19112](Notice): Request: iprop_full_resync_1, 
spawned resync process 1227, client=kiprop/host2.rutgers.edu at DEFAULT_REALM, 
service=kiprop/master1.rutgers.edu at DEFAULT_REALM, addr=XXX.XX.XXX.XX
Apr 29 16:50:40 host1 kadmind[19112](Notice): Request: iprop_get_updates_1, 
UPDATE_FULL_RESYNC_NEEDED; Incoming SerialNo=0; Outgoing SerialNo=N/A, success, 
client=kiprop/host2.rutgers.edu at DEFAULT_REALM, 
service=kiprop/master1.rutgers.edu at DEFAULT_REALM, addr=XXX.XX.XXX.XX
Apr 29 16:50:40 host1 kadmind[19112](Notice): Request: iprop_full_resync_1, 
spawned resync process 1230, client=kiprop/host2.rutgers.edu at DEFAULT_REALM, 
service=kiprop/master1.rutgers.edu at DEFAULT_REALM, addr=XXX.XX.XXX.XX
Apr 29 16:50:40 host1 kadmind[19112](Notice): Request: iprop_get_updates_1, 
UPDATE_FULL_RESYNC_NEEDED; Incoming SerialNo=0; Outgoing SerialNo=N/A, success, 
client=kiprop/host2.rutgers.edu at DEFAULT_REALM, 
service=kiprop/master1.rutgers.edu at DEFAULT_REALM, addr=XXX.XX.XXX.XX
Apr 29 16:50:40 host1 kadmind[19112](Notice): Request: iprop_full_resync_1, 
spawned resync process 1233, client=kiprop/host2.rutgers.edu at DEFAULT_REALM, 
service=kiprop/master1.rutgers.edu at DEFAULT_REALM, addr=XXX.XX.XXX.XX
Apr 29 16:50:40 host1 kadmind[19112](Notice): Request: iprop_get_updates_1, 
UPDATE_FULL_RESYNC_NEEDED; Incoming SerialNo=0; Outgoing SerialNo=N/A, success, 
client=kiprop/host2.rutgers.edu at DEFAULT_REALM, 
service=kiprop/master1.rutgers.edu at DEFAULT_REALM, addr=XXX.XX.XXX.XX
Apr 29 16:50:40 host1 kadmind[19112](Notice): Request: iprop_full_resync_1, 
spawned resync process 1236, client=kiprop/host2.rutgers.edu at DEFAULT_REALM, 
service=kiprop/master1.rutgers.edu at DEFAULT_REALM, addr=XXX.XX.XXX.XX

Sometimes I get the spawned resync and sometimes I don't.  But it never seems to 
do anything.  I still have the same entries when I do kproplog on the master and 
the slave.  There is no dumped file that I can find.

Before starting this (as I had worked with iprop a few months back) did a full 
kprop and deleted the principal.ulog files to start fresh.

One odd thing about our setup is we have multiple realms.  As far as I can tell 
from previously playing with iprop is that it doesn't work on multiple realms.  
But at this time, I just want to iprop my default realm.

The kdc.conf looks like:

[realms]
         DEFAULT_REALM = {
                  .....
                 kadmind_port = 760
                 kdc_ports = 88
                  ......
                 iprop_enable = true
                 iprop_port = 860
         }

On the slave server, the kprop is started as

    kpropd -r DEFAULT_REALM -f /path/data/DEFAULT_REALM/from_master -F 
/path/data/DEFAULT_REALM/principal -P 860 -S

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.

-ds