On Wed, 2015-05-27 at 11:50 +0200, Daniel CLEMENT wrote: > [1]daniel@e6330d ~ $ syncevolution memotoo > [INFO] calendar+todo: inactive > [INFO] addressbook: starting first time sync from server (peer is > server) > [INFO] calendar: starting first time sync from server (peer is server) > [INFO] memo: starting first time sync from server (peer is server) > [INFO] todo: resuming first time sync from server (peer is server) > [INFO] creating complete data backup of datastore todo before sync > (enabled with dumpData and needed for printChanges) > Local data changes to be applied during synchronization: > *** todo *** > Comparison was impossible. > > [INFO] addressbook: first time sync done unsuccessfully > [ERROR] addressbook: local, status 20048 > [INFO] calendar: first time sync done unsuccessfully > [ERROR] calendar: local, status 20048 > [INFO] memo: first time sync done unsuccessfully > [ERROR] memo: local, status 20048 > [ERROR] Aborting because of unexpected slow sync for datastore(s): > addressbook calendar memo > [INFO] Doing a slow synchronization may lead to duplicated items or > [INFO] lost data when the server merges items incorrectly. Choosing > [INFO] a different synchronization mode may be the better alternative. > [INFO] Restart synchronization of affected source(s) with one of the > [INFO] following sync modes to recover from this problem: > [INFO] slow, refresh-from-server, refresh-from-client > [INFO] > [INFO] Analyzing the current state: > [INFO] syncevolution --status memotoo addressbook calendar memo > [INFO] > [INFO] Running with one of the three modes: > [INFO] syncevolution --sync [slow|refresh-from-remote|refresh-from-local] > memotoo addressbook calendar memo
Please follow these instructions and then report back. SyncEvolution is always going to stop like this in your current state unless you tell it otherwise, which is intentional. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
