Forum Discussion
Amazon Drive not turning on
I've been using Amazon Drive to back up my ReadyNas for over a year. I checked Amazon to make sure that everything was backed up, but saw that the backups stopped a few weeks ago. So, I went on my ad...
I am also having the same problem with Amazon Drive switch not turning on and not allowing me to connect. I am using ReadyNAS v6.9.3
I have tried 2 different browswer's: Safari and Firefox. I have cleared the cache which looked initially like something was going to happen but only to fail to turn on again.
Anyone have any success enabling Amazon Drive feature?
jbattista wrote:
I have tried 2 different browswer's: Safari and Firefox. I have cleared the cache which looked initially like something was going to happen but only to fail to turn on again.
yes the software does work and well, but of late it would seem something within ReadynasOS broke it - differing browsers will not help as I have found.
Hi there
An update for all on what my issue was, which may or may not be the same for you.
Basically the ReadynasOS internal database had become corrupt and this is something that cannot be resolved by the end user - I know I would not be keen - because this has a higher risk of causing the Middleware to not work.
What was found by the technical team at Netgear was:- They checked the logs I sent and found that at noon on July 7, my Amazon Drive application had an abnormal interruption, which directly caused the app login token to be lost.
- Jul 07 11:54:38 Honbu readynasd[3043]: Service 'fvamazon.service' goto unexpected state 'failed'. Expect to be 'inactive'('deactivating').
- Jul 07 11:55:33 Honbu fvamazon[27972]: Not provisioned
- Since the token is lost and the internal database check is passed, the application is always in the startup->failed state.
Once the database was reset for me, I tried again and still had issues with ACD connecting with readynas and had to have the database reset again due to the same issue. I have not tried again due to work commitments, but may wait till the patch is available as I feel it may happen again.They will look to optimize the process of checking in the future firmware releases so that the customer should be able to log in again when the program fails the validity check and cannot be corrected.This has highlighted to them that design of this fucntionality is not as robust as one would expect.Finally, since the issue occurred on July 7 and logs are only kept for a short period of time they could not find more detailed information to find the root cause.A big thanks to Bryan and his team at Netgear Technical for assistance - certainly approaciated.
yoban wrote:
...Basically the ReadynasOS internal database had become corrupt and this is something that cannot be resolved by the end user ...because this has a higher risk of causing the Middleware to not work.
...wait till the patch is available as I feel it may happen again.
...They will look to optimize the process of checking in the future firmware releases so that the customer should be able to log in again when the program fails the validity check and cannot be corrected....A big thanks to Bryan and his team at Netgear Technical for assistance - certainly approaciated.So, did Bryan confirm to you that a firmware patch is coming out to address this issue?
I was able to SSH in and confirm that my service was hung similar to the way you described.
:/$ systemctl status fvamazon.service
● fvamazon.service - Amazon Cloud Drive client for ReadyNAS
Loaded: loaded (/lib/systemd/system/fvamazon.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit-hit) since ...[last reboot]...
Main PID: 20331 (code=exited, status=255)
Bass_Nas wrote:So, did Bryan confirm to you that a firmware patch is coming out to address this issue?
I was able to SSH in and confirm that my service was hung similar to the way you described.
:/$ systemctl status fvamazon.service
● fvamazon.service - Amazon Cloud Drive client for ReadyNAS
Loaded: loaded (/lib/systemd/system/fvamazon.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit-hit) since ...[last reboot]...
Main PID: 20331 (code=exited, status=255)Hi there,
It was offered to me that after QA completes the verification of aa optimisation of the code base to improve the stability, they could apply this patch to my device, if you wanted. Otherwise wait for the next OS update with the hope it is included.
I must also point out, that there testing could not replicate one of my issues based on some screenshots, I sent them which seemed to point to a time out issue..??Occured when Configuring ACD on ReadyNAS
- They checked the logs I sent and found that at noon on July 7, my Amazon Drive application had an abnormal interruption, which directly caused the app login token to be lost.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
