Nsryjdtyk

As per discussion over here, ENOSPC means Error No more hard-disk space available. Reason why this much memory required by nodemon or gulp-nodemon (in my case) is that it was watching contents of a folder which it shouldn't. To fix that nodemon has ignore setting that can be used to tell nodemon what not to watch. Have a look at nodemon sample config here.

[nodemon] Internal watch failed: watch /home/Document/nmmExpressServer/bin ENOSPC

npm ERR! code ELIFECYCLE

npm ERR! errno 1

npm ERR! nmmexpressserver@0.0.0 start: `nodemon ./bin/www`

npm ERR! Exit status 1

npm ERR! 

npm ERR! Failed at the nmmexpressserver@0.0.0 start script.

This is the error I got when running nodemon ./bin/www.

The solution was closing an Atom window that had a entire directory of folders open in the project window.

I don't know why, but I'm assuming Atom and nodemon use similar processes to watch files/folders.

Erik,
You can just kill all the other node processes by

pkill -f node

and then restart your server again. It'll work just fine then.

It works for me.

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

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.

Explanation: This error happens because you exceeded the max number of watchers allowed by your system (i.e. nodemon has no more disk space to watch all the files - which probably means you are watching not important files). So you ignore non-important files that you don't care about changes in them for example the build output or the test cases.

On running node server shows Following Errors and solutions:

nodemon server.js

[nodemon] 1.17.2

[nodemon] to restart at any time, enter rs

[nodemon] watching: .

[nodemon] starting node server.js

[nodemon] Internal watch failed: watch /home/aurum304/jin ENOSPC

sudo pkill -f node

or

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

I had the same error, but in Ubuntu 14.04 inside Windows 10 (Bash on Ubuntu on Windows). All I did to overcome the error was to update the Creators update, which then allowed me to install 16.04 version of Ubuntu bash and then after installing newest version of node (by this steps) I installed also the newest version of npm and then the nodemon started to work properly.

Instead of specifying a list of directories to ignore (e.g. negative), you can also specify a list of directories to watch (e.g positive):

nodemon --watch dir1 --watch dir2  dir1/examples/index.js

In my particular case, I had one directory I wanted to watch and about nine I wanted to ignore, so specifying '--watch' was much simpler than specifying '--ignore'

After running nodemon ,I got following error

[nodemon] 1.18.6
[0] [nodemon] to restart at any time, enterrs
[0] [nodemon] watching: *.*
[0] [nodemon] startingnode server.js
[0] [nodemon] Internal watch failed: ENOSPC: no space left on device, watch 'some filename'
[0] npm ERR! code ELIFECYCLE
[0] npm ERR! errno 1
[0] npm ERR! mernapp@1.0.0 server:nodemon server.js
[0] npm ERR! Exit status 1
[0] npm ERR!
[0] npm ERR! Failed at the mernapp@1.0.0 server script.

But these were resolved after running this command:

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