Too many open files - Failed to initialize inotify: the user limit on the total number of inotify instances has been reached. about rb-inotify HOT 15 CLOSED

I've just stumbled upon the same problem. I think this issue could be not relate to rb-inotify, but the tools we use on our computers. I just tried to increase a limit of user instances. Here is the link with more info:

http://unix.stackexchange.com/questions/13751/kernel-inotify-watch-limit-reached

I had to increase this:

echo 256 > /proc/sys/fs/inotify/max_user_instances

from rb-inotify.

yup, that solves my issues

# increase inotify file watch limit
ofile=/proc/sys/fs/inotify/max_user_instances
sudo sh -c "echo 8192 > $ofile"
cat $ofile
rerun app.rb

from rb-inotify.

thanks @hron it solved the issue for me

from rb-inotify.

I don't know who the right person to talk to about this, but I also don't know of anything we can do in rb-inotify to solve the issue 😕. Sorry.

from rb-inotify.

anything we can do to fix the problem would be nice :/ it happens to me randomly and persists until I reboot my computer.

from rb-inotify.

not for me, unfortunately - I still get the error. Oh well.

from rb-inotify.

@Karpah echo 256 > /proc/sys/fs/inotify/max_user_instances , try to increase the value, i got now 600, before 512 was working good, it looks like each time I restart guard ( kill and start again ) I had to increase it (?)

from rb-inotify.

I found that quote here: http://irclog.whitequark.org/ruby-lang/2012-03-29

16:11 <Defusal> now i can't even test anymore, rb-inotifier does not automatically close inotify handles, so if you dont manually do it, such as when the app doesn't exit cleanly, the handles are left open on the kernel forever...
16:11 <Defusal> so now its maxed out my user limit for inotify
16:11 <Defusal> Exception: Too many open files - Failed to initialize inotify: the user limit on the total number of inotify instances has been reached.
16:13 <Defusal> so between EventMachine crashing ruby and rb-inotifier, it's really screwed me over

from rb-inotify.

I'm surprised that the OS doesn't clean up handles that are held by processes that have died. I'm not aware of a way to clean them up manually in the face of the process crashing.

from rb-inotify.

Hi
Are there any news about the issue?

from rb-inotify.

I'm still unaware of any way to handle this in rb-inotify itself.

from rb-inotify.

I catch this issue when my PC had been worked for a week with turned guard on and without reboot.
Also we can compare libs/kernel versions

from rb-inotify.

I suspect the Linux kernel header for inotify has changed, so the inotify.so needs a recompile?
I am trying to find inotify.c to recompile it.
Though I do not see it in this repo.
Any clues?

from rb-inotify.

Could not find inotify.c so moving to: https://github.com/nex3/rb-inotify

from rb-inotify.

I've just stumbled upon the same problem. I think this issue could be not relate to rb-inotify, but the tools we use on our computers. I just tried to increase a limit of user instances. Here is the link with more info:

http://unix.stackexchange.com/questions/13751/kernel-inotify-watch-limit-reached

I had to increase this:

echo 256 > /proc/sys/fs/inotify/max_user_instances

works for me,thx

from rb-inotify.