[horde] Fw: Activesync unexpected full sync
Michael J Rubinsky
mrubinsk at horde.org
Sun Oct 29 22:21:54 UTC 2017
Quoting Michael J Rubinsky <mrubinsk at horde.org>:
> --
> mike
> Sent from mobile
> ________________________________
> From: Michael J Rubinsky <mrubinsk at horde.org>
> Sent: Oct 21, 2017 1:44 PM
> To: matt at fivesmallponies.com
> Subject: Re: [horde] Activesync unexpected full sync
>
> Thanks for the info. Gives me a place to start looking.
>
> Haven't forgotten about the issue, just have to find some free time
> somewhere....
Ok. I've found some issues in both the ActiveSync library and
Kronolith that seem to be causing an issue. While I never reproduced
the exact issue, there were some issues with moving an event on the
EAS client from a user-owned calendar to a calendar owned by another
user. I've fixed these issues (and a few other minor things).
Hopefully this will resolve the issue you are seeing.
Note that *stable* kronolith never supported moving items from one
calendar to another from the EAS client. This was introduced in the
current master branch.
The fixes are available via git now, and will be in the next bug fix
release of ActiveSync (and the next major release of Kronolith).
mjr
> --
> mike
> Sent from mobile
> ________________________________
> From: Matthew Seymour <matt at fivesmallponies.com>
> Sent: Oct 21, 2017 9:19 AM
> To: horde at lists.horde.org
> Subject: Re: [horde] Activesync unexpected full sync
>
>>
>> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>
>>> Quoting Torben Dannhauer <torben at dannhauer.info>:
>>>
>>>>> Am 18.10.2017 um 17:29 schrieb Matthew Seymour
>>>>> <matt at fivesmallponies.com>:
>>>>>
>>>>>
>>>>> Hi folks,
>>>>>
>>>>> I'm continuing to have this problem. I've managed to capture the
>>>>> issue with a smaller log file (only 300MB this time) but can't
>>>>> see anything obvious. It looks as if the iOS device has
>>>>> difficulty contacting the server, for some reason, then re-syncs
>>>>> everything. So the activesync logs look fine, because they are.
>>>>> What I'm not clear on is what might be causing this... it's also
>>>>> a guess as to what's actually going on.
>>>>>
>>>>> Unfortunately this is making calendars unreliable so I'd love to
>>>>> get to the bottom of this.
>>>>>
>>>>> Any pointers are welcome.
>>>>>
>>>>> Matt
>>>>>
>>>>> --
>>>>> Horde mailing list
>>>>> Frequently Asked Questions: http://horde.org/faq/ To unsubscribe,
>>>>> mail: horde-unsubscribe at lists.horde.org
>>>>
>>>> Matthew,
>>>>
>>>> I have also the impression that the cendar sometimes resybcs and
>>>> forgets so dates. I was unable to get logs of this since I always
>>>> discoverey he missing appointments when I missed an event. I‘m
>>>> very interested in your investigations!
>>>>
>>>> -> correction edit: oops lots of typos. I meant "I have also the
>>>> impression that the calendar resyncs and forgets some dates"
>>>
>>> If it's strictly calendar data, might be related to parsing MAPI
>>> data in meeting invitations coming from MS clients. Try installing
>>> the bcmath php extension, which improves performance over PEAR's
>>> (sometimes buggy) Math_BigInteger package.
>>>
>>>>
>>>> Torben
>>
>> I have found a semi reliable way of causing this to fail. If I have
>> two calendars synced via activesync and I move an entry between the
>> calendars it all goes wrong. The move happens, then a full resync.
>> I can find no errors in the activesync log though. I have
>> experienced the problem without multiple calendars being synced,
>> just wondered if this might give a clue as to what the problem is.
>>
>> Matt
>>
>> --
>> Horde mailing list
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>>
>
>
>
> --
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
--
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 9272 bytes
Desc: PGP Public Key
URL: <https://lists.horde.org/archives/horde/attachments/20171029/d874d75d/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 821 bytes
Desc: PGP Digital Signature
URL: <https://lists.horde.org/archives/horde/attachments/20171029/d874d75d/attachment-0001.bin>
More information about the horde
mailing list