-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Error 500 empty ring when referring to loki #7614
Comments
hello @Amfiass, I have the similar issue (https://community.grafana.com/t/post-loki-api-v1-push-500-response-empty-ring-and-context-canceled/75544) as you and still no idea how to fix it. Kindly tell me if you find out the solution. |
I am having the same issue. Any hint or help would be appreciated. |
@Schmoho @andrewkwok2022 The problem is probably in the key-value store. A possible solution is to change storage to consul or etcd. We solved the problem by deploying the Loki cluster in the kubernetes, since the definition of the members of the ring occurs through the kubernets API. |
I'm using inmemory kv and any kinds of cloud storage are not an option here |
Hello @Schmoho @andrewkwok2022 In the official documentation said this: In this mode the component microservices of Loki are bundled into two targets: -target=read and -target=write. The BoltDB compactor service will run as part of the read target. You only need deploy section compactor y read node. The config file must be different for -target=read and -target=write. I had the same problem an change this its works fine. This is mi basic config for two options: ### -target=read
### -target=write
|
same issue |
Also have this issue. I am running Loki as a single container with |
Is there documentation for how this "ring" thing is configured? What is the difference between A search for |
I also have a same issue. |
running loki-distributed. promtail says: This error msg comes up as soon as loki is down, why can't promtail reconnect correctly when loki comes up again? If i reinstall promtail again after loki is up, then i have no issues. Or it's isnt a problem, because i can retreive logs as usual. |
same error here |
Hello!
Faced a problem when installing a loki cluster.
The cluster consists of 5 nodes:
All have the same configuration file installed with a difference in the target item:
All healthchecks pass, the service starts.
According to the logs, Loki was able to locate all the members of the ring.
But when trying to connect the cluster to grafana, a 500 error:
Loki: Internal Server Error. 500. empty ring
In the service logs I see the following:
At the same time, the installation of loki on one server works correctly, logs are written and read.
Tell me, please, where to dig, I can not find any problems.
Also, I tried to connect the distributor to the loki, the logging does not happen either. A 404 error is thrown without any explanation:
At the same time, the s3 storage is available, another lock is written to it in parallel, which is located on a separate server.
The text was updated successfully, but these errors were encountered: