You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MacOS Sierra Error with EMFILE upon NPM start #10028
I have the same error.
I just upgraded to macOS Sierra too
➜ example npm start
> example@0.0.1 start /Users/alex/Developer/example
> node node_modules/react-native/local-cli/cli.js start
Scanning 581 folders for symlinks in /Users/alex/Developer/example/node_modules (6ms)
┌────────────────────────────────────────────────────────────────────────────┐
│ 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
/Users/alex/Developer/example
[1:56:23 PM] <START> Building Dependency Graph
[1:56:23 PM] <START> Crawling File System
[Hot Module Replacement] Server listening on /hot
React packager ready.
2016-09-21 13:56 node[15435] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 13:56 node[15435] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 13:56 node[15435] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 13:56 node[15435] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
ERROR Error watching file for changes: EMFILE
{"code":"EMFILE","errno":"EMFILE","syscall":"Error watching file for changes:","filename":null}
Error: Error watching file for changes: EMFILE
at exports._errnoException (util.js:1026:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1406:11)
See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.
npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v6.4.0
npm ERR! npm v3.10.3
npm ERR! code ELIFECYCLE
npm ERR! example@0.0.1 start: `node node_modules/react-native/local-cli/cli.js start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the example@0.0.1 start script 'node node_modules/react-native/local-cli/cli.js start'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the example package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node node_modules/react-native/local-cli/cli.js start
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs example
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls example
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/alex/Developer/example/npm-debug.log
Reacted by Luis Fernando Rocha, efistokl and Emiel Masyn
Reacted by Adam K Dean, aSnailNEO, Erlend Halvorsen, JyotirmayS, Eliseu Codinhoto, Pedro Solá, Alex Sadleir, Artem Sapegin, shaun, Rahul Bhanushali and 47 more
This answer(#9309) work to me. I create and eidt new sysctl.conf and install watchman through homebrew.
1. increase max file limt
# check open file limit
sysctl kern.maxfiles
# edit sysctl
sudo vim /etc/sysctl.conf
# add these two lines
kern.maxfiles=10485760
kern.maxfilesperproc=1048576
# reboot
sudo reboot
# check new file limit
sysctl kern.maxfiles
2. upgrade to watchman 4.6
# clone repo
git clone https://github.com/facebook/watchman.git
# change to master branch
git checkout -b v4.6.0 v4.6.0
# run compiler
./autogen.sh
./configure --enable-lenient --without-pcre --with-python
make
sudo make install
# check watchman version
watchman -v
# result should be 4.6.0
Reacted by Nick Hagianis, Wang Guan, David C, xiaoyi, Adam Oliver, Max Kokorin, Kelsey, ccm, Maksym Mosiura, jmuchaxo and 1 more
I'd like to add that I've been running the packager without watchman for 3-4 months because React Native's Node packager doesn't depend on watchman. However, after upgrading to macOS Sierra the Node packager started failing with the above errors. Installing the current version of watchman (brew install watchman) did solve the issue for me, but something obviously regressed and it would be good to understand what that is.
Reacted by Magnus Solheim Thrap, Joshua Raichur, Miguel Oller, Chen Hong, nic, Joshua Pinter, manvi, Chris Scott, Xwartz, Aleksey Kulikov and 98 more
Reacted by Adam K Dean, ccm, Igor G., Wojciech Bilicki, Vasubabu Jinagam, Dawson Botsford, Theophilus Omoregbee and Eugene
Reacted by nic, Chris Scott, Palo Otcenas, ccm, James D Stewart, Emmanuel Isaac, Dennis Brotzky, Peter, Mauricio Poppe, Wojciech Bilicki and 5 more
Reacted by Dawson Botsford, Eugene and Kevin Zeidler
@Luavis still didn't work, when I execute ./autogen.sh
./autogen.sh: line 9: aclocal: command not found
./autogen.sh: line 10: autoheader: command not found
./autogen.sh: line 11: automake: command not found
./autogen.sh: line 12: autoconf: command not found
I reinstall node, watchman, npm and etc, finally everything goes fine!
I think new updates about supporting mac OS Sierra were included in the package. brew install node brew install watchman brew link automake pcre npm install -g react-native-cli export ANDROID_HOME=~/Library/Android/sdk export PATH=${PATH}:${ANDROID_HOME} react-native run-android
Reacted by Rene Marcelo
Reacted by Mike, Luavis, Johannes Klose, Savannah Whelan, Chitranshu Asthana, Serhii and Rene Marcelo
brew install watchman solved it for me but had to update xcode to 8.1 also in order to install watchman.
Reacted by László Király, Ho-Ling Poon, Ralph, Chris Mark, Matt Butler , Johannes Klose, Mattias Petter Johansson, Jared Goertzen, Kevin Habich, Liron Yahdav and 24 more
If you are still getting this error and are using tmux on MacOS Sierra, try open a new terminal without tmux and run 'watchman version'. After doing that, it was fixed for me within tmux.
Reacted by John Granata, Wang Guan and Arthur Ouaki
Hello. I have tried everything listed above, but I continue to get this error: node[10626] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
I just upgraded to High Sierra. I had deleted XCode and Android Studio, and then reinstalled both.
I've installed watchman 4.9.0 (and also uninstalled) - no help.
I've increased the max file limit - no help.
I've reinstalled react-native and npm - no help.
This is a correct way of increasing limit on max files for Mac OS X Sierra and above https://superuser.com/a/1171028, works for me on a huge repo w/o any issues (and doesn't in case of default limits)
Thank you @pranky. I tried reinstalling watchman and just about everything else I could think of, to no avail. The thing that worked was to create a new project and port the code into that project - so I guess there was something cached in the old project that I wasn't able to find.
Activity
AlexisLeon commentedon Sep 21, 2016
I have the same error.
I just upgraded to macOS Sierra too
Etheryte commentedon Sep 21, 2016
Have you checked the solutions in #9309?
mrkhan2 commentedon Sep 21, 2016
@Etheryte yes checked it out. Seems to only be a solution for those with brew/watchman installed.
leecade commentedon Sep 22, 2016
resolved via: leecade/react-native-practice#21
oscardemoya commentedon Sep 22, 2016
I was checking watchman issues and found out this one: facebook/watchman#358
When running
watchman watch-listI got some permissions error.chmod 0700 /usr/local/var/run/watchman/<USER>-stateworked for me.AlexisLeon commentedon Sep 24, 2016
The problem can be solved by reinstalling react-native-cli:
raichur commentedon Sep 24, 2016
@AlexisLeon that didn't work for me.
Luavis commentedon Sep 27, 2016
This answer(#9309) work to me. I create and eidt new
sysctl.confand install watchman through homebrew.1. increase max file limt
2. upgrade to watchman 4.6
gnestor commentedon Sep 27, 2016
I'd like to add that I've been running the packager without watchman for 3-4 months because React Native's Node packager doesn't depend on watchman. However, after upgrading to macOS Sierra the Node packager started failing with the above errors. Installing the current version of watchman (
brew install watchman) did solve the issue for me, but something obviously regressed and it would be good to understand what that is.bbb324 commentedon Sep 30, 2016
@Luavis still didn't work, when I execute ./autogen.sh
Luavis commentedon Oct 2, 2016
@bbb324 Could you try install watchman by homebrew
sanqianpiao commentedon Oct 28, 2016
Thanks to @Luavis , I followed his steps, still resulted in failure.
In my case, need another operation that mentioned below:
#910 (comment)
mikeyang01 commentedon Nov 7, 2016
I reinstall node, watchman, npm and etc, finally everything goes fine!
I think new updates about supporting mac OS Sierra were included in the package.
brew install nodebrew install watchmanbrew link automake pcrenpm install -g react-native-cliexport ANDROID_HOME=~/Library/Android/sdkexport PATH=${PATH}:${ANDROID_HOME}react-native run-androidankitduseja commentedon Nov 11, 2016
brew install watchmansolved it for me but had to update xcode to 8.1 also in order to install watchman.4 remaining items
mg commentedon Dec 17, 2016
If you are still getting this error and are using tmux on MacOS Sierra, try open a new terminal without tmux and run 'watchman version'. After doing that, it was fixed for me within tmux.
levarberry commentedon Feb 26, 2017
Installing watchman worked for me.
manuelprojects commentedon May 6, 2017
Same, installed watchman fixed the issue
manbearshark commentedon Jun 29, 2017
This just happened to me after transferring my environment from an old MacBook Pro to a brand new one.
Using Watchman 4.7.0 and brew - problem seems to be a permissions issue with the watchman state directory, so running:
chmod 0700 /usr/local/var/run/watchman/<YOUR USERNAME HERE>-statedid the job.
sandip7484 commentedon Aug 21, 2017
@Luavis i install watchman by homebrew thanks!!
AnshuGoyal commentedon Sep 5, 2017
Clearing the builds in android->app->build folder and hitting react-native run-android worked for me.
johnwangel commentedon Oct 10, 2017
Hello. I have tried everything listed above, but I continue to get this error: node[10626] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
I just upgraded to High Sierra. I had deleted XCode and Android Studio, and then reinstalled both.
I've installed watchman 4.9.0 (and also uninstalled) - no help.
I've increased the max file limit - no help.
I've reinstalled react-native and npm - no help.
Any other ideas what I can do.
Thank you,
John
viatsko commentedon Oct 10, 2017
This is a correct way of increasing limit on max files for Mac OS X Sierra and above https://superuser.com/a/1171028, works for me on a huge repo w/o any issues (and doesn't in case of default limits)
viatsko commentedon Oct 10, 2017
Actually, what if react-native/nuclide will provide instructions on how to raise limit instead of throwing an error?
prancky commentedon Oct 14, 2017
@johnwangel this will help you to fix that error https://facebook.github.io/watchman/docs/install.html
johnwangel commentedon Oct 14, 2017
Thank you @pranky. I tried reinstalling watchman and just about everything else I could think of, to no avail. The thing that worked was to create a new project and port the code into that project - so I guess there was something cached in the old project that I wasn't able to find.
Premjeet-Singh commentedon Dec 7, 2017
brew install watchmanworked for me.gramster commentedon Feb 17, 2018
Increasing file limits, installing watchman and reinstalling react-native-cli did not fix this for me. Why is this issue closed?