For now a quick workaround sprint, which waits, till internet is accessible. This script I'm running on start instead of regular dropbox start. It checks every 5 secs internet availability (loops forever) and after internet is online, dropbox launches. So far this works, till Dropbox fixes that issue in app itself.
#!/bin/bash while $(wget -q --spider http://google.com); ret=$? ; [ $ret -ne 0 ]; do sleep 5 done dropbox start -i
I'm not sure what you guys mean by unlinking account, but I have an issue where, after rebooting server, some folders containing a lot of files gets deleted on the server. dropbox then proceeds to sync this and the files gets deleted in the cloud, and subsequently deletion gets synced to other devices.
I haven't been able to nail down, when exactly the folders gets deleted, but it happens every time I reboot my server it seems.
Leeon, can you check if the output of this command keeps changing across reboots:
stat -f -c %i ~/.dropbox/instance_db
(Keep the output secret, just check whether it changes or remains the same.)
This shows the statvfs().f_fsid, which Dropbox on Linux uses as part of the config encryption key. The developers apparently thought it is persistent, but it really isn't. For example, on XFS partitions, the fsid can change if partitions are moved around, it can change if you boot with a USB stick connected, it can even change randomly on every reboot. Every time it changes, Dropbox becomes unable to decode its configuration and just deletes it.
(I really wish they had used something more stable, but I don't even know where to submit a bug report about it.)
@grawity Yes! You are right. When Dropbox starts normally, that ID is same as in previous boot, however when it disconnects, ID is different:
I need to say, that I'm not moving partitions nor connecting any USB drives etc. It just drifts by itself.
Update to possible workaround: moving and symlinking ~/.dropbox/instance_db is not enough, it lasted for a day and resets again. Now I moved whole ~/.dropbox folder. So far so good after one day.
If you need more help you can log a ticket with our Support Team here (expected response time 24 hours), or contact us on Twitter or Facebook.
For more info on available support options, see this article.
If you found the answer to your question, please 'like' the post to say thanks to the user!