Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upShort hostname results in "context deadline exceeded" #2332
Comments
This comment has been minimized.
This comment has been minimized.
|
This sounds like a name resolution issue on your end. Have you verified this name resolves and is accessible from within the container? |
This comment has been minimized.
This comment has been minimized.
|
Yep. I used "docker exec" to get into the prometheus container and then could both ping "jira" and telnet to the correct port sending a manual HTTP request and getting the metric data back. |
This comment has been minimized.
This comment has been minimized.
|
Deadline exceeded implies that DNS worked. Can you access jira via IP address? Incidentally ping uses non-standard resolution. I wouldn't fully trust it for testing something like this. |
This comment has been minimized.
This comment has been minimized.
|
Yep accessing via IP address works. If I just change the container/link name in Docker to have an extra char it works, so it is just the 4 char hostname/port (jira:8080) which doesn't work. I don't see the callback on the jira exporter side being called at all (this is a Python script using the client library) |
This comment has been minimized.
This comment has been minimized.
|
Something weird is going on here anyway. Several of my home systems happen to be 4 chars, so I don't think it's on the Prometheus side. |
This comment has been minimized.
This comment has been minimized.
|
Could it be something about being 9 total chars (i.e. host:port = 4:4 chars)? It was a very odd thing and as I say just changing the hostname fixed it |
This comment has been minimized.
This comment has been minimized.
|
This is likely something odd with resolution on your end. If this is still occurring, it's best to discuss on https://groups.google.com/forum/#!forum/prometheus-users |
brian-brazil
closed this
Mar 27, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
stuart-c commentedJan 10, 2017
What did you do?
Added a target with a very short (4 char) hostname and port number combo
What did you expect to see?
Successful polling of the new hostname
What did you see instead? Under which circumstances?
No stats - error of "context deadline exceeded". Still didn't work even if the timeout was increased significantly.
Environment
Official Docker container of Prometheus (:latest)
The following config snippet didn't work:
static_configs:
But the following does:
static_configs: