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

fsnotify watcher: too many open files #789

Open
fosterseth opened this issue Jun 7, 2023 · 1 comment
Open

fsnotify watcher: too many open files #789

fosterseth opened this issue Jun 7, 2023 · 1 comment

Comments

@fosterseth
Copy link
Member

receptor is not bubbling up this error message in some situations.

if err == io.EOF {

On a system where fsnotify cannot create a watcher, ReadString returns EOF, and line has this content

failed to create fsnotify watcher: too many open files

however, we are leveraging EOF to also mean "we are done reading from the pod, all is good"

I think if err is EOF and line is not empty, then we may need to write bubble up line as an error.

We should make sure line is expected to be empty in successfully cases before doing that, however.

@fosterseth
Copy link
Member Author

fosterseth commented Jun 7, 2023

setting these values (or lower) on your system/VM might help replicate the issue

sysctl fs.inotify.max_user_instances=128
sysctl fs.inotify.max_user_watches=65536

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant