followed this tutorial which worked until the end where Dropbox just wouldn’t stay on
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
×Usually Killed signal is when it runs out of memory.
You can verify that by checking syslog files.
It is located at /var/log/syslog which you can open with favorite text editor:
- nano /var/log/syslog
In this file, search for Out Of Memory killer warnings/errors. If you find any for it, that means your Droplet doesn’t have enough RAM memory to run it.
To fix it you can upgrade your Droplet or add swap as a free variant.
I was afraid it might be a memory problem. The syslog file includes many lines like this: Out of memory: Kill process 5535 (dropbox) score 235
But I wish I didn’t have to add swap or upgrade my droplet. It’s a brand-new droplet, and I wish to sync only a subset of my Dropbox directory — Could my droplet running out of memory because the whole of my Dropbox directory is being copied? Is there a way to configure the ‘Exclude’ list before starting Dropbox? I wouldn’t mind destroying this droplet and trying again from scratch.
Sorry, this is field I can’t help you very much, as I never used Dropbox on Droplets.
You didn’t specified which tutorial you followed, but there is How to setup Dropbox CLI by DigitalOcean.
Look at Exclude part, you can try stopping service, excluding or even starting and ASAP excluding.
I hope someone who used this can help you more than I can. ::)
That’s exactly what i’ll be trying next: Since in order to Exclude directories has to be running, I’ll ASAP exclude with a wildcard that excludes everything before adding the directories I do want to sync. The second thing I’ll try will be to resize my droplet temporarily and see if that helps me manage my selective syncing on Dropbox so that I can resize back down. Thanks for the tip on swap space and syslog.