NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Got a brand new ReadyNAS 104 and it crashes when trying to setup Dropbox
I got my ReadyNAS 104 a week or so ago, and slapped 4 1TB Seagate drives in it, updated firmware to the newest release 6.4.2 and setup an iSCSI target. It's been working great and not had any issues so far. I'm also keeping some regular movies and pictures on the SMB shares so I thought it'd be a good idea to buy the Dropbox Pro storage and link it to my ReadyNAS since I see that's an option.
But when I go to Backup and then Cloud Storage and click the "ON" slider for Dropbox my ReadyNAS either doesnt' respond (it flips to ON but doesn't let me click activate and when I refresh the page is OFF again) OR it will actually crash the system interface and I get the "Connecting to ReadyNAS" box with the progress bar... it eventually reconnects and Dropbox is still set to OFF. I found this by looking at the logs and seeing this entry: System: ReadyNASOS service or process (readynasd) was restarted.
So it appears that whenever it's try to switch on the Dropbox module it's crashing. To see if it was a browser issue I tried Chrome and IE (with compatibility settings and trusted sites) and it did it in both. I then tried to turn the ReadyNAS Vault by clicking its ON button to see what would happen and it switches on ok and it will actually switch on and stay switched on.
Any ideas? I've rebooted twice now and even tried reuploading the 6.4.2 firmware, then rebooted, thinking that might help.
Received your logs. Thanks.
Looks like you are missing a DNS server or a gateway possibly. Lots of services like msmtp (e-mail alerts), Cloud services, are producting errors mentioning unable to connect to internet services. You have many e-mails queued up to send, but this seems intermittent (worked on Mar 2nd, didn't work Mar 3rd).
Dropbox is erroring out: error in dropbox/request_token api. http-status=500, means Internal Server error.
Can you double check DNS servers are valid and also that your default gateway is on your routable network?
11 Replies
Replies have been turned off for this discussion
When you created an iSCSI target, how much of your volume did you consume?
Can you try, for testing, a non-Dropbox Pro account and confirm whether you have an issue? I recall a bug open about Dropbox Pro account and the Sync with Dropbox functionality.There's a log which should explain the crash reason. If you don't mind, please forward us a copy of your logs so I can confirm.
Thanks!The iSCSI target is 1.0GB out of 2.72GB (rest is used for SMB shares), I have 4 1TB disks using the XRAID default of RAID5.
The type of Dropbox account doesn't matter because at this point the NAS doesn't even know what kind of account I have. I am not getting that far. I am going to "Backup" and then "Cloud Backup" and where it has Dropbox listed and you have to click the slider button to "ON" to switch it on, that is where it either doesn't respond or crashes the interface. Below that is the Activate button where I'd activate my Dropbox account but it is grayed out since the switch is set to OFF. Since I can't switch it ON it stays grayed out and thus ReadyNAS doesn't know what kind of account I have.
Mind sending your logs in so I can review what is going on?
Received your logs. Thanks.
Looks like you are missing a DNS server or a gateway possibly. Lots of services like msmtp (e-mail alerts), Cloud services, are producting errors mentioning unable to connect to internet services. You have many e-mails queued up to send, but this seems intermittent (worked on Mar 2nd, didn't work Mar 3rd).
Dropbox is erroring out: error in dropbox/request_token api. http-status=500, means Internal Server error.
Can you double check DNS servers are valid and also that your default gateway is on your routable network?
You are right, that was the problem, nice! One of my NICs didn't have a DNS server setup so I disabled that NIC and now when I click ON the Activate button lights up and I was able to finish the setup and it's now working.
The reason I didn't have the second NIC setup correctly was because I use one NIC with a real IP address on my normal network, so it has a DNS and gateway and is seen on my network. The other NIC is plugged directly into one of 4 NICs on my server which has a VMware virtual switch and NIC tied to it. I did this to keep iSCSI traffic on my regular network without have to create a separate VLAN and the VM host can see the iSCSI target that way while the ReadyNAS is seen (as SMB) on my regular network through the other NIC. It actually works great except for this... I guess the ReadyNAS tried to send outside traffic out the NIC that doesn't really go anywhere.
I noticed that I setup eth0 with the "fake" network and eth1 with the real network. I'm guessing that it tries eth0 first when trying to reach the Internet so I'm going to swap the settings of eth0 and eth1 so that eth0 has the IP on my regular network with Internet access and see if that works with both NICs enabled.
ReadyNAS won't care what network adapter you use as long as it is configured correctly. Even if eth0 is your 'fake' iSCSI network, your eth1, with a proper DNS and gateway, should be the default route for all traffic. Do not set a gateway on your eth0 and your eth1 should have a gateway. If you see your eth1 gateway in eth0, don't panic. That's normal.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
