Tickets :: Comment on [#10008] SyncML in Horde 4 only does slow syncs

* Your Email Address
* Spam protection	Enter the letters below: . .. ..__ . .. . \|\/\|\|\/\|[ __\| \|\|\/\| \| \|\| \|[_./\|/\\|\| \|
Comment	> Horde only does slow syncs with my N900 client (syncevolution), but > other users have reported similar problems on the mailing lists. As > Jan stated, it seems that Horde fails to read the timestamp of the > last sync from the database. > > I tried to produce a clean log. Here is what I did: > > 1. rm everything in /tmp/sync > 2. horde log output set to "Debug" > 3. dropped all horde_syncml tables and recreated them using the horde > configuration and deleted all turba contacts and calender items > 4. deleted everything in ~/.cache/syncevolution on the n900 > 5. manually initiated slow sync with syncevolution with > > 'syncevolution --sync refresh-from-client <myconfigname>' > > That worked flawlessly. > > 6. Initiated a "normal" two-way sync with 'syncevolution <myconfigname>' > > Same problem again. Horde can't seem to find the timestamp: > > UNKNOWN:Previous sync found for database contacts; client timestamp: > UNKNOWN:Client requested sync with anchor timestamp 20110426T173321Z > but server has recorded timestamp . Enforcing SlowSync > > Attached to this bug there is a tarball which contains: > > - Horde /tmp/sync folder contents (synclogs.tgz) > - Syncevolution output during slow sync (syncevolution_output_slow_sync) > - Syncevolution output during normal sync (syncevolution_output_normal_sync) > - content of the horde_* database tables (horde_syncml.sql) >
Attachment
Watch this ticket

Saved Queries