2016-03-22 17 views
9
version: 2.4.2 
Could not start watchman; falling back to NodeWatcher for file system events. 
Visit http://www.ember-cli.com/user-guide/#watchman for more info. 
File: /home/user/Documents/myApp/app 
The Broccoli Plugin: [object Object] failed with: 
Error: watch /home/user/Documents/myApp/app ENOSPC 
at exports._errnoException (util.js:870:11) 
at FSWatcher.start (fs.js:1234:19) 
at Object.fs.watch (fs.js:1262:11) 
at NodeWatcher.watchdir (/home/user/Documents/myApp/node_modules/ember-cli/node_modules/sane/src/node_watcher.js:144:20) 
at new NodeWatcher (/home/user/Documents/myApp/node_modules/ember-cli/node_modules/sane/src/node_watcher.js:45:8) 
at new sane (/home/user/Documents/myApp/node_modules/ember-cli/node_modules/sane/index.js:17:12) 
at EventEmitter.Watcher_addWatchDir [as addWatchDir] (/home/user/Documents/myApp/node_modules/ember-cli/node_modules/broccoli-sane-watcher/index.js:93:17) 
at /home/user/Documents/myApp/node_modules/ember-cli/node_modules/ember-cli-broccoli/lib/builder.js:95:35 
at lib$rsvp$$internal$$tryCatch (/home/user/Documents/myApp/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1036:16) 
at lib$rsvp$$internal$$invokeCallback (/home/user/Documents/myApp/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1048:17) 


The broccoli plugin was instantiated at: 
at WatchedDir.Directory (/home/user/Documents/myApp/node_modules/ember-cli/node_modules/broccoli-source/index.js:14:31) 
at new WatchedDir (/home/user/Documents/myApp/node_modules/ember-cli/node_modules/broccoli-source/index.js:58:13) 
at EmberApp._initOptions (/home/user/Documents/myApp/node_modules/ember-cli/lib/broccoli/ember-app.js:221:16) 
at new EmberApp (/home/user/Documents/myApp/node_modules/ember-cli/lib/broccoli/ember-app.js:93:8) 
at module.exports (/home/user/Documents/myApp/ember-cli-build.js:6:13) 
at Class.module.exports.Task.extend.setupBroccoliBuilder (/home/user/Documents/myApp/node_modules/ember-cli/lib/models/builder.js:55:19) 
at Class.module.exports.Task.extend.init (/home/user/Documents/myApp/node_modules/ember-cli/lib/models/builder.js:89:10) 
at new Class (/home/user/Documents/myApp/node_modules/ember-cli/node_modules/core-object/core-object.js:18:12) 
at Class.module.exports.Task.extend.run (/home/user/Documents/myApp/node_modules/ember-cli/lib/tasks/serve.js:15:19) 
at /home/user/Documents/myApp/node_modules/ember-cli/lib/commands/serve.js:70:22 
+0

próbowałeś ponownej instalacji komponentów Bower moduły węzła? –

+0

@ stijn.aerts, które nie będą działać, ponieważ jest to związane z stróżem –

Odpowiedz

17

Ten błąd jest

// installing watchman from source 
git clone https://github.com/facebook/watchman.git 
cd watchman 
./autogen.sh 
./configure 
make 
sudo make install 

pełne instrukcje dotyczące instalacji stróż z powodu inotify zegarków osiągnięciu maksymalnego limitu w systemie.

Aby sprawdzić maksymalną liczbę inotify zegarków:

cat /proc/sys/fs/inotify/max_user_watches

Aby ustawić max ilość inotify zegarki

Tymczasowo:

  • Run sudo sysctl fs.inotify.max_user_watches= z preferowanej wartości na koniec .

Trwale:

  • echo 878987 | sudo tee -a /proc/sys/fs/inotify/max_user_watches
+0

Co robi ustawienie fs.inotify.max_user_watches? – ashipj

+1

Czy istnieje jakiś ** bardziej trwały ** sposób? coś, co działa po restarcie? –