The user limit on the total number of inotify watches was reached #163

oren · 2015-10-05T00:15:35Z

System info

cat /etc/lsb-release
DISTRIB_DESCRIPTION="Ubuntu 15.04"

uname -a
Linux oren 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

lscpu | grep "Model name"
Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz

free -h
total       used       free     shared    buffers     cached
Mem:          7.5G       5.7G       1.8G       168M       1.0G       3.0G
-/+ buffers/cache:       1.7G       5.8G
Swap:         7.7G         0B       7.7G

Install watchman

sudo apt-get install automake python-dev
git clone https://github.com/facebook/watchman.git
cd watchman
git checkout v3.7.0
./autogen.sh
./configure
make
sudo make install

Create hello world react-native (here is the git repo)

react-native init hello
cd hello
npm start

output

> hello@0.0.1 start /home/oren/projects/react-native/hello
> node_modules/react-native/packager/packager.sh

 ┌────────────────────────────────────────────────────────────────────────────┐
 │  Running packager on port 8081.                                            │
 │                                                                            │
 │  Keep this packager running while developing on any JS projects. Feel      │
 │  free to close this tab and run your own packager instance if you          │
 │  prefer.                                                                   │
 │                                                                            │
 │  https://github.com/facebook/react-native                                  │
 │                                                                            │
 └────────────────────────────────────────────────────────────────────────────┘
Looking for JS files in
   /home/oren/projects/react-native/hello


React packager ready.

 ERROR  A non-recoverable condition has triggered.  Watchman needs your help!
The triggering condition was at timestamp=1444001279: inotify-add-watch(/home/oren/projects/react-native/HackerNews-React-Native/node_modules/react-native/node_modules/yeoman-generator/node_modules/download/node_modules/caw/node_modules/get-proxy/node_modules/rc/node_modules/.bin) -> The user limit on the total number of inotify watches was reached; increase the fs.inotify.max_user_watches sysctl
All requests will continue to fail with this message until you resolve
the underlying problem.  You will find more information on fixing this at
https://facebook.github.io/watchman/docs/troubleshooting.html#poison-inotify-add-watch

{"watchmanResponse":{"version":"3.7.0","error":"A non-recoverable condition has triggered.  Watchman needs your help!\nThe triggering condition was at timestamp=1444001279: inotify-add-watch(/home/oren/projects/react-native/HackerNews-React-Native/node_modules/react-native/node_modules/yeoman-generator/node_modules/download/node_modules/caw/node_modules/get-proxy/node_modules/rc/node_modules/.bin) -> The user limit on the total number of inotify watches was reached; increase the fs.inotify.max_user_watches sysctl\nAll requests will continue to fail with this message until you resolve\nthe underlying problem.  You will find more information on fixing this at\nhttps://facebook.github.io/watchman/docs/troubleshooting.html#poison-inotify-add-watch\n"}}
Error: A non-recoverable condition has triggered.  Watchman needs your help!
The triggering condition was at timestamp=1444001279: inotify-add-watch(/home/oren/projects/react-native/HackerNews-React-Native/node_modules/react-native/node_modules/yeoman-generator/node_modules/download/node_modules/caw/node_modules/get-proxy/node_modules/rc/node_modules/.bin) -> The user limit on the total number of inotify watches was reached; increase the fs.inotify.max_user_watches sysctl
All requests will continue to fail with this message until you resolve
the underlying problem.  You will find more information on fixing this at
https://facebook.github.io/watchman/docs/troubleshooting.html#poison-inotify-add-watch

    at ChildProcess.<anonymous> (/home/oren/projects/react-native/hello/node_modules/react-native/node_modules/sane/node_modules/fb-watchman/index.js:202:17)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at maybeClose (internal/child_process.js:817:16)
    at Socket.<anonymous> (internal/child_process.js:319:11)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at Pipe._onclose (net.js:469:12)

I Increased max_user_watches, max_queued_events, and max_user_instances

echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_watches
echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_queued_events
echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_instances

But I still get the same error. Any ideas?

The text was updated successfully, but these errors were encountered:

wez · 2015-10-05T02:13:22Z

After increasing the limits, you need to run watchman shutdown-server as the poison state is sticky.
https://facebook.github.io/watchman/docs/troubleshooting.html#i-39-ve-changed-my-limits-how-can-i-clear-the-error

oren · 2015-10-05T04:14:36Z

👍

gabouh · 2015-12-14T21:45:08Z

echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_watches && echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_queued_events && echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_instances && watchman shutdown-server
:)

yottanami · 2015-12-16T12:24:33Z

Why do I need to change the these parameters everytime?

ssomnoremac · 2015-12-16T15:59:44Z

Just want to add this was still an issue (after everything above) when running

sudo npm start

better to chown any files that are su owned. In my case .babel.json

wez · 2015-12-16T16:11:29Z

@yottanami every time you reboot? You need to persist your configuration for sysctl in /etc/sysctl.conf; take a look at man 8 sysctl

eladcandroid · 2016-06-06T09:10:57Z

@wez I didn't understand what to do to save the state also after reboot

wez · 2016-06-06T18:10:22Z

@eladcandroid It is usually managed by /etc/sysctl.conf but it may depend on your linux distribution. You should google for something like "ubuntu sysctl save" if you're using ubuntu.

eladcandroid · 2016-06-07T12:23:05Z

@wez Thanks. Now I've found it:
https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers

Here is the full command that sets a high limit and makes it permanent:

echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_watches && echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_queued_events && echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_instances && watchman shutdown-server && sudo sysctl -p

adeelibr · 2016-09-05T06:21:55Z

thankyou @eladcandroid this fixed my problem

yottanami · 2016-09-15T15:55:32Z

It can be useful

https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers

tundeojediran · 2016-10-28T22:35:38Z

Problem fixed. Thank you @eladcandroid

victoriastuart · 2017-02-23T17:49:27Z

Arch Linux:

"... The user limit on the total number of inotify watches was reached; increase the fs.inotify.max_user_watches sysctl ..."
Change to 10,000,000:

sudo echo 10000000 | sudo tee /proc/sys/fs/inotify/max_user_watches

longhorn09 · 2017-06-08T15:58:22Z

I tried a number of suggestions in this thread which worked temporarily, but the changes didn't persist after reboot.
One technique that worked for me is appending to /etc/sysctl.conf. I run Ubuntu 16.04.

fs.inotify.max_user_watches = 999999
fs.inotify.max_queued_events = 999999
fs.inotify.max_user_instances = 999999

You can also view the values using
sudo sysctl fs.inotify.max_user_watches fs.inotify.max_queued_events fs.inotify.max_user_instances

victoriastuart · 2017-06-08T16:30:09Z

Hi! You can add this to cron/crontab, as shown further below:

Install inotify [Arch Linux]:

sudo pacman -Syu
sudo pacman -S inotify-tools

Issue: Krusader (file manager) views were not auto-refreshing

cat /proc/sys/fs/inotify/max_user_watches
8192

echo 100000000 | sudo tee /proc/sys/fs/inotify/max_user_watches ## 100,000,000
100000000

cat /proc/sys/fs/inotify/max_user_watches
100000000

Added as entry (every minute) in crontab:

# m h dom mon dow user nice command

# "At every minute" [http://crontab.guru/]:
* * * * * root nice -n 19 sudo echo 100000000 | sudo tee /proc/sys/fs/inotify/max_user_watches

# 100000000 : 100,000,000
# verify: cat /proc/sys/fs/inotify/max_user_watches

jandiralceu · 2018-03-18T00:20:29Z

Solve my problem! thanks @longhorn09 !!!!!

schmitt-kevin · 2018-03-23T12:56:34Z

just a simple

sudo sysctl -p

cmd worked for me

cpmech · 2018-09-21T01:56:15Z

@wez Thanks. Now I've found it:
https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers

Here is the full command that sets a high limit and makes it permanent:

echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_watches && echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_queued_events && echo 999999 | sudo tee -a /proc/sys/fs/inotify/max_user_instances && watchman shutdown-server && sudo sysctl -p

I just don't need watchman shutdown-server. It is not available on Ubtuntu 18.04..

barretogustavo · 2022-10-27T13:58:55Z

Thanks eladcandroid ! Solve my problem.

oren mentioned this issue Oct 5, 2015

Error when running watchman facebook/react-native#3199

Closed

oren closed this as completed Oct 5, 2015

taras mentioned this issue Nov 10, 2017

Increase the amount of inotify watchers thisdot/enterprise-ui-dev-box#3

Open

ide mentioned this issue Feb 5, 2018

Android Build Fails, Execution failed for task ':app:exponentPrebuildStep' (fixed by increasing inotify limit) expo/expo#1369

Closed

iqqmuT mentioned this issue Dec 27, 2018

Use archlinux/base as parent image farwayer/docker-react-native#4

Open

murtraja mentioned this issue Jul 15, 2019

"Loading dependency graph, done." Stuck facebook/react-native#25650

Closed

urgent mentioned this issue Jul 20, 2020

Init leads urgent/thisbounty.com-events#24

Closed

5 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

The user limit on the total number of inotify watches was reached #163

The user limit on the total number of inotify watches was reached #163

oren commented Oct 5, 2015

wez commented Oct 5, 2015

oren commented Oct 5, 2015

gabouh commented Dec 14, 2015

yottanami commented Dec 16, 2015

ssomnoremac commented Dec 16, 2015

wez commented Dec 16, 2015

eladcandroid commented Jun 6, 2016

wez commented Jun 6, 2016

eladcandroid commented Jun 7, 2016

adeelibr commented Sep 5, 2016

yottanami commented Sep 15, 2016

tundeojediran commented Oct 28, 2016

victoriastuart commented Feb 23, 2017 •

edited

Loading

longhorn09 commented Jun 8, 2017 •

edited

Loading

victoriastuart commented Jun 8, 2017 •

edited

Loading

jandiralceu commented Mar 18, 2018

schmitt-kevin commented Mar 23, 2018 •

edited

Loading

cpmech commented Sep 21, 2018

barretogustavo commented Oct 27, 2022

The user limit on the total number of inotify watches was reached #163

The user limit on the total number of inotify watches was reached #163

Comments

oren commented Oct 5, 2015

wez commented Oct 5, 2015

oren commented Oct 5, 2015

gabouh commented Dec 14, 2015

yottanami commented Dec 16, 2015

ssomnoremac commented Dec 16, 2015

wez commented Dec 16, 2015

eladcandroid commented Jun 6, 2016

wez commented Jun 6, 2016

eladcandroid commented Jun 7, 2016

adeelibr commented Sep 5, 2016

yottanami commented Sep 15, 2016

tundeojediran commented Oct 28, 2016

victoriastuart commented Feb 23, 2017 • edited Loading

longhorn09 commented Jun 8, 2017 • edited Loading

victoriastuart commented Jun 8, 2017 • edited Loading

jandiralceu commented Mar 18, 2018

schmitt-kevin commented Mar 23, 2018 • edited Loading

sudo sysctl -p

cpmech commented Sep 21, 2018

barretogustavo commented Oct 27, 2022

victoriastuart commented Feb 23, 2017 •

edited

Loading

longhorn09 commented Jun 8, 2017 •

edited

Loading

victoriastuart commented Jun 8, 2017 •

edited

Loading

schmitt-kevin commented Mar 23, 2018 •

edited

Loading