Have to keep restarting Amazon CloudDrive sync after upgrading from 6.9.4 Hotfix 1 to 6.10.2

[toledotom]

Since upgrading from 6.9.4 Hotfix 1 to 6.10.2, the Amazon CloudDrive sync has to be restarted continuously.  I do this by going to the admin page, Cloud, AmazonDrive button, settings, the settings button for sessions, create, apply.  I then get what seems to be a one-time sync.  Have to repeat that to get it to sync again.  Prior to upgrade to 6.10.2, the syncing was automatic and continuous.

Any ideas as to what might be the issue?

[toledotom]

Should mention in addition to above, the sync is partially working; if I create or copy a file locally it always makes it up to AmazonCloud.  But not the other direction - if I add to the Cloud (either directly through web or sent up by another synced ReadyNas it doesn't make it back down as explained above.

[JohnCM_S]

Hi toledotom,

On the Amazon Drive settings on the NAS, what is the sync direction selected? Is it on Bi-directional?

You may also download the NAS system logs, then check the amazon-drive.log. You might be able to find some clues there on what is causing the issue.

Regards,

[toledotom]

Sync is and has been set to bidirectional.

I test by logging into my amazon clouddrive account, and uploading a local file to the cloud in a particular folder.  It should download back to my ReadyNas in the selected folder, but it doesn't unless I go through the manual 'kickstart' procedure described in my first post (settings, apply, etc.)

I did a test a bit ago, and it successfully synced but again, only after manually kickingstarting the process as above.  Here is a log from the settings page of the Amazon Clouddrive under Cloud after successful manual kickstart:

Dec 16, 2019 09:17:42 AM	Amazon Drive service started.
Dec 16, 2019 09:17:42 AM	Starting to index local drive. This could take a while. Please wait.
Dec 16, 2019 09:17:48 AM	Indexing local drive is complete.
Dec 16, 2019 09:17:48 AM	Starting to scan cloud drive for changes. It could take a while. Please wait.
Dec 16, 2019 09:19:11 AM	Downloading /data/AmazonCloudDrive/Personal/2017 Terrain/vzw-global-modem-usb730l-ug.pdf ...
Dec 16, 2019 09:19:13 AM	/data/AmazonCloudDrive/Personal/2017 Terrain/vzw-global-modem-usb730l-ug.pdf was downloaded to local.
Dec 16, 2019 09:27:46 AM	Scaning cloud drive changes is complete.
Dec 16, 2019 09:27:46 AM	Starting to scan local drive for changes. It could take a while. Please wait.

 So clearly, things are in place for the sync to work, but it seems the Amazon drive service isn't always on; has to be 'kickstarted'.  Is there a setting to keep this on somewhere?

[toledotom]

Here are recent log entires from ReadyNas system log:

Dec 16, 2019 09:56:51 AM		System: Unauthorized. It could be invalid user account credential or the app is not allowed to access cloud drive. Stopped syncing with Amazon Drive.
Dec 16, 2019 09:56:42 AM		System: Service protocol amazon-drive is enabled.
Dec 16, 2019 09:53:27 AM		System: Unauthorized. It could be invalid user account credential or the app is not allowed to access cloud drive. Stopped syncing with Amazon Drive.
Dec 16, 2019 09:53:18 AM		System: Service protocol amazon-drive is enabled.
Dec 16, 2019 09:52:36 AM		System: Unauthorized. It could be invalid user account credential or the app is not allowed to access cloud drive. Stopped syncing with Amazon Drive.
Dec 16, 2019 09:06:37 AM		System: Successfully sent alert message.
Dec 16, 2019 09:06:20 AM		System: Alert settings are updated.
Dec 16, 2019 09:06:20 AM		System: Alert contact information was saved.
Dec 16, 2019 09:05:38 AM		System: Alert settings are updated.
Dec 16, 2019 09:05:38 AM		System: Alert contact information was saved.
Dec 16, 2019 09:00:18 AM		System: Alert message failed to send.
Dec 16, 2019 09:00:07 AM		System: Alert settings are updated.
Dec 16, 2019 09:00:07 AM		System: Alert contact information was saved.
Dec 16, 2019 08:59:04 AM		System: Alert message failed to send.
Dec 16, 2019 08:58:53 AM		System: Alert settings are updated.
Dec 16, 2019 08:58:53 AM		System: Alert contact information was saved.
Dec 16, 2019 08:57:23 AM		System: Alert settings are updated.
Dec 16, 2019 08:57:23 AM		System: Alert contact information was saved.
Dec 16, 2019 08:56:45 AM		System: Alert message failed to send.
Dec 16, 2019 08:56:33 AM		System: Alert settings are updated.
Dec 16, 2019 08:56:33 AM		System: Alert contact information was saved.
Dec 16, 2019 08:55:29 AM		System: Alert message failed to send.
Dec 16, 2019 08:55:18 AM		System: Alert settings are updated.
Dec 16, 2019 08:55:17 AM		System: Alert contact information was saved.
Dec 16, 2019 08:54:48 AM		System: Alert message failed to send.
Dec 14, 2019 04:18:44 AM		System: ReadyNASOS background service started.
Dec 13, 2019 05:36:31 PM		System: Alert message failed to send.
Dec 13, 2019 05:36:31 PM		System: The system is shutting down.
Dec 13, 2019 05:22:28 PM		System: ReadyNASOS background service started.
Dec 12, 2019 12:22:19 AM		System: Alert message failed to send.

So it looks like there is an authentication issue with Amazon CloudDrive that is causing the Amazon CloudDrive service to stop?  But I can't find anywhere to check the authentication settings.  And, if authentication is an issue, why would I be able to achieve a bidirectional sync by "kickstarting"?

[JohnCM_S]

Hi toledotom,

It does look like an issue with the authentication. Have you tried leaving and then rejoining the NAS to the Amazon Drive?

Regards,

[toledotom]

I Have tried "leaving and rejoining"; a little reluctant to do that again, since everything works other than I have to manually restart the sync.

If its an authentication issue, I'm wondering why the sync is working up to cloud but not down.  Also, how would leaving and rejoining change things?

Thx