Error when running watchman

Question

When I run react-native start, I am getting the following message

Error: A non-recoverable condition has triggered. Watchman needs your help! The triggering condition was at timestamp=1489123194: inotify-add-watch(/var/www/html/eventManager/android/app/src/main/res/mipmap-mdpi) -> 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> (/var/www/html/bookLister/node_modules/fb-watchman/index.js:207:21)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:852:16)
at Socket.<anonymous> (internal/child_process.js:323:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at Pipe._handle.close [as _onclose] (net.js:492:12)

are you running in device or emulator? – Nitesh Mishra Mar 10 '17 at 06:42 — Nitesh Mishra, Mar 10 '17 at 06:42
Check this answer given by me it can solve your problem. – Nitesh Mishra Mar 10 '17 at 06:43 — Nitesh Mishra, Mar 10 '17 at 06:43
http://stackoverflow.com/a/42627342/7604342 check this out – Nitesh Mishra Mar 10 '17 at 06:52 — Nitesh Mishra, Mar 10 '17 at 06:52

Geethu Jose · Accepted Answer · 2022-08-06T10:17:12.897

49

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
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf
sudo sysctl -p

watchman shutdown-server

This one helped

edited Aug 06 '22 at 10:17

answered Mar 10 '17 at 07:14

Geethu Jose

1,953
2
14
30

Happy to hear @DamianLattenero – Geethu Jose Aug 14 '18 at 05:40
Thanks, it helped. – Shahrukh Anwar Oct 30 '18 at 10:37
It worked for me as well. But I need to enter these commands every time I reset my computer. Is there any permanent way to do it? – JollyRoger Oct 26 '19 at 13:13
1

@JollyRoger The answer by mad_greasemonkey here will solve the problem permanently. I tried on my computer and next time when I start computer the error doesn't occur. – Debanjan Dey Jul 20 '20 at 15:29
Thanks for this post. It helps me but each time I reboot my system I should run these lines! What should I do for solve this for ever on my system?! – ermi Nov 23 '21 at 08:21

Syed Zain Ali · Answer 2 · 2019-01-26T10:40:31.930

Just run these commands in terminal:

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

Other Way make Script in package.json

"scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest",
    "flow": "flow",
    "flow-stop": "flow stop",
    "watch-need-help": "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"
  },

Run following command on Terminal in project directory

npm run watch-need-help

score 6 · Answer 3 · answered Dec 07 '21 at 00:18

6

It works for me

watchman watch-del-all
watchman shutdown-server

Here is link which I follow.

answered Dec 07 '21 at 00:18

Sumj25

129
1
2

It worked for me, but add `watchman watch-project '[my project path]'` at the end. – Daniel Duarte Nov 24 '22 at 17:28

score 5 · Answer 4 · answered Jul 15 '19 at 04:38

5

Increase inotify limit to increase the limit on the number of files you can monitor.

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

Please go through this for more info

answered Jul 15 '19 at 04:38

mad_greasemonkey

864
2
15
32

score 3 · Answer 5 · answered May 23 '18 at 06:45

This One is Also Helpfull .

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

score 1 · Answer 6 · answered Jul 25 '17 at 17:16

1

updating

watchman

to latest(4.7.0) version helped me solve this problem.

answered Jul 25 '17 at 17:16

Jose Kj

2,912
2
28
40

Waqas Ali · Answer 7 · 2022-03-07T05:33:32.710

1

this one helped found it on github issues

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

https://github.com/facebook/watchman/issues/163 by @eladcandroid [1]

edited Mar 07 '22 at 05:33

answered Mar 01 '22 at 05:59

Waqas Ali

91
3

Rhibi Hamdi · Answer 8 · 2020-10-09T15:01:11.290

You can solve it by trying one of the below solutions:

first pass hit line of code in your terminal and test it :

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

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

otherwise perhaps the debugger page was left open from previous sessions. Closing the tab completely and then opening the debugger in a new tab solved the issue.

if none of the above solution doesn't work with you try to restart your PC

Prince Akoensi · Answer 9 · 2022-12-05T15:13:49.133

0

i faced the same problem even after reinstalling watchman using homebrew: after deleting the pid, log and sock files, the following steps worked for me:

touch pid && touch log && touch sock
watchman --foreground --logfile=/dev/stdout
Allowed accessibility permissions : sudo chmod 700 /usr/local -closed all terminals and re-runned my commands. That should help.

edited Dec 05 '22 at 15:13

answered Dec 04 '22 at 15:11

Prince Akoensi

1
1

Error when running watchman

9 Answers9

Linked