[2.0 beta] addrConn.resetTransport failed to create client transport #3004

hiscal2015 · Jul 29, 2017

Hi, all

When I'm testing 2.0 beta version, everything looks fine but one error repeats in logs:

prometheus[3766]: 2017/07/30 07:44:58 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp [::]:9090: connect: cannot assign requested address"; Reconnecting to {[::]:9090 <nil>}

What does this mean, do I need to fix this? Thanks.

gouthamve · Jul 30, 2017

This looks like an error from the new GRPC API. Not sure what the issue is.

/cc @fabxc

vin33sh · Aug 8, 2017

I get the same thing. I am using 'prometheus-2.0.0-beta.0.windows-amd64.tar.gz'

prometheus-2.0.0-beta.0.windows-amd64.tar.gz

D:\tools\prometheus-2.0.0>prometheus.exe --config.file=./prometheus.yml INFO[0000] Starting prometheus (version=2.0.0-beta.0, branch=master, revision=2b5d9159537cbd123219296121e05244e26c0940) source="main.go:202" INFO[0000] Build context (go=go1.8.3, user=root@fc24486243df, date=20170712-12:28:38) source="main.go:203" INFO[0000] Host details (windows) source="main.go:204" INFO[0000] Starting tsdb source="main.go:216" INFO[0000] tsdb started source="main.go:222" INFO[0000] Loading configuration file ./prometheus.yml source="main.go:351" INFO[0000] Starting target manager... source="targetmanager.go:67" INFO[0000] Listening on 0.0.0.0:9090 source="web.go:286" 2017/08/08 20:03:43 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: failed to do connect handshake, response: \"HTTP/1.1 503 Service Unavailable\\r\\nConnection: close\\r\\nContent-Length: 768\\r\\nCache-Control: no-cache\\r\\nContent-Type: text/html; charset=utf-8\\r\\nPragma: no-cache\\r\\nProxy-Connection: close\\r\\n\\r\\n<HTML><HEAD>\\r\\n<TITLE>Network Error</TITLE>\\r\\n</HEAD>\\r\\n<BODY>\\r\\n\\r\\n<big></big> \\r\\n\\r\\n<blockquote>\\r\\n<TABLE border=0 cellPadding=1 width=\\\"80%\\\">\\r\\n<TR><TD>\\r\\n\\r\\n<big>Network Error (tcp_error)</big>\\r\\n \\r\\n \\r\\n\\r\\n</TD></TR>\\r\\n<TR><TD>\\r\\n\\r\\nA communication error occurred: \\\"\\\"\\r\\n\\r\\n</TD></TR>\\r\\n<TR><TD>\\r\\n\\r\\nThe Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.\\r\\n\\r\\n</TD></TR>\\r\\n<TR><TD>\\r\\n\\r\\n \\r\\nFor assistance, contact your network support team.\\r\\n\\r\\n</TD></TR>\\r\\n</TABLE>\\r\\n</blockquote>\\r\\n\\r\\n</BODY></HTML>\\r\\n\""; Reconnecting to {[::]:9090 <nil>} 2017/08/08 20:03:44 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: failed to do connect handshake, response: \"HTTP/1.1 503 Service Unavailable\\r\\nConnection: close\\r\\nContent-Length: 768\\r\\nCache-Control: no-cache\\r\\nContent-Type: text/html; charset=utf-8\\r\\nPragma: no-cache\\r\\nProxy-Connection: close\\r\\n\\r\\n<HTML><HEAD>\\r\\n<TITLE>Network Error</TITLE>\\r\\n</HEAD>\\r\\n<BODY>\\r\\n\\r\\n<big></big> \\r\\n\\r\\n<blockquote>\\r\\n<TABLE border=0 cellPadding=1 width=\\\"80%\\\">\\r\\n<TR><TD>\\r\\n\\r\\n<big>Network Error (tcp_error)</big>\\r\\n \\r\\n \\r\\n\\r\\n</TD></TR>\\r\\n<TR><TD>\\r\\n\\r\\nA communication error occurred: \\\"\\\"\\r\\n\\r\\n</TD></TR>\\r\\n<TR><TD>\\r\\n\\r\\nThe Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.\\r\\n\\r\\n</TD></TR>\\r\\n<TR><TD>\\r\\n\\r\\n \\r\\nFor assistance, contact your network support team.\\r\\n\\r\\n</TD></TR>\\r\\n</TABLE>\\r\\n</blockquote>\\r\\n\\r\\n</BODY></HTML>\\r\\n\""; Reconnecting to {[::]:9090 <nil>} 2017/08/08 20:03:46 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: failed to do connect handshake, response: \"HTTP/1.1 503 Service Unavailable\\r\\nConnection: close\\r\\nContent-Length: 768\\r\\nCache-Control: no-cache\\r\\nContent-Type: text/html; charset=utf-8\\r\\nPragma: no-cache\\r\\nProxy-Connection: close\\r\\n\\r\\n<HTML><HEAD>\\r\\n<TITLE>Network Error</TITLE>\\r\\n</HEAD>\\r\\n<BODY>\\r\\n\\r\\n<big></big> \\r\\n\\r\\n<blockquote>\\r\\n<TABLE border=0 cellPadding=1 width=\\\"80%\\\">\\r\\n<TR><TD>\\r\\n\\r\\n<big>Network Error (tcp_error)</big>\\r\\n \\r\\n \\r\\n\\r\\n</TD></TR>\\r\\n<TR><TD>\\r\\n\\r\\nA communication error occurred: \\\"\\\"\\r\\n\\r\\n</TD></TR>\\r\\n<TR><TD>\\r\\n\\r\\nThe Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.\\r\\n\\r\\n</TD></TR>\\r\\n<TR><TD>\\r\\n\\r\\n \\r\\nFor assistance, contact your network support team.\\r\\n\\r\\n</TD></TR>\\r\\n</TABLE>\\r\\n</blockquote>\\r\\n\\r\\n</BODY></HTML>\\r\\n\""; Reconnecting to {[::]:9090 <nil>} WARN[0003] Received SIGTERM, exiting gracefully... source="main.go:334" INFO[0003] See you next time! source="main.go:341" INFO[0003] Stopping target manager... source="targetmanager.go:81" INFO[0003] Target manager stopped. source="targetmanager.go:93" INFO[0003] Stopping rule manager... source="manager.go:454" INFO[0003] Rule manager stopped. source="manager.go:460" INFO[0003] Stopping notification handler... source="notifier.go:471"

Rucknar · Aug 9, 2017

Just built and ran the dev-2.0 branch and no longer see this error, where as i do when running the beta0 build from dockerhub. Suspect it was fixed shortly after the beta was cut.

hiscal2015 · Aug 17, 2017

Upgraded to 2.0.0-beta.1, still have this issue.

mkjaer · Aug 20, 2017

I have this issue with 2.0.0-beta.2

Only tested on Ubuntu 17.04 with docker 17.06.1-ce

haosdent · Aug 22, 2017

Have this issue with 2.0.0-beta.2

gjflsl · Sep 4, 2017

@hiscal2015 When you runing with web.listen-address="0.0.0.0:9090" and you system disable ipv6,you will get this waring message.

aliasmee · Sep 10, 2017

I also encountered the same error message, but did not affect the normal use.
Follow-up can be detected at boot time ipv6 have wood enabled, if not enabled, no longer try to bind ipv6.

htdvisser · Sep 14, 2017

I created Pull Request #3174 that fixes this issue (at least, for me)

lock · 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.

gouthamve added kind/bug dev-2.0 labels Jul 30, 2017

htdvisser referenced this issue Sep 14, 2017
Closed
Fix loopback address for REST API gateway (v2) #3174

aliasmee referenced this issue Sep 28, 2017
Closed
grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp [::]:9090: connect: no route to host"; Reconnecting to {[::]:9090 <nil>} #3149

hiscal2015 closed this Dec 21, 2017

lock bot locked and limited conversation to collaborators Mar 23, 2019

prometheus/prometheus

[2.0 beta] addrConn.resetTransport failed to create client transport #3004

[2.0 beta] addrConn.resetTransport failed to create client transport #3004

hiscal2015 commented Jul 29, 2017

This comment has been minimized.

gouthamve commented Jul 30, 2017

gouthamve added kind/bug dev-2.0 labels Jul 30, 2017

This comment has been minimized.

vin33sh commented Aug 8, 2017

This comment has been minimized.

Rucknar commented Aug 9, 2017

This comment has been minimized.

hiscal2015 commented Aug 17, 2017

This comment has been minimized.

mkjaer commented Aug 20, 2017 •

edited

This comment has been minimized.

haosdent commented Aug 22, 2017

This comment has been minimized.

gjflsl commented Sep 4, 2017

This comment has been minimized.

aliasmee commented Sep 10, 2017

htdvisser referenced this issue Sep 14, 2017

Fix loopback address for REST API gateway (v2) #3174

This comment has been minimized.

htdvisser commented Sep 14, 2017

aliasmee referenced this issue Sep 28, 2017

grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp [::]:9090: connect: no route to host"; Reconnecting to {[::]:9090 <nil>} #3149

simonpasquier added a commit to simonpasquier/prometheus that referenced this issue Nov 28, 2017

juliusv added a commit that referenced this issue Dec 11, 2017

hiscal2015 closed this Dec 21, 2017

This comment has been minimized.

lock bot commented Mar 23, 2019

lock bot locked and limited conversation to collaborators Mar 23, 2019

prometheus/prometheus

Join GitHub today

[2.0 beta] addrConn.resetTransport failed to create client transport #3004

Comments

hiscal2015 commented Jul 29, 2017

This comment has been minimized.

gouthamve commented Jul 30, 2017

gouthamve added kind/bug dev-2.0 labels Jul 30, 2017

This comment has been minimized.

vin33sh commented Aug 8, 2017

This comment has been minimized.

Rucknar commented Aug 9, 2017

This comment has been minimized.

hiscal2015 commented Aug 17, 2017

This comment has been minimized.

mkjaer commented Aug 20, 2017 • edited

This comment has been minimized.

haosdent commented Aug 22, 2017

This comment has been minimized.

gjflsl commented Sep 4, 2017

This comment has been minimized.

aliasmee commented Sep 10, 2017

htdvisser referenced this issue Sep 14, 2017

Fix loopback address for REST API gateway (v2) #3174

This comment has been minimized.

htdvisser commented Sep 14, 2017

aliasmee referenced this issue Sep 28, 2017

grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp [::]:9090: connect: no route to host"; Reconnecting to {[::]:9090 <nil>} #3149

simonpasquier added a commit to simonpasquier/prometheus that referenced this issue Nov 28, 2017

juliusv added a commit that referenced this issue Dec 11, 2017

hiscal2015 closed this Dec 21, 2017

This comment has been minimized.

lock bot commented Mar 23, 2019

lock bot locked and limited conversation to collaborators Mar 23, 2019

mkjaer commented Aug 20, 2017 •

edited