Error when running watchman

See original GitHub issue
npm start

> PropertyFinder@0.0.1 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.

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Reactions:2
  • Comments:22 (2 by maintainers)

github_iconTop GitHub Comments

162reactions
orencommented, Oct 5, 2015
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.

4reactions
AndreiCalazanscommented, Jun 11, 2017

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error when running watchman - react native - Stack Overflow
Run following command on Terminal in project directory ... i faced the same problem even after reinstalling watchman using homebrew: after ...
Read more >
Troubleshooting | Watchman - Meta Open Source
The warning will stick until you cancel the watch and reinstate it, or restart the watchman process. The simplest resolution is to run...
Read more >
watchman crawl failed | The AI Search Engine You Control
Retrying once with node crawler. Usually this happens when watchman isn't running. Create an empty `.watchmanconfig` file ...
Read more >
How To Fix Annoying WATCHMAN.EXE Errors [SOLVED]
Following these instructions carefully should resolve your WATCHMAN.EXE error, but we recommend running a brief check. Test the outcome of your replaced ...
Read more >
Error when installing Watchman on Ubuntu 20.04
Simply install the same watchman 4.9.0 package from official repository by using below commands (and maybe consult with official guide):
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found