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

Error watching for file (runtime.json) ENOSPC #27

Closed
fed135 opened this issue Jun 29, 2015 · 3 comments
Closed

Error watching for file (runtime.json) ENOSPC #27

fed135 opened this issue Jun 29, 2015 · 3 comments

Comments

@fed135
Copy link

fed135 commented Jun 29, 2015

Hey guys,

Just installed the package and I got some weird error when I start my application.

I've isolated the faulty line to this (I don't even do anything with it):

var Monitor = require('monitor');

The error being :

Error watching for file: /home/fcharette/Documents/workspace/gap-telemetry/config/runtime.json { [Error: watch ENOSPC] code: 'ENOSPC', errno: 'ENOSPC', syscall: 'watch' }

monitor version from npm, v0.6.10

I run iojs v1.8.2, npm 2.9.0
I'm on Ubuntu 15
I have plenty of space on my disk (and on /tmp)

Any ideas ?
Thank you!

@lorenwest
Copy link
Owner

A quick search on ENOSPC shows you have no space left on your device. The runtime.json file is probably being watched from the node-config dependency.

@fed135
Copy link
Author

fed135 commented Jun 29, 2015

As mentionned, plenty of space:

Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 798M 18M 781M 3% /run
/dev/sda1 111G 14G 91G 14% /
tmpfs 3.9G 444K 3.9G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs 798M 56K 798M 1% /run/user/1000

Even changed my tmp path in npm config to /var/logs

Looking into the config package, I see where it does the watch, still unsure why there is an error though.

@fed135
Copy link
Author

fed135 commented Jun 29, 2015

According a couple bug reports surrounding fs.watch and ENOSPC, it seems like the issue is that the limit for simultaneous file watches has been reached.

I rebooted and now everything seems to run fine.
Not entirely sure where the other file watches were coming from, had no other node process opened.

Oh well, you could maybe add a note about this somewhere.

FYI: I like to know what the libraries I require do behind my back. And preferably, I like them to not do anything behind my back.

@fed135 fed135 closed this as completed Jun 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants