Open imclint21 opened 5 months ago
Hi @imclint21
Thanks for reporting. Can you also post the full docker run
command the the startup logs?
Here you go @chaudum I exported the whole logs. loki.csv
I restarted the instance for now it seems UP I'll wait a bit.
Okay no it again crashed, and this time I don't have logs.
The only things I can say it's it crash when I restart promtail on all my servers:
May 15 12:26:34 fra3 promtail[30227]: level=warn ts=2024-05-15T10:26:34.891870836Z caller=client.go:419 component=client host=loki.xxx msg="error sending batch, will retry" status=429 tenant= error="server returned HTTP status 429 Too Many Requests (429): Ingestion rate limit exceeded for user fake (limit: 4194304 bytes/sec) while attempting to ingest '4383' lines totaling '1048442' bytes, reduce log volume or contact your Loki administrator to see if the limit can be increased"
May 15 12:26:37 fra3 promtail[30227]: level=warn ts=2024-05-15T10:26:37.652537111Z caller=client.go:419 component=client host=loki.xxx msg="error sending batch, will retry" status=429 tenant= error="server returned HTTP status 429 Too Many Requests (429): Ingestion rate limit exceeded for user fake (limit: 4194304 bytes/sec) while attempting to ingest '4380' lines totaling '1048435' bytes, reduce log volume or contact your Loki administrator to see if the limit can be increased"
May 15 12:26:39 fra3 promtail[30227]: level=warn ts=2024-05-15T10:26:39.696488947Z caller=client.go:419 component=client host=loki.xxx msg="error sending batch, will retry" status=429 tenant= error="server returned HTTP status 429 Too Many Requests (429): Ingestion rate limit exceeded for user fake (limit: 4194304 bytes/sec) while attempting to ingest '4386' lines totaling '1048532' bytes, reduce log volume or contact your Loki administrator to see if the limit can be increased"
After some testing I could not reproduce this issue yet.
I can propose you an access to our NAS if you want!
I guess it's related to compactor but I'm not sure, we have like 1GB currently in /loki.
Any news guys? I don't think I used a so special configuration, that's strange
The only things I can say it's it crash when I restart promtail on all my servers:
~~Could it be that you are overloading Loki when you restart your Promtails? The 429 HTTP error indicates that you are hitting the ingestion rate limit. Have you checked the memory usage of your Docker container, maybe they are OOMing?~~
Edit: Nevermind, I saw that screenshot from panic again. This is definitely not from an OOM event. Is it always panicking?
Actually I'm not a specialist at all of Loki, I just try to make it works
I can propose you an access to our NAS if you want!
You are running Loki as Docker container on a NAS? I don't think you can run Loki in a stable way in an environment that is usually very restricted in the amount of resources (CPU,memory).
It's not restricted at all.
Describe the bug The instance crash after few hours
Configuration:
Logs I get: