#What do the logs say when put into debug
solid fossil
I'd very happily not do some fiddling, but it doesn't work and I don't know what else to do in order to debug it. Here's what I've done so far:
- Confirmed that posting to Loki from inside the Loki container works
- Confirmed that posting to Loki from inside the Promtail container works
- That's all I can do 😦
The Promtail container logs say:
level=info ts=2023-04-28T09:19:48.214747284Z caller=server.go:288 http=[::]:9080 grpc=[::]:37225 msg="server listening on addresses"
level=info ts=2023-04-28T09:19:48.230530349Z caller=main.go:121 msg="Starting Promtail" version="(version=2.6.1, branch=HEAD, revision=6bd05c9)"
And then never anything more.
So its on, but either its not noticing changes to the journal, or its not managing to post to Loki (and doing it silently)
solid fossil
Yes, Loki is definitely running..
If I manually construct a query to Loki with curl it gets picked up and I can see it in Grafana, so that side of things seems to be ok
I haven't done any configuration of Promtail because the docs say its not necessary:
By default this addon version of Promtail will tail logs from the systemd journal. This will include all logs from all addons, supervisor, home assistant, local log files in /share or /ssl if you have a particular add-on that logs to a file instead of to stdout.
but also because I have no idea what I would configure 🙂
earnest citrus
I just tried setting it up myself and I see the same as you. So, not exactly sure... the most significant thing I see in the debug output is what appear to be a conflicted client/clients section in promtail. I wonder if it's reading the first one and assuming there's no client?
(Can't copy and paste the text, so image of text will have to do)
earnest citrus
Odd though, I don't actually see the add-on writing that section, so promtail itself might be interpreting it somehow?
solid fossil
Right, nothing like this appears in the addon code that I can see
You see why I wanted to have a fiddle around, eh 🙂
Maybe its something as simple as Promtail needing to be updated to the latest version or something like that
When refreshing I noticed some other logs that seemed to get cleared
Maybe there is a clue in those earlier startup logs
It looks ok to me 🤷
BTW I've tried both with the normal and the beta repositories, but they have the same result
earnest citrus
Yeah, seems odd. The limited amount of feedback it gives makes it challenging to see if it's even trying to connect. The add-on owner is in this Discord, he might have some ideas on that possibly
solid fossil
I've been trying to avoid noising them up because its a bit invasive, but I think that's the only way