1Password sync issues with Synology Cloud Station
I have setup a little system to sync my vaults with Cloud Station, which basically sync folders. No problems ever happened until few days, when few files were constantly self-updating (contents.js and many dupes marked as the filename with .conflict).
Do you believe i should close systematically 1Password on the other machines while I keep one app open at a time? It's a problem that did not happen before.
Please help me solve this, thanks.
1Password Version: 1Password 5 Version 5.3.2 (532001) Agile Web Store
Extension Version: Not Provided
OS Version: 10.10.4
Sync Type: Folder with CloudStation
Comments
-
Hi @gabyu,
I'm sorry to hear about the issue you've encountered when syncing 1Password via Synology Cloud Station!
We've heard a few other similar reports about this. In a nutshell, what's happening is that at least 2 of the computers sharing the .agilekeychain file/folder think they have more up to date info than the other(s), and the sync service (in this case, Cloud Station) handles that by creating separate conflict files in the .agilekeychain. When that happens, 1Password is notified of the changes to the .agilekeychain and it tries to sync those changes to the local 1Password vault. So far, this is all basically normal behavior.
The problem is that 1Password doesn't support Synology Cloud Station, so it doesn't understand the way the conflict files are being created. Therefore, 1Password isn't able to resolve the conflict, and as the different computers continue to insist they each have the more up to date data, more conflict files are created and the sync is constantly triggered in 1Password, so it all ends up as an endless sync loop. (This is really a simplified summary of what happens, so hopefully what I wrote makes sense. Also, I apologize if I'm explaining something you already knew! :) )
So, getting back to your question:
Do you believe i should close systematically 1Password on the other machines while I keep one app open at a time?
I don't know for sure, but that's certainly something you can try. In theory, I think that would likely help to avoid multiple computers thinking they have newer data than the others. You may also want to check the time on each computer involved to make sure they all match. This isn't usually much of an issue on modern computers, but if for some reason the time on one or more computers is a bit off from the others, that might be related to the problem.
However, in the long run, conflicts can still happen, and because 1Password doesn't specifically support the way Synology Cloud Station handles conflicts, you can run into the same problem again. We do have ticket open with our developers about this, so it might be improved at some point, but I don't have any timeframe for that right now. I'll be happy to add your comments to our internal tracker, though, to let our developers know you've also run into this.
For now, you can fix this (at least temporarily) by disabling sync in 1Password on each computer and deleting the current .agilekeychain bundle from Cloud Station (which should remove it from each Mac). Then re-enable sync in 1Password on one of the Macs to re-create the .agilekeychain, which should sync to Cloud Station and the other Macs, and then you can re-enable sync in 1Password on the other Macs as well.
I hope this helps, but if you have more questions about that, please let us know - we're here for you! :)
ref: OPM-3074
0 -
Thank you @Drew_AG for your reply!
I believe that you nailed the problem -- I was traveling through different timezones with one of the computers that was synching to this Cloud Station folder few weeks ago, and since I'm back the issue started to happen, syncing endlessly.
Weirdly enough, only the Main vault was affected, and not the other ones (that was also in folder sync to a Cloud Station folder).
I've just wiped all sync information and start from scratch to see it the problems comes again. Additionally, I turned off the "Revision history" feature from Cloud Station. The issue does not repeat. yet.
Thanks a lot for this very detailed information!
0 -
I've just wiped all sync information and start from scratch to see it the problems comes again. Additionally, I turned off the "Revision history" feature from Cloud Station. The issue does not repeat. yet.
@gabyu: Excellent! Thanks for the update. On behalf of Drew, you're most welcome. I'm glad that helped!
I appreciate you letting us know what (so far) worked for you. Be sure to let us know how it goes, as I'm sure others will appreciate hearing of your experiences as well. Cheers! :)
0 -
Hi @gabyu,
While investigating another issue with Synology Cloud Station, we were able to consistently reproduce sync issues when the client and the server thought they were in different time zones or had different times set. Other customers reported high CPU usage when syncing via Cloud Station.
This suggests that a workaround, to prevent the creation of Cloud Station conflict files, could mean checking that the time and date as well as timezone on the server and clients is identical (possibly by using the same network time server). Can you please compare the time and date on your server and your client devices?
0 -
I am also having the high cpu usage but I am using Connected Data's File Transporter. I also have a Synology NAS and use Cloud Station but with a different vault but am not currently seeing a problem with Cloud Station and syncing -- only the Transporter. The Transporter Sync keeps notifying me of new conflict files that are being synced so it sounds very similar.
I'll try the similar steps to resolve as described here and see if that helps.
0 -
Should you have any issues @MacMike it will be best to keep the conversation to a single thread. Which thread is entirely your choice but we wouldn't want to waste your time by having two people asking you the same questions or causing confusion by going down different troubleshooting routes in parallel :smile:
0
