Skip to content
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

rancher-windows-exporter not working on AWS EKS #80

Open
chrism417 opened this issue Feb 3, 2022 · 0 comments
Open

rancher-windows-exporter not working on AWS EKS #80

chrism417 opened this issue Feb 3, 2022 · 0 comments

Comments

@chrism417
Copy link

Rancher windows exporter is running AWS EKS with wins version 0.1.3. However, we see the following with exporter-node-proxy:

INFO[2022-02-03T18:22:38-05:00] Connecting to proxy                           url="ws://rancher_wins_proxy"
ERRO[2022-02-03T18:23:48-05:00] Error writing ping                            error="i/o timeout"
ERRO[2022-02-03T18:23:48-05:00] Error writing ping                            error="i/o timeout"
FATA[2022-02-03T18:23:48-05:00] i/o timeout
2022/02/03 18:23:48 tcpproxy: for incoming conn 10.136.180.113:43510, error dialing "": i/o timeout
2022/02/03 18:23:48 tcpproxy: for incoming conn 10.136.185.172:46670, error dialing "": i/o timeout
2022/02/03 18:23:48 tcpproxy: for incoming conn 10.136.185.172:45154, error dialing "": i/o timeout

The bottom three IPs are prometheus. However, I can get onto the EC2 instance hosting the rancher-windows-exporter pod and curl http://localhost:9796/metrics and can get all the metrics. If I exec into another node in any namespace and curl the EC2 instance primary IP such as http://10.136.111.222:9796/metrics it works. The servicemonitor picks up the IP of the pod running rancher-windows-exporter which doesn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants