-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
1.1.0 kubernetes panic: send on closed channel #877
Comments
I has happend alot since i updated to 1.1.0 yesterday:
|
@jonaz I made a fix and pushed a Docker image for testing |
Hi @emilevauge I had the same problem, just updated my traefik controller (it went smoothly), will let you know how it goes for me. Thanks ! |
@emilevauge i will try tomorrow at work. is there a commit with diff i can look at to complement the testing? (code review ftw) |
Here is the pull request #900 |
I have deployed containous/traefik:k8s into our development cluster and will give it a few hours now. |
As a heads up, it has been 15 hours and not a single restart. |
There is a problem with the fix. containous/traefik:k8s seems contain the fix in #874
Which means that it will never try do write to errCh (failed to decode watch event: GET) and it will not panic. So in order to test this fix we need a docker image without the fix from #874. Since this really is a bug in the error handling we need to continue to get the errors that #874 solved :) |
@emilevauge thanks i'll redeploy that |
I have not had any panics the last 5 hours. I will leave it running over the weekend. |
It has not crashed yet. So i would consider it fixed. |
I've switched to using the containous/traefik:k8s build and still see the decoding issues:
My traefik config:
|
Yeah if you read my comment you will se why: |
The comment from emilevuage indicates the k8s image was updated 3 days ago without the fix. The image on docker hub also indicates it was updated 3 days ago. |
Yeah thats exacly the point? containous/traefik:k8s must NOT contain the fix from #874 (fix for unexpected EOF). Otherwise we cannot know if this #877 is fixed. Because as i said this is an error in the errorhandlinng. This issue is only about fixing "panic: send on closed channel" which was an error depending on errorhanding the unexpected EOF. |
Makes sense now. Will ignore the log entries :) Thanks! |
This has happened twice (2) in the last hour since i upgraded to 1.1.0 in our development cluster.
The last log message before the panic was:
I run traefik like this:
The text was updated successfully, but these errors were encountered: