How to fix / debug such issue?

I keep getting this error:
rpc error: code = Unavailable desc = all SubConns are in TransientFailure

The same client - server logic works fine if I remove the TLS credentials 
... any help to resolve would be appreciated!


On Monday, December 4, 2017 at 5:44:41 AM UTC-8, Paul Breslin wrote:
>
> We didn't really solve it but discovered a work-around. For some reason if 
> I start my services in one script and then run the tests from a separate 
> script it seems to work fine. So it may have to do with some extra delay 
> time between starting the containers and then attempting to run the client 
> code.
>
>
> On Monday, December 4, 2017 at 7:22:22 AM UTC-5, [email protected] wrote:
>>
>> Hi Paul,
>>
>> can i ask did you have solved the issue. i have the same problem..
>>
>> On Tuesday, November 14, 2017 at 5:36:19 AM UTC+8, Paul Breslin wrote:
>>>
>>>
>>> I'm running local grpc services under Docker for Mac. All has been fine 
>>> but today I started getting intermittent failures:
>>> rpc error: code = Unavailable desc = all SubConns are in TransientFailure
>>> when my test code sends a message to one of the services. The test code 
>>> also runs inside a docker container.
>>>
>>> Sometime restarting the docker daemon would make this go away but for 
>>> some reason the problem is now happening consistently.
>>>
>>> I've tried updating to the latest stable Docker for Mac and updating to 
>>> the current grpc release code.
>>>
>>> I'm stuck - not sure what to try next. We're currently using: go version 
>>> go1.8.3 linux/amd64
>>>
>>> Suggestions are welcome.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/44f304ae-3d12-49ce-9931-0b8608be6a27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to