React-native: Error when running watchman

Created on 2 Oct 2015  ยท  22Comments  ยท  Source: facebook/react-native

npm start

> [email protected] start /home/oren/projects/react-native/ReactNative-PropertyFinder
> 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/ReactNative-PropertyFinder 


React packager ready.

[12:00:54] <START> Building Dependency Graph
[12:00:54] <START> Crawling File System
 ERROR  A non-recoverable condition has triggered.  Watchman needs your help!
The triggering condition was at timestamp=1443812455: inotify-add-watch(/home/oren/projects/react-native/ReactNative-PropertyFinder/node_modules/react-native/node_modules/module-deps/node_modules/detective/node_modules/escodegen/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=1443812455: inotify-add-watch(/home/oren/projects/react-native/ReactNative-PropertyFinder/node_modules/react-native/node_modules/module-deps/node_modules/detective/node_modules/escodegen/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=1443812455: inotify-add-watch(/home/oren/projects/react-native/ReactNative-PropertyFinder/node_modules/react-native/node_modules/module-deps/node_modules/detective/node_modules/escodegen/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/ReactNative-PropertyFinder/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 Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)

I tried echo 524288 | sudo tee -a /proc/sys/fs/inotify/max_user_watches but it didn't help.
i guess i'll have to spend the time here - https://facebook.github.io/watchman/docs/troubleshooting.html#poison-inotify-add-watch
btw, I am on ubuntu, not mac.

if anyone got a quick solution, please comment here.

Locked

Most helpful comment

echo 256 | sudo tee -a /proc/sys/fs/inotify/max_user_instances
echo 32768 | sudo tee -a /proc/sys/fs/inotify/max_queued_events
echo 65536 | sudo tee -a /proc/sys/fs/inotify/max_user_watches
watchman shutdown-server

the last command solved it.

All 22 comments

posted it on watchman's repo - https://github.com/facebook/watchman/issues/163

echo 256 | sudo tee -a /proc/sys/fs/inotify/max_user_instances
echo 32768 | sudo tee -a /proc/sys/fs/inotify/max_queued_events
echo 65536 | sudo tee -a /proc/sys/fs/inotify/max_user_watches
watchman shutdown-server

the last command solved it.

The same problem.Thanks for your sharing oren!

@oren It is work for me ,Thanks!

@oren Thanks!

Many Thanks! @oren

Thanks!! work for me :+1:

For Info: I Reboot my Mashine and now it works

Thanks...!!

Thanks @oren !

@oren dude I dont know how to thank you, but you are a genius!

Thank you @oren.

many thanks @oren

I tried orens way, got rid of the error, but then when i tried runnin the app, i got a scary red screen with "Could not get BatchedBridge, make sure your bundle is packaged correctly" written on it. Help

@dennisobel use "react-native start" in the root of your project and then (in other terminal) "react-native run-android" or "run-ios"

Thanks @oren

Thanks @oren

Does anyone have a permanent solution for this?,
I did use the following command and it works fine, but every time i restart my pc it resets the values.

I have tried editing the maximum queued file itself but i again it always resets.
I am running a Ubuntu 16.10.

Thanks @oren

Thank you @oren and @viviannysdiaz

Thanks @oren

@AndreiCalazans on Ubuntu 16.04 (not sure about 16.10) the value of fs.inotify.max_user_watches in /etc/sysctl.conf needs to be changed and then run watchman shutdown-server && sudo sysctl -p for a permanent fix.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

upbit picture upbit  ยท  3Comments

phongyewtong picture phongyewtong  ยท  3Comments

grabbou picture grabbou  ยท  3Comments

lazywei picture lazywei  ยท  3Comments

oney picture oney  ยท  3Comments