[SOLVED] New user problem with Dropbox and sudo relating to "Can't monitor Dropbox folder" error.

globetrotterdk · 03-21-2018, 08:56 AM

I am trying to sort out a problem where starting Dropbox, I get the error Can't monitor Dropbox folder". I found out that I should check the following:

Code:

$ tail -f /var/log/syslog

which at the very bottom gives me the following:

Code:

Mar 21 14:22:47 darkstar Dropbox[6323]: Unable to monitor entire Dropbox folder hierarchy. Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p"

As a new user, I believe that Slackware frowns on the use of sudo. Should I add myself to the sudoers file to run this command?

BW-userx · 03-21-2018, 09:27 AM

when you established your dropbox install into a user account, did you use sudo or log into root then issue the command to set up a user account for dropbox? I ask because you mentioned sudo. unless you're holding back pertinent information on how you setup your account, which is not relevant to your question in this post. nevertheless, the steps to install and set up dropbox.

install dropbox via slackbuild

dropbox start i
or
dropboxd start i

if the first one does not work.

then let it download client login let Dropbox do its thing.
this is all done in a NON root privileged mode.

if you need to run a command with root privileges log into root then run them or put yourself in the wheel group. that is the group Slackware uses for sudo privileges, do not forget to check your sudoers file to ensure that one of the options for sudo is un-commented.

if it is still giving you an issue. in your user account rename your .dropbox ( for safe keeping ) then go through the setting up dropbox in that account again being sure you're not using root privileges to see if that fixes it.

loging in as root

Code:

su
root passwd
#

issue commands then use the exit command to leave root and go back to user. If everything then works out you can delete your old .dropbox directory that you renamed.

globetrotterdk · 03-21-2018, 10:11 AM

Quote:

Originally Posted by BW-userx

when you established your dropbox install into a user account, did you use sudo or log into root then issue the command to set up a user account for dropbox? I ask because you mentioned sudo. unless you're holding back pertinent information on how you setup your account, which is not relevant to your question in this post. nevertheless, the steps to install and set up dropbox.

Thanks for the reply. I installed Dropbox via SlackBuild, and when the install was completed, I chose Dropbox in the XFCE4 app menu under "Internet".

Quote:

Originally Posted by BW-userx

install dropbox via slackbuild

dropbox start i
or
dropboxd start i
(...)
if it is still giving you an issue. in your user account rename your .dropbox ( for safe keeping ) then go through the setting up dropbox in that account again being sure you're not using root privileges to see if that fixes it.

I renamed the .dropbox folder and then ran dropbox again.

Here is the output:

Code:

$$ dropbox start i
bash: dropbox: command not found
bash-4.3$ dropboxd start i
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-NaTrqk
dropbox: initializing
dropbox: running python 2.7.11
dropbox: setting program path '/opt/dropbox/dropbox-lnx.x86_64-42.4.114/dropbox'
dropbox: setting home path '/opt/dropbox/dropbox-lnx.x86_64-42.4.114'
dropbox: setting python path '/opt/dropbox/dropbox-lnx.x86_64-42.4.114:/opt/dropbox/dropbox-lnx.x86_64-42.4.114/python-packages-27.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-42.4.114/cryptography.hazmat.bindings._constant_time.so'
dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-42.4.114/cryptography.hazmat.bindings._openssl.so'
dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-42.4.114/cryptography.hazmat.bindings._padding.so'
dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-42.4.114/psutil._psutil_linux.so'
dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-42.4.114/psutil._psutil_posix.so'
dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-42.4.114/linuxffi.pthread._linuxffi_pthread.so'
dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-42.4.114/tornado.speedups.so'
dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-42.4.114/cpuid.compiled._cpuid.so'
dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-42.4.114/linuxffi.resolv.compiled._linuxffi_resolv.so'
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-EMJspn
dropbox: initializing
dropbox: initializing python 2.7.11
dropbox: setting program path '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/dropbox'
dropbox: setting home path '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92'
dropbox: setting python path '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92:/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/python-packages-27.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/cryptography.hazmat.bindings._constant_time.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/cryptography.hazmat.bindings._openssl.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/cryptography.hazmat.bindings._padding.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/psutil._psutil_linux.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/psutil._psutil_posix.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/linuxffi.pthread._linuxffi_pthread.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/tornado.speedups.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/cpuid.compiled._cpuid.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/linuxffi.resolv.compiled._linuxffi_resolv.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/posixffi.libc._posixffi_libc.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/librsyncffi.compiled._librsyncffi.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/linuxffi.sys.compiled._linuxffi_sys.so'
Killed
bash-4.3$ dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/PyQt5.QtWebKit.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/PyQt5.QtCore.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/PyQt5.QtNetwork.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/PyQt5.QtGui.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/PyQt5.QtWebKitWidgets.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/PyQt5.QtWidgets.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/PyQt5.QtPrintSupport.so'
dropbox: load fq extension '/home/username/.dropbox-dist/dropbox-lnx.x86_64-45.4.92/PyQt5.QtDBus.so'
[23552:23588:0321/155520.784082:ERROR:browser_gpu_channel_host_factory.cc(121)] Failed to launch GPU process.
Created new window in existing browser session.
[24028:24064:0321/155552.620669:ERROR:browser_gpu_channel_host_factory.cc(121)] Failed to launch GPU process.
Created new window in existing browser session.
Unable to monitor entire Dropbox folder hierarchy. Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem.
Unable to monitor entire Dropbox folder hierarchy. Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem.
Unable to monitor entire Dropbox folder hierarchy. Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem.
Unable to monitor entire Dropbox folder hierarchy. Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem.
Unable to monitor entire Dropbox folder hierarchy. Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem.
Unable to monitor entire Dropbox folder hierarchy. Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem.

"Created new window in existing browser session." is where I went into the Dropbox applet menu manually and chose to sign in, as I could see the browser_gpu_channel_etc error.

BW-userx · 03-21-2018, 10:53 AM

looks like it put you right back where you started,

Code:

echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p

I ran that,

Code:

userx@slackwhere101:~
$ echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p
fs.inotify.max_user_watches=100000
fs.inotify.max_user_watches = 100000

so try that next, and cross your fingers, you might have to logout and login, or stop dropbox and restart it.

command line: dropbox stop, dropbox start you'll see a lot of output in your terminal that is normal.

mralk3 · 03-21-2018, 02:51 PM

As a side note:

For sudo usage on Slackware: Make sure you use "sudo -i" when using sudo in Slackware. You can set up a bash alias for when you write sudo to always use sudo -i.
For su usage on Slackware: Make sure you use "su -" when using su in Slackware. You can use su -c "some command" as well if you only need to run one command or script as root.

I use "sudo -i" to execute slackpkg and sbopkg. I used to use "su -" for all of this but read somewhere that "sudo -i" is just fine. If you leave out the -i then a login shell will not be executed and this will cause problems on your Slackware system. If I am executing a SlackBuild script via sh (sh ./some.SlackBuild), I always use su -.

Maybe someone else can further expand on why this is the case. I cannot seem to find the document (or forum post?) I read discussing this.

globetrotterdk · 03-21-2018, 04:30 PM

Quote:

Originally Posted by BW-userx

so try that next, and cross your fingers, you might have to logout and login, or stop dropbox and restart it.

That seems to have done it. I have both logged out and restarted a couple of times. Thanks again

globetrotterdk · 03-21-2018, 04:35 PM

Quote:

Originally Posted by mralk3

As a side note:

For sudo usage on Slackware: Make sure you use "sudo -i" when using sudo in Slackware. You can set up a bash alias for when you write sudo to always use sudo -i.
For su usage on Slackware: Make sure you use "su -" when using su in Slackware. You can use su -c "some command" as well if you only need to run one command or script as root.

I use "sudo -i" to execute slackpkg and sbopkg. I used to use "su -" for all of this but read somewhere that "sudo -i" is just fine. If you leave out the -i then a login shell will not be executed and this will cause problems on your Slackware system. If I am executing a SlackBuild script via sh (sh ./some.SlackBuild), I always use su -.

Maybe someone else can further expand on why this is the case. I cannot seem to find the document (or forum post?) I read discussing this.

Thanks. I decided to play it safe and only added my user name for this one operation, and then removed it again from sudoers. I have also been looking around for some sudo documentation and was surprised not to find very much. Regarding "su", I have just been using "su", not "su -"...

mralk3 · 03-21-2018, 10:08 PM

You are going to want to start using "su -" because it launches a login shell that will source the proper shell environment. This is especially important during package installation and upgrades.

globetrotterdk · 03-22-2018, 05:44 AM

Quote:

Originally Posted by mralk3

You are going to want to start using "su -" because it launches a login shell that will source the proper shell environment. This is especially important during package installation and upgrades.

I have just been using "su" up to now for running sbopkg and slackpkg. Is that a problem?

BW-userx · 03-22-2018, 09:15 AM

I've never had any issues with it.

Code:

sudo ./some.slacBuild

or

Code:

sudo sboinstall <some program>