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

epoll_ctl: File exists, errno=17 #488

Closed
solsson opened this issue Jan 22, 2018 · 7 comments
Closed

epoll_ctl: File exists, errno=17 #488

solsson opened this issue Jan 22, 2018 · 7 comments

Comments

@solsson
Copy link

solsson commented Jan 22, 2018

I run fluent/fluent-bit-kubernetes-logging#16 with modest load and very tight memory limits, 10MB. This triggers occasional restarts of the daemonset pods. Despite this it all works very well, but now I have one pod that repeatedly logs the following error:

[2018/01/22 09:08:15] [  Error] epoll_ctl: File exists, errno=17 at /tmp/src/lib/monkey/mk_core/mk_event_epoll.c:133

Before I kill the pod, is there anything I should investigate?

@edsiper
Copy link
Member

edsiper commented Jan 23, 2018

@solsson is the HTTP Server enabled ?, if so, if you disable it do you see the same issue ?

@solsson
Copy link
Author

solsson commented Jan 24, 2018

What HTTP Server are you referring to?

@StevenACoffman
Copy link
Contributor

Prometheus endpoint requires the HTTP server (monkey is the one in fluent-bit). The config that enables the HTTP_Server is here in the fluent-bit-configmap

        HTTP_Server   On
        HTTP_Listen   0.0.0.0
        HTTP_Port     2020

@solsson
Copy link
Author

solsson commented Jan 24, 2018

Thanks. Yes, I run the exact config from fluent/fluent-bit-kubernetes-logging#16, bar memory limit changes for fluent/fluent-bit-kubernetes-logging#18. The pod is gone now, so I'll have to see if I run into this again, and next time I will check if I get any prometheus metrics for the pod.

@edsiper
Copy link
Member

edsiper commented Jan 30, 2018

are you seeing the issue with the latest fluent/fluent-bit-0.13-dev:0.6 image ?

@solsson
Copy link
Author

solsson commented Jan 30, 2018

Nope, not seen. It might have been a rare error though, and the new tag hasn't been running for long. Ok with me if you want to close the issue. I can post an update if I see it again.

@edsiper
Copy link
Member

edsiper commented Jan 30, 2018

thanks, I will close it for now.

@edsiper edsiper closed this as completed Jan 30, 2018
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

3 participants