An error "Error: watch ENOSPC" #214

jamlfy · 2013-10-20T21:43:04Z

20 Oct 16:40:37 - [nodemon] v0.7.10
20 Oct 16:40:37 - [nodemon] to restart at any time, enter `rs`
20 Oct 16:40:37 - [nodemon] watching: /my/proyect/server
20 Oct 16:40:37 - [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.<anonymous> (child_process.js:948:11)
20 Oct 16:40:37 - [nodemon] reading ignore list
20 Oct 16:40:37 - [nodemon] exception in nodemon killing node
Error: watch ENOSPC
    at errnoException (fs.js:1019:11)
    at FSWatcher.start (fs.js:1051:11)
    at fs.watch (fs.js:1076:11)
    at checkTimer (/usr/lib/node_modules/nodemon/nodemon.js:467:27)
    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

remy · 2013-10-20T22:18:44Z

Version of Node?

remy · 2013-10-20T22:19:21Z

Also, can you provide a simple test case script you're using (to test with).

jamlfy · 2013-10-21T17:20:02Z

use Node 0.10.21. With any script, generates an error.

remy · 2013-10-27T13:12:53Z

Is this the same issue as #144? I can't replicate this on my mac (though I didn't ask what OS you had, but assumed *nix type based on the path in your paste above).

jamlfy · 2013-10-28T00:43:55Z

Not the same, are different here is running a single processo. In the other runs on multiple processo, non-cloud

davidbarton · 2013-11-11T16:52:05Z

Experienced this error today with multiple apps (express, restify).

NodeJS: v0.10.21
ElementaryOS Version: 0.2 "Luna" ( 64-bit )
Built on: Ubuntu 12.04 ( "Precise" )
Kernel 3.5.0-43-generic

11 Nov 17:32:38 - [nodemon] v0.7.10
11 Nov 17:32:38 - [nodemon] to restart at any time, enter `rs`
...
11 Nov 17:32:38 - [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 (/home/.../node_modules/nodemon/nodemon.js:160:6)
    at ready (/home/.../node_modules/nodemon/nodemon.js:49:22)
    at /home/.../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.<anonymous> (child_process.js:948:11)

reproduce:

npm install nodemon
./node_modules/.bin/nodemon app.js

app.js (from http://nodejs.org/)

var http = require('http');
http.createServer(function (req, res) {
  res.writeHead(200, {'Content-Type': 'text/plain'});
  res.end('Hello World\n');
}).listen(1337, '127.0.0.1');
console.log('Server running at http://127.0.0.1:1337/');

davidbarton · 2013-11-13T18:39:40Z

I got same error with CoffeeScript --watch ./node_modules/.bin/coffee --watch app/

/home/.../node_modules/coffee-script/lib/coffee-script/command.js:334
        throw e;
              ^
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 watchDir (/home/.../node_modules/coffee-script/lib/coffee-script/command.js:299:27)
    at /home/.../node_modules/coffee-script/lib/coffee-script/command.js:102:11
    at Object.oncomplete (fs.js:107:15)

chok · 2013-11-27T20:43:56Z

I got the same error with a compound.js project using coffeescript on Ubuntu 13.10 with node 0.10.21

$ nodemon server.coffee

27 Nov 21:40:14 - [nodemon] v0.7.10
27 Nov 21:40:14 - [nodemon] to restart at any time, enter `rs`
27 Nov 21:40:14 - [nodemon] watching: /home/chok/work/edf/bluetic/src
27 Nov 21:40:14 - [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/local/lib/node_modules/nodemon/nodemon.js:160:6)
    at ready (/usr/local/lib/node_modules/nodemon/nodemon.js:49:22)
    at /usr/local/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.<anonymous> (child_process.js:948:11)

remy · 2013-12-03T13:43:28Z

Can someone have a go at this with the dev version of nodemon? I've made a lot of changes and am trying to concentrate my efforts on making sure the new version gets all these issues closed.

You can install using npm install -g nodemon@dev

davidbarton · 2013-12-03T14:13:06Z

Works for me now dunno why. Using latest stable nodemon npm version. Also had same issue with coffeescript --watch and this works too now. No node update, just npm install modules and distro updates.

chok · 2013-12-03T14:34:30Z

I have the same error but the process stop :

$ nodemon server.coffee 
3 Dec 15:32:42 - [nodemon] v0.9.10
[nodemon] exception in nodemon killing node
[nodemon] 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 Function.check (/usr/local/lib/node_modules/nodemon/lib/config/watchable.js:34:6)
    at alternativeCheck (/usr/local/lib/node_modules/nodemon/lib/config/checkWatchSupport.js:18:15)
    at /usr/local/lib/node_modules/nodemon/lib/config/checkWatchSupport.js:36: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.<anonymous> (child_process.js:948:11)

remy · 2013-12-03T15:18:14Z

@chok can you run the following (and paste the result) for me in the same directory you're running nodemon:

find . | wc

I'm trying to get an idea what's actually causing this problem.

chok · 2013-12-03T15:29:20Z

Here is the result :

$ find . | wc
   7677    7677  542965

remy · 2013-12-03T15:55:44Z

Okay, that's 7600 files it's trying to bind watches too.

Can you run tree and put the result in http://pastie.org/ (only because it's going to be massive).

chok · 2013-12-03T18:10:56Z

Pastie said it's too large (more than 64kb) and after all I don't like the text at the bottom :p (All your pastes are belong to us. ). I removed some parts specific to my projects. By the way, most of files are, of course, located in node_modules.

You can find it on gist : https://gist.github.com/chok/7774318

remy · 2013-12-03T19:48:55Z

Okay, I think this is a problem entirely linked to the number of files being monitored (since you're having to bind to each individual file). I was thinking about ignoring node_modules and .git directories by default, but can you try doing it with the ignore command (assuming you're still running 0.9.x):

nodemon -i node_modules

Of course this shouldn't need to be done every time, I'm just trying to confirm this is the issue.

chok · 2013-12-03T19:53:54Z

It doesn't work :(

$ nodemon -i node_modules/ server.coffee 
3 Dec 20:52:32 - [nodemon] v0.9.10
[nodemon] exception in nodemon killing node
[nodemon] 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 Function.check (/usr/local/lib/node_modules/nodemon/lib/config/watchable.js:34:6)
    at alternativeCheck (/usr/local/lib/node_modules/nodemon/lib/config/checkWatchSupport.js:18:15)
    at /usr/local/lib/node_modules/nodemon/lib/config/checkWatchSupport.js:36: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.<anonymous> (child_process.js:948:11)

I also try :

$ nodemon -w app/* server.coffee 
3 Dec 20:53:32 - [nodemon] v0.9.10
[nodemon] exception in nodemon killing node
[nodemon] 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 Function.check (/usr/local/lib/node_modules/nodemon/lib/config/watchable.js:34:6)
    at alternativeCheck (/usr/local/lib/node_modules/nodemon/lib/config/checkWatchSupport.js:18:15)
    at /usr/local/lib/node_modules/nodemon/lib/config/checkWatchSupport.js:36: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.<anonymous> (child_process.js:948:11)

remy · 2013-12-03T20:02:57Z

Can you run the exact same command, but add --dump and send me the response (when you're doing the ignore version).

chok · 2013-12-03T20:19:51Z

There is no change :

$ nodemon -i node_modules/ server.coffee  --dump
3 Dec 21:17:18 - [nodemon] v0.9.10
[nodemon] exception in nodemon killing node
[nodemon] 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 Function.check (/usr/local/lib/node_modules/nodemon/lib/config/watchable.js:34:6)
    at alternativeCheck (/usr/local/lib/node_modules/nodemon/lib/config/checkWatchSupport.js:18:15)
    at /usr/local/lib/node_modules/nodemon/lib/config/checkWatchSupport.js:36: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.<anonymous> (child_process.js:948:11)

remy · 2013-12-03T20:22:33Z

Hmm, sorry, can you stick --dump before your script, it should give me a dump of the config.

chok · 2013-12-03T20:26:12Z

I already tried both :(

$ nodemon -i node_modules/ --dump server.coffee 
3 Dec 21:25:35 - [nodemon] v0.9.10
[nodemon] exception in nodemon killing node
[nodemon] 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 Function.check (/usr/local/lib/node_modules/nodemon/lib/config/watchable.js:34:6)
    at alternativeCheck (/usr/local/lib/node_modules/nodemon/lib/config/checkWatchSupport.js:18:15)
    at /usr/local/lib/node_modules/nodemon/lib/config/checkWatchSupport.js:36: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.<anonymous> (child_process.js:948:11)

tjbrennan · 2013-12-03T20:37:14Z

Hi. I don't want to sound obtuse, but when I encountered this error I fixed it by increasing max_user_watches on my system. I've been watching this thread to see if something else was going on.

remy · 2013-12-03T20:40:01Z

@taylorjbrennan yeah, I know that will fix the issue, but whilst @chok is able to replicate consistently, I'm after a change that will fix nodemon without the user needing to do the max_user_watches io magic.

tjbrennan · 2013-12-03T20:41:54Z

@remy great, I look forward to seeing it.

remy · 2013-12-30T12:19:49Z

@chok can you try this again with nodemon@1.0.0 - nodemon now ignores .git and node_modules/**/node_modules by default, so the number of watches should be significantly lower (I'll reopen if this is still an issue).

I'm also going to try to detect the watch ENOSPC error and echo out a message about increasing max_user_watches. Not ideal, but nothing more that I can really do.

chok · 2014-01-02T11:52:18Z

I haven't this message anymore :) but now I have the problem explained in #245

remy · 2014-12-09T17:31:22Z

@alejonext can you try with npm install -g nodemon@dev - I've made quite a few changes that aren't in 1.2.1.

The error actually means "Error NO disk SPaCe" - but I think it's linked to the number of files being monitored, which should be reduced down via changes to the watching code...

jamlfy · 2014-12-09T17:42:08Z

@remy Works perfect :) thanks for your work!!!!

remy · 2014-12-09T18:40:13Z

Sweet. There'll be a stable release of 1.3.0 to npm likely this week with a bunch of bug fixes too.

baio · 2014-12-10T06:07:44Z

@remy astonished with response time. Thanks!

nikopolidi · 2014-12-15T18:25:11Z

@remy
exception in nodemon killing node
Error: watch ENOSPC
at errnoException (fs.js:1030:11)
at FSWatcher.start (fs.js:1062:11)
at Object.fs.watch (fs.js:1087:11)

node v0.10.33
OS: Linux ubuntu

ahnbizcad · 2015-03-22T04:40:13Z

I've fixed this with this command ember-cli/ember-cli#1240 (comment)

but is updating the package the recommended way?

I'm wondering why it got like this in the first place. I'm using node version manager with
node 0.12.0
npm 2.7.0
ember 0.2.0

jkarttunen · 2015-03-26T10:44:58Z

@ahnbizcad
Maybe because of
https://github.com/joyent/node/wiki/API-changes-between-v0.10-and-v0.12#resource-management ?

uttampanara · 2015-06-23T05:21:01Z

The system has a limit to how many files can be watched by a user. You can run out of watches pretty quickly if you have Grunt running with other programs like Dropbox.

The post suggest running this to increase the number of watches that are available.

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

ghost · 2015-09-08T15:20:33Z

I'm having this issue with "nodemon": "^1.4.1" and "node": "0.12.7" 😞

remy · 2015-09-08T16:17:25Z

Please try with #625

On Tue, 8 Sep 2015 16:20 Wesley Queiroz notifications@github.com wrote:

I'm having this issue with "nodemon": "^1.4.1" and "node": "0.12.7" [image:
😞]

—
Reply to this email directly or view it on GitHub
#214 (comment).

ghost · 2015-09-08T16:37:30Z

Tried with alpha but still getting ENOSPC...
My sysctl.conf has fs.inotify.max_user_watches=10000.
If I change it to 524288 it works, but in my "dev-server" I'll not able to change it.

remy · 2015-09-08T16:50:51Z

How many files are you trying to watch? i.e. how many are under your
working directory?

On Tue, 8 Sep 2015 at 17:37 Wesley Queiroz notifications@github.com wrote:

Tried with alpha but still getting ENOSPC...
My sysctl.conf has fs.inotify.max_user_watches=10000.
If I change it to 524288 it works, but in my "dev-server" I'll not able
to change it.

—
Reply to this email directly or view it on GitHub
#214 (comment).

ghost · 2015-09-09T13:52:55Z

Not many, 30 at max.
But i think nodemon is trying to watch node_modules at the root of the project.
Below is the config passed to nodemon (I'm using it as a node module):

nodemon({
    script: 'server/server.js',
    watch: [
        'server/',
        'common/'
    ],
    ext: 'js json coffee'
});

the server folder has:
7 coffee files
5 json files
and the common folder has just 1 json file...

remy · 2015-09-09T21:40:12Z

Yeah...so run find . | wc -l and what does that number give you? Though, it's supposed to ignore node_modules by default, it's possible it's not being taken into consideration.

ghost · 2015-09-10T03:06:50Z

Running find . | wc -l on the root of the project gives me 18266 but when I remove node_modules and bower_components gives just 320.

remy · 2015-09-10T05:57:49Z

Okay, so I think that the watch is including the node_modules - this is part of the #625 refactor and needs to be fixed.

remy · 2015-09-10T10:06:34Z

@wesleycoder can you try with the latest nodemon@dev (it should be version 1.5.0-alpha4) and run with DEBUG=nodemon <your normal nodemon command> then paste up the full output.

ghost · 2015-09-10T16:51:52Z

Whoa!
It works!
No errors!
Thanks!

ankibalyan · 2016-02-15T11:57:23Z

This might be because of your system reach out of user can watch files. you can use the following command line in ubuntu
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
or try
npm dedupe

Ref to this stackoverflow

ikrum · 2016-03-08T06:07:29Z

@ankibalyan @uttampanara

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

rafaelfvalim · 2016-05-27T23:08:42Z

works for me too !
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

mouthzipper · 2016-05-31T14:49:34Z

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

meghjoshi · 2018-03-16T09:29:40Z

Run this command

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

ahmdsolmn · 2018-03-19T13:07:22Z

Another possible solution is to add a nodemon.json configuration file in your root folder and specify ignore patterns for example:
nodemon.json

{
  "ignore": [
    "*.test.js", 
    "dist/*"
  ]
}

Note that by default .git, node_modules, bower_components, .nyc_output, coverage and .sass-cache are ignored so you don't need to add them to your configuration.

FossPrime · 2018-07-30T00:09:47Z

The fs notify trick doesn't seem to work on a docker container... at least not Alpine 3.8, I get the same ENOSPC error. It's becoming more important as tools get deprecated and we still need to maintain legacy products

MariusStuparu mentioned this issue Dec 2, 2013

Nodemon doesn't like clustering with CoffeeScript #229

Closed

remy mentioned this issue Dec 4, 2013

Ignore node_modules and .git by default #230

Closed

remy closed this as completed Dec 30, 2013

remy mentioned this issue Dec 30, 2013

Useful message for watch ENOSPC error #239

Closed

curran mentioned this issue Sep 21, 2016

Get Tests to Run nuagenetworks/visualization-framework#37

Closed

albinekb mentioned this issue Sep 28, 2017

Ubuntu 14.04 not launching. vercel/hyper#2298

Closed

2 tasks

wellyshen mentioned this issue Nov 14, 2017

Getting errror when starting in development mode with yarn start wellyshen/react-cool-starter#128

Closed

FND mentioned this issue Feb 27, 2018

watch mode chokes due to file limit (Linux) frctl/fractal#424

Closed

happybeing mentioned this issue Jan 8, 2019

yarn start / npm start / reac-static start errors with 'Error: watch /home/mrh/src/safe-sites/safe-dweb-blog/static.config.js ENOSPC' react-static/react-static#952

Closed

An error "Error: watch ENOSPC" #214

An error "Error: watch ENOSPC" #214

Comments

jamlfy commented Oct 20, 2013

remy commented Oct 20, 2013

remy commented Oct 20, 2013

jamlfy commented Oct 21, 2013

remy commented Oct 27, 2013

jamlfy commented Oct 28, 2013

davidbarton commented Nov 11, 2013

davidbarton commented Nov 13, 2013

chok commented Nov 27, 2013

remy commented Dec 3, 2013

davidbarton commented Dec 3, 2013

chok commented Dec 3, 2013

remy commented Dec 3, 2013

chok commented Dec 3, 2013

remy commented Dec 3, 2013

chok commented Dec 3, 2013

remy commented Dec 3, 2013

chok commented Dec 3, 2013

remy commented Dec 3, 2013

chok commented Dec 3, 2013

remy commented Dec 3, 2013

chok commented Dec 3, 2013

tjbrennan commented Dec 3, 2013

remy commented Dec 3, 2013

tjbrennan commented Dec 3, 2013

remy commented Dec 30, 2013

chok commented Jan 2, 2014

remy commented Dec 9, 2014

jamlfy commented Dec 9, 2014

remy commented Dec 9, 2014

baio commented Dec 10, 2014

nikopolidi commented Dec 15, 2014

ahnbizcad commented Mar 22, 2015

jkarttunen commented Mar 26, 2015

uttampanara commented Jun 23, 2015

The post suggest running this to increase the number of watches that are available.

ghost commented Sep 8, 2015

remy commented Sep 8, 2015

ghost commented Sep 8, 2015

remy commented Sep 8, 2015

ghost commented Sep 9, 2015

remy commented Sep 9, 2015

ghost commented Sep 10, 2015

remy commented Sep 10, 2015

remy commented Sep 10, 2015

ghost commented Sep 10, 2015

ankibalyan commented Feb 15, 2016

ikrum commented Mar 8, 2016

rafaelfvalim commented May 27, 2016

mouthzipper commented May 31, 2016

meghjoshi commented Mar 16, 2018

ahmdsolmn commented Mar 19, 2018

FossPrime commented Jul 30, 2018