Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Useful message for watch ENOSPC error #239

Closed
remy opened this issue Dec 30, 2013 · 5 comments
Closed

Useful message for watch ENOSPC error #239

remy opened this issue Dec 30, 2013 · 5 comments
Labels
stale no activity for 2 weeks

Comments

@remy
Copy link
Owner

remy commented Dec 30, 2013

Instead of exception, point users to increasing max_user_watches. Ref #214.

@ondrejsika
Copy link

enlage numbers of watchers

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

@dileephell
Copy link

dileep@dileep-VirtualBox:~/tmp/rest$ nodemon server.js
28 Jan 15:22:13 - [nodemon] v0.7.10
28 Jan 15:22:13 - [nodemon] to restart at any time, enter rs
28 Jan 15:22:13 - [nodemon] watching: /home/dileep/tmp/rest
28 Jan 15:22:13 - [nodemon] exception in nodemon killing node
Error: watch ENOSPC
at errnoException (fs.js:1019:11)
at FSWatcher.start (fs.js:1051:11)
at Object.fs.watch (fs.js:1076:11)
at Object.watchFileChecker.check (/usr/lib/node_modules/nodemon/nodemon.js:160:6)
at ready (/usr/lib/node_modules/nodemon/nodemon.js:49:22)
at /usr/lib/node_modules/nodemon/nodemon.js:63:11
at ChildProcess.exithandler (child_process.js:641:7)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:735:16)
at Socket. (child_process.js:948:11)

i am not able to sort it out? also go throught that above query??? nothing happens???

@remy
Copy link
Owner Author

remy commented Jan 28, 2014

@dileephell can you upgrade to 1.0.x first? The command that @ondrejsika posted should allow for more watchers, but won't echo anything once it's run.

@dileephell
Copy link

@remy :upgradation works !!!

@stale
Copy link

stale bot commented Dec 5, 2017

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3

@stale stale bot added the stale no activity for 2 weeks label Dec 5, 2017
@stale stale bot closed this as completed Dec 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale no activity for 2 weeks
Projects
None yet
Development

No branches or pull requests

3 participants