Noe Nieto

Mi sitio personal | Personal site

My first issue with Meteor solved quickly

Cómo resolver el error 'watch ENOSPC' en Meteor ajustando los parámetros de inotify en Linux para monitoreo de archivos.

My first issue with Meteor solved quickly

Today I was hacking on my first app with Meteor and I stumbled upon the following issue right after running the application for the first time:

[tzicatl@hormiga-gris preguntame]$ meteor
[[[[[ ~/Aplicaciones/Codigo/Meteor/preguntame ]]]]]

Running on: http://localhost:3000/

fs.js:837
    throw errnoException(errno, 'watch');
          ^
Error: watch ENOSPC
    at errnoException (fs.js:806:11)
    at FSWatcher.start (fs.js:837:11)
    at Object.fs.watch (fs.js:861:11)
    at _.extend._scan (/usr/lib64/meteor/app/meteor/run.js:355:24)
    at Array.forEach (native)
    at Function._.each._.forEach (/usr/lib64/meteor/app/lib/third/underscore.js:76:11)
    at new DependencyWatcher (/usr/lib64/meteor/app/meteor/run.js:291:5)
    at exports.run.start_watching (/usr/lib64/meteor/app/meteor/run.js:490:17)
    at exports.run.restart_server (/usr/lib64/meteor/app/meteor/run.js:547:5)
    at /usr/lib64/meteor/app/meteor/run.js:607:9

I found this thread on StackOverflow, but that specific workaround didn't work out well. So the user Lander gave me a kind hand and suggested that I should tweak fs.inotify.max_user_watches and set it to 10000.

So, I combined both solutions (the one from StackOverflow and the one from Lander) and this fixed the issue:

echo 10000 > /proc/sys/fs/inotify/max_user_watches
echo 10000 > /proc/sys/fs/inotify/max_user_instances

Back to hacking again.