Could mean many things:
- node_exporter isn't running on the target host
- node_exporter is listening on a different port than the one you're trying
to connect to
- it is listening on the wrong IP address or interface (e.g. if bound to
127.0.0.1 then it won't accept connections from outside)
On 2022-04-21 16:03, BHARATH KUMAR wrote:
thanks for your reply. I think we fixed some firewall issues and now
working fine for most servers. But still we are facing new error like
Get "http://some_ip:port_number/metrics": dial tcp
some_ip:port_number: connect: connection refused
what could be
thanks for your reply. I think we fixed some firewall issues and now
working fine for most servers. But still we are facing new error like
Get "http://some_ip:port_number/metrics": dial tcp some_ip:port_number:
connect: connection refused
what could be the reason for this error?
thanks
"Context deadline exceeded" simply means "timeout waiting to connect or
receive data"
It sounds to me like you have a network connectivity problem between the
client (i.e. prometheus) and wherever the binary node exporter was
installed. Talk to a local network administrator or system
If I do curl in the particular server where I installed n=binary node
exporter I am able to see metrics but in browser and grafana and in
prometheus UI I am not able to see metrics. It is showing CONTEXT DEADLINE
EXCEEDED.
thanks
Bharath
On Thursday, 21 April 2022 at 12:18:23 UTC+5:30 Brian
> we are getting error like context deadline exceeded
You haven't show the actual error, nor where you saw it.
The most likely explanation I can see is simply that prometheus cannot
communicate with node_exporter - for example, you've misconfigured the
target or there is some sort of
Hiii
Thanks for your reply. we were using two different ports for two node
exporters. Actually one node exporter is running in container/pod and
another node exporter is running as a binary file. we are not getting any
issue with container/pod one. But when we are running with binary one we
You need to be clearer about what you're doing and what errors you see.
Yes, you could run two node_exporters on the same server, bound to
different ports. However this is normally completely pointless, since
they're both monitoring the same server, and exporting the same data.
It is not
8 matches
Mail list logo
