[sync] Client and server timestamps don't match

[jochem at mondrian-it.nl]

Karsten,

As far as I understand, sync is a part of the horde package, which I use the
HEAD release of, and update daily.

I've tried this a couple more times, and it's now becoming clear that Horde
keeps using the same anchor ts. I've tried to find where horde should be
storing this value, but can't currently find it easily.

Having mysql log the queries taught me that a sync doesn't actually do an
UPDATE or INSERT on horde_datatree, where the anchor ts is saved. 

This was using yesterday's HEAD release.

Today's HEAD release doesn't complain about mismatching anchor ts's anymore.
It just doesn't save the anchor at all anymore:

Mar 09 14:45:24 HORDE [debug] [horde] SyncML: SyncML: No info about previous
syncs found for device fwm-05B08261D0B92 and database calendar [on line 88
of "/usr/share/php/SyncML/Command/Alert.php"]

It does an initial sync every time (pda leading), which has the same effect.

I've attached a copy of my horde.log and mysqld's querylog (n2svr02.log).
These were both wiped clean just before the sync, and copied right after, so
they contain nothing but the data generated by the sync. Horde.log is at
debug level. Both obviously have the ipadresses removed.

I'll be looking into this more after the weekend.

Regards,

Jochem

-----Oorspronkelijk bericht-----
Van: Karsten Fourmont [mailto:fourmont at gmx.de] 
Verzonden: donderdag 8 maart 2007 17:24
Aan: sync at lists.horde.org
Onderwerp: Re: [sync] Client and server timestamps don't match

Hi,

 > Not what it means. A syncml 'anchor' is an arbitrary value describing
 > "the point at which the last sync occurred" -
Exactly.

Different sync anchors have nothing to do with different clock times.
They can occur when one partner considers a sync "finished" and stores 
the sync anchor while another considers it "incomplete" and does not 
store the anchor

Jochem, are you using the current cvs version of the Sync module?

Cheers,
  Karsten


Andrew Suffield wrote:
> On Thu, Mar 08, 2007 at 02:16:45PM +0100, jochem at mondrian-it.nl wrote:
>> While testing the funambol windows mobile pluging 3.0.31 against horde's
>> syncml backend, I get the following INFO level entry in the log:
>>
>> client requested sync with anchor ts 16252726 but server has
>> timestamp16232634 on file. Enforcing SlowSync
>>
>> The time on the PDA and the server are (almost, only a few seconds off)
>> identical, and I've waited long enough between syncs to rule out that the
>> small difference might be a problem. 
> 
> Not what it means. A syncml 'anchor' is an arbitrary value describing
> "the point at which the last sync occurred" - it's usually the time in
> seconds, but there's no particular reason why it should be and clock
> differences are not an issue. The server just records the last value
> that the client sent it.
> 
> When the client anchor is higher than the one recorded on the server,
> that indicates the client has synced with something else since it last
> synced with this server (or something is broken).


-- 
sync mailing list - Join the hunt: http://horde.org/bounties/#sync
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: sync-unsubscribe at lists.horde.org