The symptoms you describe sound typical of a run that is building on an earlier failed run, which sort of messed up the state.
Could you do the following: (a) Start from a fresh BBDB file (b) delete all entries in your carddav (c) create a new asynk profile Now run the sync. Even if it does not fully work, it will make it easier for me to debug. -Sriram On Fri, Mar 10, 2017 at 6:53 PM, Fr. John Jenkins <[email protected]> wrote: > Dear Sriram, > > Thanks for looking into this problem. I checked out the /issues/110 > branch and I still get the same symptoms. > > 1/ sync from bbdb -> CardDav seems to work - 1016 entries created and > written to the server. The first sync seems perfect. > > 2/ sync after this first syncronization however begins to have the same > problem as noted before. It sees that 1016 entries in bbdb are the same, > but then sees that there are 1016 "NEW" entries in Carddav but > "deleted". > > So it begins a "conflict resolution" : 1016 in bbdb need to be deleted. > > Here is the log from debug. Afterwards it begins creating new entries in > BBDB and then deletes them. There seems to be something fundamentally > wrong in the way it classifies the CD entries as 'deleted'. > > I am trying ASynK now with NextCloud which is a more up to date version > of Owncloud 9.1 thinking that there was something perhaps fixed in a > newer version. Unfortunately it is showing the same behavior as OC 9.1. > > Also to not that ASynK hangs on "Writing sync state to the CardDAV > server", and stays this way for at least an hour (I interrupted it with > C-c after an hour of waiting). > > Here is the log from the second sync: > > Last synk for profile SSPXZA was at: 2017-03-10T07:23:01.93Z > [12:00:25.997 INFO] ==== bb ===== > [12:00:25.997 INFO] New : 0 > [12:00:25.997 INFO] Modified : 0 > [12:00:25.997 INFO] Unchanged : 1016 > [12:00:25.997 INFO] ===== > [12:00:25.997 INFO] Total Entries : 1016 > [12:00:25.997 INFO] Deleted : 0 > [12:00:25.997 INFO] ==== cd ===== > [12:00:25.997 INFO] New : 1016 > [12:00:25.997 INFO] Modified : 0 > [12:00:25.997 INFO] Unchanged : 0 > [12:00:25.997 INFO] ===== > [12:00:25.998 INFO] Total Entries : 1016 > [12:00:25.998 INFO] Deleted : 1016 > [12:00:25.998 INFO] Number of entries modified both places > (conflicts): 0 > [12:00:25.998 INFO] conflict resolve direction : 1. db1id: bb, db2id: > cd > [12:00:25.998 INFO] After conflict resolution, size of bb mod : 0 > [12:00:25.998 INFO] After conflict resolution, size of cd mod : 0 > [12:00:25.999 INFO] After conflict resolution, size of bb del : 0 > [12:00:25.999 INFO] After conflict resolution, size of cd del : 1016 > [12:00:25.999 INFO] ============================== > ======================= > [12:00:25.999 INFO] Sending New bb entries to cd > [12:00:25.999 INFO] ============================== > ======================= > [12:00:25.999 INFO] No new entries that need to be synched > [12:00:25.999 INFO] ============================== > ======================= > [12:00:25.999 INFO] Sending Modified bb entries to cd > [12:00:25.999 INFO] ============================== > ======================= > [12:00:25.999 INFO] No modified entries that need to be synched > [12:00:26.000 INFO] ============================== > ======================= > [12:00:26.000 INFO] Synching Deleted bb entries to cd > [12:00:26.000 INFO] ============================== > ======================= > [12:00:26.000 INFO] No deleted entries that need to be synched. > [12:00:26.000 INFO] ============================== > ======================= > [12:00:26.000 INFO] Sending New cd entries to bb > [12:00:26.000 INFO] ============================== > ======================= > [12:00:26.000 INFO] 1016 new entries to be synched. > > > In die Thu, Mar 09 2017, Sriram Karra scripsit: > > > John, thanks for sending me the test credentials. I think I have isolated >> the issue. I have put a fix in this branch: >> https://github.com/skarra/ASynK/tree/issues/110 >> > > If you can validate it works for you as well, then I will test against some >> other older CardDAV servers and then merge it to master. >> > > -Sriram >> > > On Tue, Mar 7, 2017 at 8:45 PM, Sriram Karra <[email protected]> wrote: >> > > > John, if you can create a test account for me on an OwnCloud 9.1 instance >> > that would help me debug this issue. I have debugged other issues with >> > OwnCloud using a similar approach with other users. It appears like >> > installing a version of Owncloud 9.1 from scratch is going to be too >> > painful for the present purpose. >> > >> > On Tue, Mar 7, 2017 at 2:31 PM, Sriram Karra <[email protected]> >> wrote: >> > >> >> John, I am sorry to hear about this. I have not tested ASynK with >> latest >> >> versions of OwnCloud, so I cannot comment on whether it is "officially" >> >> incompatible. As this is a side project that I maintain in my free >> time I >> >> have not invested in building robust end to end tests but rely on my >> users >> >> to inform me about issues with different stores as they encounter them. >> >> This is the first report I have received about problems with OwnCloud >> 9.1. >> >> >> >> I will investigate this issue a little more in the coming weeks. In the >> >> mean time I guess you have no option but to roll back your version of >> >> ownCloud or just pause using ASynK, depending on your relative >> preference. >> >> >> >> >> >> >> >> On Tue, Mar 7, 2017 at 12:08 AM, Fr. John Jenkins < >> [email protected]> >> >> wrote: >> >> >> >>> Also I should point out that before synching I removed from BBDB all >> the >> >>> fields that had an asynk:id as I knew that would probably cause >> >>> difficulties. Thus the BBDB addressbook was entirely 'clean' when I >> began >> >>> the process. >> >>> >> >>> -- >> >>> Find ASynK useful? Consider leaving a tip at this Bitcoin address: >> >>> 1KarraEGixRyScZ9qFHdekxNkgpPTuzWBc >> >>> --- >> >>> You received this message because you are subscribed to the Google >> >>> Groups "ASynK Users" group. >> >>> To unsubscribe from this group and stop receiving emails from it, send >> >>> an email to [email protected]. >> >>> For more options, visit https://groups.google.com/d/optout. >> >>> >> >> >> >> >> > >> > > -- > Find ASynK useful? Consider leaving a tip at this Bitcoin address: > 1KarraEGixRyScZ9qFHdekxNkgpPTuzWBc > --- You received this message because you are subscribed to the Google > Groups "ASynK Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Find ASynK useful? Consider leaving a tip at this Bitcoin address: 1KarraEGixRyScZ9qFHdekxNkgpPTuzWBc --- You received this message because you are subscribed to the Google Groups "ASynK Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
