-
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
Promtail to remote Loki - context deadline exceeded #3867
Comments
Hey @Lithimlin Just to confirm: are you able to communicate with that host/port combination manually from the same host that you're running Promtail from? I want to rule out a networking issue before we dive deeper. |
Yes, indeed. Starting netcat on the remote host and sending messages to port 9200 of the Loki-host causes them to show up in tcpdump. Additionally, I can see that messages from the promtail service on the remote host arrive at the Loki-host. |
I am seeing the exact same error message (context deadline exceeded) while testing promtail on Ubuntu 18.04, currently manually running the binary, no Docker or Systemd involved. |
I upgraded NixOS today and now am using |
Could this have to do with the |
It doesn't look like that was the issue |
+1 Same issue here! Currently testing Loki on Amazon Linux 2 and sending logs from another node via Promtail using same @Lithimlin configuration. (Loki binary + Promtail daemonset) |
While inspecting some logs on the Loki-host (ironically with Loki) I realized that that host refuses the incoming connection from the remote host:
Maybe this helps? PS: Pings do still go through without any issues so this is not a firewall problem |
I updated the original post to reflect changes done in NixOS 21.05. |
Well, this is a bit embarrassing. |
No worries @Lithimlin 🙂 glad you found the source of the issue. |
Describe the bug
I'm trying to set up Promtail on mutliple machines which all send the respective logs to a single central Loki instance. Sending logs from the machine hosting Loki to that Loki instance works fine. However, when I try to do the same from another machine, Promtail is unable to send the logs to Loki. Instead, I get the following error in the logs:
Since most issues here concerning this issue are about docker and the DNS setting, I've tried inserting the Loki-host's IP directly instead though with no difference in behavior. I've also tried looking into the code at the line mentioned in the message but I can't really see anything there.
According to #2453, this error message should also be more verbose if I understood correctly.
Nevertheless, I'm not sure if the data processing time is the issue here. Maybe someone else can judge that better.
Environment:
To Reproduce
Steps to reproduce the behavior:
grafana-loki-2.2.1
) with the config files found below on Loki-hostgrafana-loki-2.2.1
) with the config file found below on remote hostjournalctl -efu promtail
)I'm not sure if there would be a big difference between doing this on a NixOS system vs any other Linux system though I don't expect it unless it's a different version of Loki.
Expected behavior
Promtail sends the logs to the Loki instance on the Loki-host without issues.
Screenshots, Promtail config, or terminal output
Loki-config on Loki-host:
promtail.nix
file on both Loki-host and remote host:EDIT: Updated configs to reflect changes in NixOS 21.05
EDIT: Added i/o timeout error
The text was updated successfully, but these errors were encountered: