Re: Ubuntu headless install not working

Here is the output from the wget and Dropboxd commands:

levoy@levoy:~$ cd ~ && wget -O - "https://www.dropbox.com/download?plat=lnx.x86_64" | tar xzf -
--2020-01-02 18:03:27-- https://www.dropbox.com/download?plat=lnx.x86_64
Resolving www.dropbox.com (www.dropbox.com)... 162.125.1.1, 2620:100:6016:1::a27d:101
Connecting to www.dropbox.com (www.dropbox.com)|162.125.1.1|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://clientupdates.dropboxstatic.com/dbx-releng/client/dropbox-lnx.x86_64-87.4.138.tar.gz [following]
--2020-01-02 18:03:27-- https://clientupdates.dropboxstatic.com/dbx-releng/client/dropbox-lnx.x86_64-87.4.138.tar.gz
Resolving clientupdates.dropboxstatic.com (clientupdates.dropboxstatic.com)... 99.86.39.59
Connecting to clientupdates.dropboxstatic.com (clientupdates.dropboxstatic.com)|99.86.39.59|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 101508210 (97M) [binary/octet-stream]
Saving to: ‘STDOUT’

- 100%[===================>] 96.81M 41.7MB/s in 2.3s

2020-01-02 18:03:29 (41.7 MB/s) - written to stdout [101508210/101508210]

levoy@levoy:~$ ~/.dropbox-dist/dropboxd
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-eBYwi0
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/dropbox'
dropbox: setting python path '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138:/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.pthread._linuxffi_pthread.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cpuid.compiled._cpuid.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.resolv.compiled._linuxffi_resolv.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/librsyncffi.compiled._librsyncffi.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.sys.compiled._linuxffi_sys.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/posixffi.libc._posixffi_libc.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.gnu.compiled._linuxffi_gnu.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/PyQt5.QtNetwork.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/PyQt5.QtDBus.cpython-37m-x86_64-linux-gnu.so'
levoy@levoy:~$ ./dropbox.py status
Dropbox isn't running!
levoy@levoy:~$

:grinning::slight_smile: Seems you have killed the daemon! That's why "Dropbox isn't running!".

Ok... Try following and paste the result:

rm -rf ~/.dropbox ~/.dropbox-dist ~/Dropbox; ./dropbox.py start -i

In that way the daemon will be detached and you can check the status in same terminal without killing anything. :wink:

I tried your command, and it popped up a warning that the daemon didn't exist, and it seemed to then download it from Dropbox and install it, but ended up in exactly the same spot.  The output is below.  Should it pop up a link to paste into my browser?  Or am I not getting that far for some reason?

evoy@levoy:~$ rm -rf ~/.dropbox ~/.dropbox-dist ~/Dropbox; ./dropbox.py start -i
Starting Dropbox..../dropbox.py:342: PyGIDeprecationWarning: Since version 3.11, calling threads_init is no longer needed. See: https://wiki.gnome.org/PyGObject/Threading
GObject.threads_init()
./dropbox.py:503: PyGTKDeprecationWarning: Stock items are deprecated. Please use: Gtk.Button.new_with_mnemonic(label)
self.ok = ok = Gtk.Button(stock=Gtk.STOCK_OK)
./dropbox.py:508: PyGTKDeprecationWarning: Stock items are deprecated. Please use: Gtk.Button.new_with_mnemonic(label)
cancel = Gtk.Button(stock=Gtk.STOCK_CANCEL)
./dropbox.py:378: PyGIDeprecationWarning: GObject.idle_add is deprecated; use GLib.idle_add instead
GObject.idle_add(self.loop_callback, *ret)
./dropbox.py:388: PyGIDeprecationWarning: GObject.idle_add is deprecated; use GLib.idle_add instead
GObject.idle_add(self.on_done)
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-En2Hr9
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/dropbox'
dropbox: setting python path '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138:/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.pthread._linuxffi_pthread.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cpuid.compiled._cpuid.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.resolv.compiled._linuxffi_resolv.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/librsyncffi.compiled._librsyncffi.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.sys.compiled._linuxffi_sys.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/posixffi.libc._posixffi_libc.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.gnu.compiled._linuxffi_gnu.cpython-37m-x86_64-linux-gnu.so'
success!
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-VudtxG
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/dropbox'
dropbox: setting python path '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138:/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.pthread._linuxffi_pthread.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/cpuid.compiled._cpuid.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.resolv.compiled._linuxffi_resolv.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/librsyncffi.compiled._librsyncffi.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.sys.compiled._linuxffi_sys.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/posixffi.libc._posixffi_libc.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/linuxffi.gnu.compiled._linuxffi_gnu.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
Done!
levoy@levoy:~$ dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/PyQt5.QtNetwork.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/usr/local/google/home/levoy/.dropbox-dist/dropbox-lnx.x86_64-87.4.138/PyQt5.QtDBus.cpython-37m-x86_64-linux-gnu.so'

levoy@levoy:~$ ./dropbox.py status
Dropbox isn't running!
levoy@levoy:~$

Response on next page.

There is only one reason for such thing. You try run in graphical shell! Don't you?!

In such cases Dropbox application tries to redirect the link directly to default web browser. Just go there and declare you would like to connect. If, for some reason, this don't happens try to execute previous command in clear console shell. In advance login, using following:

ssh levoy@localhost

Type your password (computer account, not Dropbox one) and proceed as in my previous post. Once you get your application connected to the Dropbox account, you can run the application in any other way, also (connection is granted). :wink:

I think you are looking in the correct direction, but I don't understand your instructions.

My situation is that I am using Chrome Remote Desktop to log from a Mac into the headless Linux instance.  In CRD I see a simulated desktop, I can launch terminal windows, browsers, etc.  In Chrome in my Mac I have popups allowed.  I also have popups allowed in the Chrome browser in the Linux instance.  During installation of the daemon I see popups from the installation process appear in my CRD window.  Thus, I would expect that if it wanted to pop up a window giving me a URL link to log into Dropbox, it would have appeared.  No? 

So given this setup, what do you suggest I do?  What do you mean by "Just go there and declare you would like to connect".  How?  Or on which machine would I execute 

ssh levoy@localhost

 ?

It worked!  Thank you *so* much!  I ssh'ed from the Linux instance to @localhost, then re-ran your commands, and it gave me the link to copy/paste into the browser on that Linux instance.

Could you take one more minute, and explain to me why that works?

What does this ssh'ing to localhost do?

-Marc

Ok... I will try explain in more details.

In Linux (unlike Mac and Windows) graphical shell doesn't "stick" to the place where particular program runs. One program can run on machine (real or virtual) where graphics isn't available, but program widow can come up on another machine where X interface is supported (either native - Linux, or emulated), if the interface is redirected. Something similar seems happens in your case. For example, X redirection in 'ssh' command could be achieved using '-X' option. In some graphical terminal emulators is a checkbox for same reason. Anyway, when local graphics is available or X interface is redirected, corresponding session is graphical, otherwise session is clear console. Seems you have used a redirection for your initial session. I have not any idea why browser doesn't bring up, but one possibility would be missing browser installation on the Linux. If so, you can install Firefox, for example, using:

sudo apt-get install firefox

About 'ssh' command: As I mentioned above already, to redirect X interface '-X' option is need. When this option gets miss, newly created session is clear terminal session and Dropbox application doesn't try any browser, but print the link as a console output. That's it. :wink:

Hope this casts some light. :slight_smile:

PS: Something else! You don't actually run headless Linux! As I'm reading your above post (before the last) seems your install is graphical. So you incorrectly "titled" it as headless. Probably you didn't set a default browser.

Again, you have been very helpful.  It appears that I have a default browser already, but if I click on a .html file in the Files app (on my Linux instance), it challenges me to enter a password to "Unlock keyring".  My Linux account password, which is also my Chrome passphrase, seems to work.  Perhaps Dropbox was failing to pop up the login web page because it reached this challenge and silently failed on it.  Once I've entered my password, then clicking on other .html files immediately bring them up on my Chrome browser (in the Linux instance).

-Marc Levoy
 Distinguished Engineer
 Google

Different user, same problem (as far as I can see)

Ran the suggested:

rm -rf ~/.dropbox ~/.dropbox-dist ~/Dropbox; ./dropbox.py start -i

Did get the 'visit URL' prompt, did so, and my Dropbox directory started to populate.

Process indicated by ~/.dropbox/dropbox.pid doesn't exist.

dropbox.py output is:

Traceback (most recent call last):
File "/tmp/dropbox.py", line 1603, in <module>
ret = main(sys.argv)
File "/tmp/dropbox.py", line 1592, in main
result = commands[argv[i]](argv[i+1:])
File "/tmp/dropbox.py", line 743, in newmeth
return meth(*n, **kw)
File "/tmp/dropbox.py", line 1224, in status
lines = dc.get_dropbox_status()['status']
File "/tmp/dropbox.py", line 714, in __spec_command
return self.send_command(str(name), kw)
File "/tmp/dropbox.py", line 672, in send_command
ok = self.__readline() == "ok"
File "/tmp/dropbox.py", line 646, in __readline
toret = self.f.readline().rstrip("\n")
File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 30: ordinal not in range(128)

Hi DavidLedger,

Your problem isn't the same definitely. Above issue was for authentication troubles.

---

DavidLedger wrote:
...

rm -rf ~/.dropbox ~/.dropbox-dist ~/Dropbox; ./dropbox.py start -i

Did get the 'visit URL' prompt, did so, and my Dropbox directory started to populate.

...

---

As could be seen (you mention - "Dropbox directory started to populate") you don't have such trouble. Seems Dropbox application works for you.

---

DavidLedger wrote:
...

Process indicated by ~/.dropbox/dropbox.pid doesn't exist.

...

---

Waw, realy?! What is the result from:

cat ~/.dropbox/dropbox.pid; echo; ps -C dropbox

---

DavidLedger wrote:
...
File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 30: ordinal not in range(128)

---

Seems you have some communication problem between Dropbox daemon and Dropbox control script. Are you sure they run in same context? If contexts differs (for example: daemon has run as a service with different uid), then connection would fail, because both - daemon and control script - can't get to each other. Also, are you using beta build? If so, there was reported similar issues. Revert back to stable release! Take a look in your account settings, is "Early releases" enabled. Make sure it's turned off! Make sure you Dropbox daemon isn't running (no Dropbox process gets in ps list) - quit/stop/kill, if any. Execute in sequence:

dropbox.py status
rm -rf ~/.dropbox ~/.dropbox-dist
dropbox.py start -i
dropbox.py status

What is the result?

david@ivdweb:5$: cat ~/.dropbox/dropbox.pid; echo; ps -C dropbox
13930
PID TTY TIME CMD
david@ivdweb:6$:

and

david@ivdweb:6$: dropbox.py status
Dropbox isn't running!
david@ivdweb:7$: rm -rf ~/.dropbox ~/.dropbox-dist
david@ivdweb:8$: dropbox.py start -i
Starting Dropbox...Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

Then pop-up window (no copy for paste allowed):

Dropbox is the easiest way ... Head to ...

In order to use Dropbox, you must download the proprietary daemon.

Note: python3-gpg (python3-gpgme for Ubuntu 16.10 and lower) is not installed, we will not be able to verify binary signatures.

(Click OK, continuing)

dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-24rT2I
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/dropbox'
dropbox: setting python path '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273:/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
success!

dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-pCINKo
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/dropbox'
dropbox: setting python path '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273:/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtNetwork.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtDBus.cpython-37m-x86_64-linux-gnu.so'
Done!
david@ivdweb:9$: dropbox.py status
Waiting to be linked to a Dropbox account...
To link this computer to a Dropbox account, visit the following url:
https://www.dropbox.com/cli_link_nonce?nonce=b2a7e4aa6efa50b0c859a9705a6a9885

(Done this twice already, but done again now with this nonce data)

Then did:

david@ivdweb:10$: dropbox.py status
Dropbox isn't running!
david@ivdweb:11$:

This is on an AWS Lightsail box which is where the 'bitnami' bit comes from.

David

To be honest, I'm getting confused here. Initially you said "Dropbox directory started to populate". In this context, dropbox has to run, but according your result it's not. That's not possible. This "populate" doesn't fall from the sky! There is some process running to do that. As could be seen from the last post, the communication problem already got gone - a good news. Is syncing continue (like initial populate)? You have GUI, why you note install as a headless? What is the result after starting:

dropbox.py start
ps -C dropbox
cat ~/.dropbox/dropbox.pid; echo

Is there some error message? In your last post could be seen two tries for runs of the daemon (the second one unsuccessful - of course). Is this happens again?

I don't have a GUI on that box. I says to visit a URL which I do using Firefox on my Ubuntu laptop. That seems to trigger the connection. No idea how - I have not put my Dropbox login details anywhere on the AWS server 'ivdweb'. It can't be using the IP address to link the two actions unless the Dropbox startup works out that it's being started ultimetely from an ssh from the same IP as the browser. Perhaps I'll delete it all and start again. Where, apart from ~/dropbox, ~/.dropbox-dist, the ~/Dropbox itself and the 'dropbox' command in /usr/biin, does it put stuff?

Thanks,

David

Hi DavidLedger,

It's not need have GUI on particular device (including your virtual box) to run GUI session! 😉 It's enough running application has access to the GUI on your workstation (your Ubuntu laptop in particular).

---

DavidLedger wrote:
...

Then pop-up window (no copy for paste allowed):

Dropbox is the easiest way ... Head to ...

In order to use Dropbox, you must download the proprietary daemon.

Note: python3-gpg (python3-gpgme for Ubuntu 16.10 and lower) is not installed, we will not be able to verify binary signatures.

 

(Click OK, continuing)

...

Where that pop-up comes from? 🤔 There are two ways - either you run Dropbox on your local Ubuntu or X-forwarding is on go. I gonna bet on second one. Be careful, you can redirect X, but not dropbox control connection! Dropbox daemon and the control script must run on same context. Either on remote box or locally, for both cases in same user context. Otherwise they will never get together. To be honest, I have not experience in AWS, but seems the X redirection gets performed for (and behind) you.

---

DavidLedger wrote:

... No idea how - I have not put my Dropbox login details anywhere on the AWS server 'ivdweb'. ...

---

What you mean "login details" here? 🙂 If you mean your user id (the email in fact) and password - yes they never get saved on any device. Based on your choice during device linking, a connection id gets created for every one device connection which serve as a credentials. This id (OAuth id - to be more precise) is keep locally in "~/.dropbox" folder. That's why every time you remove this folder you have to link your device (real or virtual) again - credentials (together with local, no account, settings, if any) get lost!

---

DavidLedger wrote:

.... Perhaps I'll delete it all and start again. Where, apart from ~/dropbox, ~/.dropbox-dist, the ~/Dropbox itself and the 'dropbox' command in /usr/biin, does it put stuff?

---

There is not "~/dropbox", but "~/.dropbox" folder (one missing dot, be careful). The daemon related resources are limited to "~/.dropbox" and "~/.dropbox-dist" folders. Removing them you remove any pointing trace to the daemon. "~/Dropbox" folder keeps your user data (the local mirror of your account content, when in sync). The control script could be set wherever you want, if installed by hand. If you install it using a install package, then "/usr/bin/dropbox" is the spot. When you install a package some other files get installed together with the control script. Everything installed through install package gets removed on same package uninstall.

Yes, it's good idea start on clear from beginning. Take care to not mixing the local and remote account!

Good luck. 😉

    In what follows the cmnd no in the prompt just happened to be similar because I the previos connections had stopped overnight. I have manually added A and B. Hope I've done that right.

    Deleted ~/.dropbox, ~/.dropbox-dist

    did, from HOME:

david@ivdwebA:15$: wget -O - "https://www.dropbox.com/download?plat=lnx.x86_64" | tar xzf -

    This completed, then did:

david@ivdwebA:16$: .dropbox-dist/dropbox
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-4ydX4w
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/dropbox'
dropbox: setting python path '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273:/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
. . .

. . .

dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtDBus.cpython-37m-x86_64-linux-gnu.so'

    At this point the o/p in this window (A) stopped. After a few minutes, in a different xterm, same host, same user. I did:

david@ivdwebB:13$: dropbox status

Starting...
To link this computer to a Dropbox account, visit the following url:
https://www.dropbox.com/cli_link_nonce?nonce=87baf19271329e9d8c459177239af242

    Did this in Firefox window on Ubuntu labtop (one false start because URL suggestion replaced with previous version :-) ). Then on second remote xterm (B) did:

david@ivdwebB:14$: dropbox status
Syncing 6,153 files
Indexing 6,153 files...
david@ivdwebB:15$: ll Dropbox/

    <<Displayed file listing>>

david@ivdwebB:16$: dropbox status
Traceback (most recent call last):
File "/usr/bin/dropbox", line 1603, in <module>
ret = main(sys.argv)
File "/usr/bin/dropbox", line 1592, in main
result = commands[argv[i]](argv[i+1:])
File "/usr/bin/dropbox", line 743, in newmeth
return meth(*n, **kw)
File "/usr/bin/dropbox", line 1224, in status
lines = dc.get_dropbox_status()['status']
File "/usr/bin/dropbox", line 714, in __spec_command
return self.send_command(str(name), kw)
File "/usr/bin/dropbox", line 672, in send_command
ok = self.__readline() == "ok"
File "/usr/bin/dropbox", line 646, in __readline
toret = self.f.readline().rstrip("\n")
File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 28: ordinal not in range(128)
david@ivdwebB:17$:

    At this point the first remote xterm (A) resumed o/p with:

Killed
david@ivdwebA:17$:

Thanks,

David

Hi DavidLedger,

I just tried, but can't reproduce your situation.

---

DavidLedger wrote:
...

dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtDBus.cpython-37m-x86_64-linux-gnu.so'

 

    At this point the o/p in this window (A) stopped. After a few minutes, in a different xterm, same host, same user. I did:

...

---

"At this point" Dropbox application tries open default web browser window to authenticate, but can't (for some reason - could be a daemon bug - multiple times reported, including in the current thread). That happens because you are running on GUI session. You can force usage of clear console variant using:

ssh $USER@localhost
~/.dropbox-dist/dropboxd # or: dropbox start -i

In such a way the authentication link would be shown in first (and eventually the only) console. Seems you are using free account, that's why connections are limited to 3 and you have to keep their number below, so new connection creation to be possible. You can control the existing connections in the "Devices" section of your security settings. Anyway... seems you have successfully link your device to the account.

---

DavidLedger wrote:

 ...
File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 28: ordinal not in range(128)
david@ivdwebB:17$:

    At this point the first remote xterm (A) resumed o/p with:

Killed

...

---

Here, seems some hidden bug brings up. I can't reproduce the situation, but other users in the forum had report the same "symptoms". Probably some special circumstances are needed for the particular bug's reproduction. The code point 0xe2 isn't valid in ASCII table, definitely. Here Dropbox development have to take care, but better don't rely too much. Over years Dropbox confirmed their carelessness for Linux users, unfortunately.

Try to find out some workaround for you. Can't you follow the application status from the status icon (somewhere in the browser window representing the remote display)?

Submitted this yesterday but it was rejected because of an 'HTML error' which has been removed. Something in this must be seen as HTLM and so missing when you get it.

The reason Dropbox cannot open the default web browser is that there isn't one. It's a headless server accessed via an xterm over ssh. I'm not running on a GUI session, just an xterm shell session on the remote server displaying back to my Ubuntu laptop. Dropbox may 'think' I'm using a GUI session, but I'm not. Trying the 'dropbox start -i' you suggested gives me:

david@ivdweb:/home/bitnami$ dropbox start -i
Starting Dropbox...dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-WYMNgP
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/dropbox'
dropbox: setting python path '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273:/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtNetwork.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
Dropbox isn't running!
Done!
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtDBus.cpython-37m-x86_64-linux-gnu.so'

david@ivdweb:/home/bitnami$

I have a personal paid-for account.:

I ran out of hosts last year and had to start a paid account. I share across three Macs, one Ubuntu, one iPad and one Android phone. I am running genealogy s/w on this AWS host but rsearch from the laptop. I want to be able to easily move downloaded images into the Media area of the genealogy s/w, which can be under a Dropbox directory.

I still don't understand how software running on an AWS server knows what link to generate for me to use on a laptop at home to allow connection to the Dropbox server. All it has to go on is possibly the IP address of the ssh login and the fact that that IP is used to access that Dropbox account.

I don't have a 'browser window representing the remote display'. It's just an xterm window on the laptop desktop. So no status icon.

Thanks for persevering with this.

David

Hi DavidLedger,

---

DavidLedger wrote:

Submitted this yesterday but it was rejected because of an 'HTML error' which has been removed. Something in this must be seen as HTLM and so missing when you get it.

---

Yes, that's something usual. Sometimes seen as a HTML, sometimes seen as a Spam - one of the forum bugs.

---

DavidLedger wrote:
...

The reason Dropbox cannot open the default web browser is that there isn't one. It's a headless server accessed via an xterm over ssh. I'm not running on a GUI session, just an xterm shell session on the remote server displaying back to my Ubuntu laptop. Dropbox may 'think' I'm using a GUI session, but I'm not. ...

---

Ok... If you say so. My comments are based on your description, nothing more. Just one clarification here: even headless server can have installed web browser and could participate in GUI session! Be careful, don't make conclusion: because my server is headless, then GUI isn't possible; that's not true, X-session could be remote - i.e. your AWS session could use your local X-server (real or emulated)! Of course, I don't state it's so. To make clearer, what the session type is, post the result from:

lsb_release -d; echo "Shell: $SHELL"; echo "Display: $DISPLAY"; echo "User: $USER"; echo "Home: $HOME"; echo "Installed: $(dpkg -s dropbox | grep Package)"; ps -C dropbox

---

DavidLedger wrote:

... Trying the 'dropbox start -i' you suggested gives me:

 

david@ivdweb:/home/bitnami$ dropbox start -i
Starting Dropbox...dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-WYMNgP
...
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
Dropbox isn't running!
Done!
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtDBus.cpython-37m-x86_64-linux-gnu.so'

david@ivdweb:/home/bitnami$

....

---

That's exactly what has to be! From that moment on, your Dropbox is running. Don't be confused from: "Dropbox isn't running!"; that means it's not running to that moment. The next "Done!" shows everything is Ok. 🙂

About your plan - seems I misunderstood "one false start because URL suggestion replaced with previous version". Anyway... doesn't matter.

About "how software running on an AWS server knows what link to generate for me"... I don't know what else can say. You can take a look, for some more info, here or if you want to know more in deep, take a look here.

The Dropbox folder on the remote server hasn't updated since 21st March even though six items were knowingly added on the 23rd and one today. 'dropbox status' still says it isn't running, and the process shown in .dropbox/dropbox.pid doesn't exist.

There is no conventional browser installed on the server, just wget and curl, and the dropbox app itself in that it makes HTTP calls to the Dropbox servers (according to that OAuth page). AWS Linux servers are just virtual machines with a base Linux installation. If you want a browser you have to install one, and I haven't.

My point about the authentication/authorisation is that I haven't claimed to be anybody on the server.

Thanks again

David

Ok, the clarifications, you just made, are important. You haven't mentioned anything about the commands result. I gonna expand them little-bit:

dropbox start
lsb_release -d; echo "Shell: $SHELL"; echo "Display: $DISPLAY"; echo "User: $USER"; echo "Home: $HOME"; echo "Installed: $(dpkg -s dropbox | grep Package)"; cat ~/.dropbox/dropbox.pid; echo; ps -C dropbox; dropbox status; dropbox filestatus ~/Dropbox

Execute the two lines in sequence. What is the result?

david@ivdweb:18$: lsb_release -d; echo "Shell: $SHELL"; echo "Display: $DISPLAY"; echo "User: $USER"; echo "Home: $HOME"; echo "Installed: $(dpkg -s dropbox | grep Package)"; ps -C dropbox
Description: Ubuntu 16.04.6 LTS
Shell: /bin/bash
Display: localhost:10.0
User: david
Home: /home/david
Installed: Package: dropbox
PID TTY TIME CMD
david@ivdweb:19$:

I might get confused again. Where you launch that on? Again we are talking for AWS, not your local machine. Am I right? What's the result from my "expanded" variant (launched on the AWS!)?

Created shell script on the AWS server, while connected to it from an xterm on the Ubuntu laptop via ssh.

david@ivdweb:11$: cat bin/droptest
#!/bin/bash
# @(#) test Dropbox on AWS Lightsail Linux

dropbox start
lsb_release -d; echo "Shell: $SHELL"; echo "Display: $DISPLAY"; echo "User: $USER"; echo "Home: $HOME"; echo "Installed: $(dpkg -s dropbox | grep Package)"; cat ~/.dropbox/dropbox.pid; echo; ps -C dropbox; dropbox status; dropbox filestatus ~/Dropbox
pid="$(cat .dropbox/dropbox.pid)"
while ps -fp $pid; do sleep 1; done

Ran it on the AWS server, connected from an xterm on the Ubuntu laptop via ssh.

and got:

david@ivdweb:10$: droptest
Starting Dropbox...dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-gTnSE0
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/dropbox'
dropbox: setting python path '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273:/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtNetwork.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
Dropbox isn't running!
Done!
dropbox: load fq extension '/home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/PyQt5.QtDBus.cpython-37m-x86_64-linux-gnu.so'
Description: Ubuntu 16.04.6 LTS
Shell: /bin/bash
Display: localhost:10.0
User: david
Home: /home/david
Installed: Package: dropbox
30309
PID TTY TIME CMD
30309 ? 00:00:03 dropbox
Dropbox isn't running!

Dropbox isn't running!
UID PID PPID C STIME TTY TIME CMD
david 30309 1 77 12:19 ? 00:00:03 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 61 12:19 ? 00:00:03 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 52 12:19 ? 00:00:03 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 47 12:19 ? 00:00:03 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 51 12:19 ? 00:00:04 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 56 12:19 ? 00:00:05 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 60 12:19 ? 00:00:06 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 55 12:19 ? 00:00:06 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 51 12:19 ? 00:00:06 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 53 12:19 ? 00:00:06 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 54 12:19 ? 00:00:07 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 56 12:19 ? 00:00:08 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 57 12:19 ? 00:00:09 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 55 12:19 ? 00:00:10 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 56 12:19 ? 00:00:10 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 47 12:19 ? 00:00:10 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 44 12:19 ? 00:00:11 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david 30309 1 41 12:19 ? 00:00:11 /home/bitnami/.dropbox-dist/dropbox-lnx.x86_64-93.4.273/
UID PID PPID C STIME TTY TIME CMD
david@ivdweb:11$:

That's 18 x 1 second loops before the process dies. Sometimes more, sometimes less. The file entries added recently on the laptop have not arrived at the AWS server.

The only things that I have done on the local laptop are (i) visit the URL specified during the Dropbox install on the AWS server. (ii) start xterms and ssh into the AWS server. (iii) take part in this discussion.

Thanks,

David

Hi DavidLedger,

One last test, just to confirm my suspicions. 🙂 What is the result from:

ls -l1 ~/.dropbox-*

🤔