Open chriskuchin opened 6 months ago
Hi @chriskuchin Thanks for reporting the issue. What version did you use?
Is it possible that it is the same bug as described in https://github.com/grafana/loki/issues/12842? If so, there is already a fix with https://github.com/grafana/loki/pull/12873 and will be available with the next patch release.
That looks like it could be it. I wasnt able to figure out which endpoint was triggering it. I was running 3.0.0 when it was panicking. I have downgraded to 2.9.6.
Any idea when the next patch will be released?
Just following up here My query frontentend are stuck on an old version and would love if loki would release a patch version to fix this so I can verify that it is the problem
Describe the bug I recently upgraded to v3 on my self hosted cluster. When I roll out the query frontend it crashes with the following error.
I haven't been able to identify what is causing the nil pointer.
To Reproduce Steps to reproduce the behavior: I have rolled back to the previous version of my frontend but everything else is running v3 and seems to be working...
I have reviewed everything I can find and have no idea what is causing this.
Expected behavior No Nil Pointer
Environment: ECS with cloudmap
Screenshots, Promtail config, or terminal output If applicable, add any output to help explain your problem. loki_config.yaml.txt