Re: Calendar syncing issues

Quoting Michael J Rubinsky <[email protected]>:

> Quoting John H. Bennett III <[email protected]>:
>
>> Quoting Simon B <[email protected]>:
>>
>>> On 14 Apr 2016 05:35, "John H. Bennett III"  
>>> <[email protected]> wrote:
>>>>
>>>>  Quoting [email protected]:
>>>>
>>>>
>>>>>  
>>>>>      -------- Original message --------
>>>>>    From: Michael J Rubinsky <[email protected]>
>>>>>    Date: 4/5/16 8:11 AM (GMT-06:00)
>>>>>    To: [email protected]
>>>>>    Subject: Re: [kronolith] Calendar syncing issues
>>>>>     
>>>>>
>>>>> Quoting Michael J Rubinsky <[email protected]>:
>>>>>
>>>>>> Quoting Michael J Rubinsky <[email protected]>:
>>>>>>
>>>>>>> Re-adding the mailing list in CC for the remainder of the discussion.
>>>>>>>
>>>>>>> Quoting John H. Bennett III <[email protected]>:
>>>>>>>
>>>>>>>> Quoting Michael J Rubinsky <[email protected]>:
>>>>>>>>
>>>>>>>>> Quoting John H. Bennett III <[email protected]>:
>>>>>>>>>
>>>>>>>>>> Quoting Michael J Rubinsky <[email protected]>:
>>>>>>>>>>
>>>>>>>>>>> Quoting John H. Bennett III <[email protected]>:
>>>>>>>>>>>
>>>>>>>>>>>> Hello all,
>>>>>>>>>>>>
>>>>>>>>>>>> I am having an issue getting my calendar to sync, correctly.  
>>>>>>>>>>>> If I add an event using kronolith, then that event won't sync 
>>>>>>>>>>>> to my mobile device.  I will still get the event reminder, and 
>>>>>>>>>>>> the event will be shown in the daily agenda email.  If I add 
>>>>>>>>>>>> an event using my mobile, then that event will sync just fine 
>>>>>>>>>>>> to kronolith.  I've no idea how this get into this state.  
>>>>>>>>>>>> Things had been working just fine until the last set of 
>>>>>>>>>>>> updates, but I'm not sure if those updates are really the cause.
>>>>>>>>>>>>
>>>>>>>>>>>> If it will help, I can provide a sync log showing when I add 
>>>>>>>>>>>> an event to my phone, then sync, and when I add with kronolith 
>>>>>>>>>>>> and sync, which hopefully would show something.
>>>>>>>>>>>>
>>>>>>>>>>>> I appreciate whatever help can be given to me.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> You don't mention what protocol you are using to synchronize.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thank you,
>>>>>>>>>>>>
>>>>>>>>>>>> John
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> kronolith mailing list
>>>>>>>>>>>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>>>>>>>>>>>> To unsubscribe, mail: [email protected]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> mike
>>>>>>>>>>> The Horde Project
>>>>>>>>>>> http://www.horde.org
>>>>>>>>>>> https://www.facebook.com/hordeproject
>>>>>>>>>>> https://www.twitter.com/hordeproject
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I'm sorry about that.  I am using Activesync.  My mobile device 
>>>>>>>>>> is a Galaxy S6, with Android 6.0.1, Android security patch level 
>>>>>>>>>> February 1, 2016.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Then, yes. Please provide a synclog showing both a successful and 
>>>>>>>>> unsuccessful attempt.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Part of my horde/conf.php
>>>>>>>>>> $conf['activesync']['params']['driverconfig'] = 'horde';
>>>>>>>>>> $conf['activesync']['storage'] = 'Sql';
>>>>>>>>>> $conf['activesync']['emailsync'] = true;
>>>>>>>>>> $conf['activesync']['version'] = '14.1';
>>>>>>>>>> $conf['activesync']['auth']['type'] = 'basic';
>>>>>>>>>> $conf['activesync']['autodiscovery'] = 'user';
>>>>>>>>>> $conf['activesync']['outlookdiscovery'] = false;
>>>>>>>>>> $conf['activesync']['ping']['heartbeatmin'] = 60;
>>>>>>>>>> $conf['activesync']['ping']['heartbeatmax'] = 2700;
>>>>>>>>>> $conf['activesync']['ping']['heartbeatdefault'] = 480;
>>>>>>>>>> $conf['activesync']['ping']['deviceping'] = true;
>>>>>>>>>> $conf['activesync']['ping']['waitinterval'] = 5;
>>>>>>>>>> $conf['activesync']['enabled'] = true;
>>>>>>>>>> $conf['activesync']['logging']['type'] = false;
>>>>>>>>>>
>>>>>>>>>> John
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> kronolith mailing list
>>>>>>>>>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>>>>>>>>>> To unsubscribe, mail: [email protected]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> mike
>>>>>>>>> The Horde Project
>>>>>>>>> http://www.horde.org
>>>>>>>>> https://www.facebook.com/hordeproject
>>>>>>>>> https://www.twitter.com/hordeproject
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi Mike,
>>>>>>>>
>>>>>>>> Thank you for looking at the sync log.  2 files attached.  The 
>>>>>>>> first file, I added event on my phone, then did a sync.  It shows 
>>>>>>>> up on my personal calendar.  Second file done on Kronolith, event 
>>>>>>>> doesn't show up.  None of the previous events I had on my personal 
>>>>>>>> calendar are showing up.  One recurring event I've had on there 
>>>>>>>> for close to 2 years.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> This is weird:
>>>>>>>
>>>>>>> 016-04-04T23:01:49-05:00 INFO: [2596] Initializing message diff 
>>>>>>> engine for Ab2ed48a2 (@Tasks@)
>>>>>>> 2016-04-04T23:01:49-05:00 INFO: [2596] 
>>>>>>> Horde_Core_ActiveSync_Driver::getSyncStamp(@Tasks@, 42915);
>>>>>>> 2016-04-04T23:01:49-05:00 INFO: [2596] Using SYNCSTAMP 42915  
>>>>>>> for Ab2ed48a2.
>>>>>>> 2016-04-04T23:01:49-05:00 INFO: [2596] 
>>>>>>> Horde_Core_ActiveSync_Driver::getServerChanges(@Tasks@, 42915, 
>>>>>>> 42915, 1452571309, 0, 1, 100, )
>>>>>>>
>>>>>>> Somehow the collection id of Ab2ed48a2 is supposed to be for your 
>>>>>>> calendar, but it is being translated server side in some places as 
>>>>>>> tasks. This would definitely cause problems, as it is causing Horde 
>>>>>>> to poll Nag for changes when it should be polling Kronolith. I will 
>>>>>>> have to look into this further to see how this could have happened.
>>>>>>
>>>>>>
>>>>>>
>>>>>> The synckey that is being requested by the client for the Calendar 
>>>>>> collection is present in your syncCache attached to two different 
>>>>>> collections - both the Tasks and Calendar. I would need to see the 
>>>>>> log when this actually happened to see when the duplicate sync key 
>>>>>> was added, but it is most likely a client issue - sending the wrong 
>>>>>> synckey during a request which corrupted the synccache. I will look 
>>>>>> to add code to catch this case and reset the state.
>>>>>
>>>>>
>>>>> I forgot to ask what state storage backend is in use, SQL or Mongo?
>>>>>
>>>>> --
>>>>> mike
>>>>> The Horde Project
>>>>> http://www.horde.org
>>>>> https://www.facebook.com/hordeproject
>>>>> https://www.twitter.com/hordeproject
>>>>>
>>>>> --
>>>>> kronolith mailing list
>>>>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>>>>> To unsubscribe, mail: [email protected]     
>>>>>   I'm using SQL.
>>>>>    
>>>>>   Thank you, 
>>>>>    
>>>>>   John
>>>>
>>>>
>>>> Is there anything else you need from me for this?  No matter what  
>>>> I do, I can't get things working as they were, so I'm  asking  
>>>> before I delete the account from my device and the activesync  
>>>> devices from horde.
>>>
>>> Frankly those are my first two synch issue trouble-shooting synch  
>>> issues.  Not the last resort.
>>>
>>> Simon
>>
>> That message was really to Mike since I sent him my device sync  
>> logs, and he had made the "This is weird" comment.  I had already  
>> removed the device from horde activesync.  This time around, it's  
>> just my device that is having this issue, but if this were  
>> happenning to multiple devices, taking the time to delete and  
>> re-create accounts for every device wouldn't be something I'd want  
>> to do which is why I don't think deleting and recreating the  
>> account on a device should be the first thing to do.  I'd rather  
>> provide information so that if there is an issue, it can be fixed.
>
> Sorry, I've been sick the last few days and am still getting over  
> things. I'll try to finish looking at this soon. Basically though,  
> the only explanations I have is that either your client is BADLY  
> broken, or your system is generating colliding UUIDs for the  
> synckeys. This would normally be a VERY rare occurrence and I would  
> not expect that to happen multiple times.
>
> I've already added code to try to help catch this when loading the  
> device state, but still want to add code that checks for the  
> collision when the synckey is generated. This will prevent the case  
> when it's your system generating colliding keys, but not if your  
> client is broken.

This feature is included in the latest Horde_ActiveSync package  
released last night.

-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

-- 
kronolith mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]