Skip to content
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.

etcdserver/api/v3rpc: grpc: addrConn.resetTransport failed to create client transport #340

Open
mthenw opened this issue Oct 27, 2017 · 3 comments

Comments

@mthenw
Copy link
Contributor

mthenw commented Oct 27, 2017

This is a Bug Report

When etcd client (libkv) cannot connect to etcd instance event gateway logs following messages:

2017-10-27 14:59:03.206243 I | etcdserver/api/v3rpc: grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:2379: getsockopt: connection refused"; Reconnecting to {127.0.0.1:2379 <nil>}
2017-10-27 14:59:04.207386 I | etcdserver/api/v3rpc: grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:2379: getsockopt: connection refused"; Reconnecting to {127.0.0.1:2379 <nil>}

It's known issue cause by grpc-go impl that shouldn't log to stdout/stderr: grpc/grpc-go#1044.

Another issue is that even though we silence most logs from etcd above logs are still outputted.

@mthenw
Copy link
Contributor Author

mthenw commented Oct 27, 2017

I reported this issue in etcd repo etcd-io/etcd#8778.

@fargozhu
Copy link

fargozhu commented Nov 8, 2018

and this message is related with which scenarios? Is there a root cause for it? I start seeing them and I can see that no event is . triggered anymore (which makes sense).

@mthenw
Copy link
Contributor Author

mthenw commented Nov 8, 2018

@fargozhu it happens when EG instance cannot connect to etcd.

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

No branches or pull requests

2 participants