From: Martin F. <ma...@si...> - 2005-09-21 22:41:26
|
Hello, it looks like opensync has some problems when handling mapping conflicts. I have a syncing group with evo2-sync and file-sync. I only have some items in evo. The first sync went fine and when I provoked a conflict and tried to ignore it, all went fine, too. But the third sync I got this error: ** ERROR **: file opensync_member.c: line 1065 (osync_member_read_change): assertion failed: (fmtsink->functions.read ! = NULL) aborting... The fourth sync found mapping conflict in every item (ignoring worked), but again the next sync failed, like in the third sync. I tried to find out where the problem might be, but couldn't find real solutions. I only found out, that if you delete .opensync/groupX/changelog.db, the third sync works fine. I've added the traces, for the first, second, third, and the fourth sync. martn |