Any suggestions on this message of a week ago? Another run today produced a similar result:
[INFO] @default/calendar: started [INFO] @default/calendar: sent 106/563 [INFO @google] @google/calendar: started [INFO @google] adding "..." ... a number of similar lines, interrupted occasionally with lines like [ERROR @google] error code from SyncEvolution access denied (remote, status 403): PUT: bad HTTP status: <status 1.1, code 403, class 4, Forbidden> ... and then ending with [INFO @google] @google/calendar: received 105/669 [INFO] @default/calendar: first time sync done unsuccessfully [INFO] log in succeeded, but server refuses access - contact server operator [INFO] creating complete data backup after sync (enabled with dumpData and needed for printChanges) Synchronization failed, see /home/twilson/.cache/syncevolution/google-2014-04-27-14-14/syncevolution-log.html for details. Changes applied during synchronization: +---------------|-----------------------|-----------------------|-CON-+ | | @default | @google | FLI | | Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS | +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+ | calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | refresh-from-local, 0 KB sent by client, 0 KB received | | item(s) in database backup: 669 before sync, 669 after it | | access denied (remote, status 403) | +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+ | start Sun Apr 27 14:14:25 2014, duration 2:23min | | access denied (remote, status 403) | +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+ First ERROR encountered: error code from SyncEvolution access denied (remote, status 403): PUT: bad HTTP status: <status 1.1, code 403, class 4, Forbidden> Data modified @default during synchronization: *** @default/calendar *** no changes I can send the syncevolution-log.html file privately, if you like. Thanks, --Todd Todd Wilson, PhD Department of Computer Science California State University, Fresno On Sat, Apr 19, 2014 at 12:08 PM, Todd Wilson <[email protected]> wrote: > On Fri, Apr 18, 2014 at 4:58 AM, Patrick Ohly <[email protected]> wrote: >> There is a "calendar ID". Use that in the URL of the form: >> >> https://www.google.com:443/calendar/dav/<calendar >> ID>/events/?SyncEvolution=Google >> >> The problem with --print-databases and Google CalDAV is already fixed. I >> think Google did not implement support for calendar discovery initially, >> and when they did, it required some more changes in SyncEvolution. > > OK, after using my calendar ID, which had the form > > <random string>@group.calendar.google.com > > in the configuration, I was able to set up the target-config and print > items from the calendar (after adding a couple of test items). When I > went to push the local copy of my zimbra calendar (@default context, > file backend) to the Google calendar, all seemed to be going well for > a while, until the sync failed: > > $ syncevolution --sync refresh-from-local google > [INFO] @default/addressbook: inactive > [INFO] @default/memo: inactive > [INFO] @default/todo: inactive > [INFO @google] target side of local sync ready > [INFO @google] @google/addressbook: inactive > [INFO @google] @google/memo: inactive > [INFO @google] @google/syncurl=https:: inactive > [INFO @google] @google/todo: inactive > [INFO @google] @google/calendar: starting first time sync from server > (peer is server) > [INFO @google] @google/calendar: deleting 0 > [INFO] @default/calendar: starting first time sync, two-way (peer is client) > [INFO] creating complete data backup of source calendar before sync > (enabled with dumpData and needed for printChanges) > @default data changes to be applied during synchronization: > *** @default/calendar *** > Comparison was impossible. > > [INFO] @default/calendar: started > [INFO] @default/calendar: sent 106/563 > [INFO @google] @google/calendar: started > [INFO @google] adding "..." > .... 112 more "adding" lines like this last one, with my event > titles in quotes .... > [INFO @google] @google/calendar: received 105/669 > [INFO] @default/calendar: first time sync done unsuccessfully > [INFO] server database not found, check URI 'calendar' > [INFO] creating complete data backup after sync (enabled with dumpData > and needed for printChanges) > > Synchronization failed, see > /home/twilson/.cache/syncevolution/google-2014-04-19-11-41/syncevolution-log.html > for details. > > Changes applied during synchronization: > +---------------|-----------------------|-----------------------|-CON-+ > | | @default | @google | FLI | > | Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS | > +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+ > | calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | > | refresh-from-local, 0 KB sent by client, 0 KB received | > | item(s) in database backup: 669 before sync, 669 after it | > | object not found (remote, status 404) | > +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+ > | start Sat Apr 19 11:41:16 2014, duration 1:45min | > | object not found (remote, status 404) | > +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+ > First ERROR encountered: error code from SyncEvolution object not > found (remote, status 404): PUT: bad HTTP status: <status 1.1, code > 404, class 4, Not Found> > > Data modified @default during synchronization: > *** @default/calendar *** > no changes > > Any explanation for what happened, and what I should do next? _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
