September
2nd,
2015
Some of you may run into problem when your server keeps trowing error at you that dont make of sense, example
watch ENOSPC
Error: watch ENOSPC
at errnoException (fs.js:1024:11)
at FSWatcher.start (fs.js:1056:11)
at Object.fs.watch (fs.js:1081:11)
at Watcher.watchdir ([MY-PATH]/ember-cli/node_modules/broccoli-sane-watcher/node_modules/sane/index.js:184:20)
at new Watcher ([MY-PATH]/ember-cli/node_modules/broccoli-sane-watcher/node_modules/sane/index.js:63:10)
at EventEmitter.Watcher_addWatchDir [as addWatchDir] [MY-PATH]/ember-cli/node_modules/broccoli-sane-watcher/index.js:65:17)
at [MY-PATH]/ember-cli/node_modules/broccoli/lib/builder.js:66:35
at tryCatch ([MY-PATH]/ember-cli/node_modules/rsvp/dist/commonjs/rsvp/-internal.js:163:16)
at invokeCallback ([MY-PATH]/ember-cli/node_modules/rsvp/dist/commonjs/rsvp/-internal.js:172:17)
at [MY-PATH]/ember-cli/node_modules/rsvp/dist/commonjs/rsvp/promise.js:186:17
at flush ([MY-PATH]/ember-cli/node_modules/rsvp/dist/commonjs/rsvp/asap.js:51:9)
at process._tickCallback (node.js:419:13)
This may happen in two cases if you already using port your server running, or if your config has less watchers then its required for a project in that case command
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
will do the trick.