Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

[ravijo]

Hi Josh,

Thanks a lot for your help.

Yes, the custom dialer helped to understand the actual error message (in my 
case the certificate is valid for the "hostname", but the client is using 
"localhost" to connect to the server).
After changing it, things started to work.

thanks.

On Friday, December 22, 2017 at 7:55:11 PM UTC-8, Josh Humphries wrote:
>
> Hi, Ravi,
> Yes, I understand. That is because grpc.Dial doesn't actually return an 
> error just because there are issues establishing socket connections -- it 
> asynchronously starts a client that will transparently retry dialing as 
> needed (possibly continuously dialing, with some backoff, depending on the 
> nature of the connection failure).
>
> While you can try to use dial options grpc.WithBlock() and 
> grpc.FailOnNonTempDialError(true), in my experience this still usually 
> results in only a timeout error from grpc.Dial. In order to get visibility 
> into the actual errors, you need a custom dialer that also performs the TLS 
> handshake so that you can adequately capture the error (log it or 
> otherwise). This will likely shed much light on why all connections are 
> always in transient failure state.
>
>
>
> 
> *Josh Humphries*
> jh...@bluegosling.com 
>
> On Fri, Dec 22, 2017 at 8:56 PM, Ravi Jonnadula  > wrote:
>
>> Hi Josh,
>>
>> Thanks for sharing your thoughts.
>>
>> In my case, grpc.Dial is successful, there is no error for this call.
>> The error occurs when the rpc call is invoked.
>>
>>
>> On Fri, Dec 22, 2017 at 3:42 PM, Josh Humphries > > wrote:
>>
>>> If you use a custom dialer, specify the "insecure" dial option in the 
>>> GRPC client, but then handle TLS in your custom dialer, you can get at the 
>>> actual error messages that are causing the transport failure.
>>>
>>> Here's an example I used in a command-line tool, where I wanted to be 
>>> able to show users a good error message when there was a TLS issue 
>>> preventing things from working:
>>> https://github.com/fullstorydev/grpcurl/blob/master/grpcurl.go#L916
>>>
>>> I've considered filing a bug with the grpc-go project about this. The 
>>> ClientConn has information about the actual errors that cause the SubConn 
>>> transient failure, but provide no API to access it (like for logging/error 
>>> reporting): 
>>> https://github.com/grpc/grpc-go/blob/master/clientconn.go#L989.
>>>
>>>
>>>
>>> 
>>> *Josh Humphries*
>>> jh...@bluegosling.com 
>>>
>>> On Fri, Dec 22, 2017 at 2:08 PM, Ravi  
>>> wrote:
>>>
 Hi Yufeng,

 My server side code exactly like yours.
 My certificates and keys are fine, because when I plug them into 
 example route_guide code (grpc-go/examples/route_guide) they work.

 My server-client logic is also fine without certificates. The moment I 
 enable certificates, I get this error:
 rpc error: code = Unavailable desc = all SubConns are in 
 TransientFailure


 My Server side code:

 lis, err := net.Listen("tcp", port)
 if err != nil {
 return fmt.Errorf("Failed to listen: %s", err)
 }
 creds, err := credentials.NewServerTLSFromFile(certFile, keyFile)
 if err != nil {
 return fmt.Errorf("could not load keys: %s", err)
 }

 opts := []grpc.ServerOption{grpc.Creds(creds)}
 grpcServer := grpc.NewServer(opts...)

 pb.RegisterHelloServer(grpcServer, newServer())

 if err := grpcServer.Serve(lis); err != nil {
 return fmt.Errorf("Failed to start Hello Server: %s", err)
 }


 My Client side code:
 

   
 creds, err := credentials.NewClientTLSFromFile(certFile, "")
 if err != nil {
 log.Fatalf("could not load cert: %s", err)
 }
 conn, err = grpc.Dial(port, grpc.WithTransportCredentials(creds))
 if err != nil {
 log.Fatalf("Failed to connect to server: %s", err)
 return
 }

 defer conn.Close()
 c := pb.NewHelloClient(conn)

 r, err := c.HelloServer(context.Background(), {Name: 
 "Myname", Id:10})




 On Thursday, December 21, 2017 at 7:18:11 PM UTC-8, Yufeng Liu wrote:
>
> Hi Ravijo,
>
> I have fixed the issue, I just change the service code below. The cert 
> is bought normal cert from “https://www.rapidssl.com/“. 
>
> certificate, err := credentials.NewServerTLSFromFile(conf.CRT, 
> conf.KEY)
> if err != nil {
> log.Errorf("could not load server key pair: %s", err)
> }
>
> I don’t know that can help you anything.
>
>
> On 22 Dec 2017, at 10:57 AM, rav...@gmail.com wrote:
>
> How to fix / debug such issue?
>
> I keep getting this error:
> rpc error: code = Unavailable desc = all SubConns are in 
> TransientFailure

Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

[Josh Humphries]

Hi, Ravi,
Yes, I understand. That is because grpc.Dial doesn't actually return an
error just because there are issues establishing socket connections -- it
asynchronously starts a client that will transparently retry dialing as
needed (possibly continuously dialing, with some backoff, depending on the
nature of the connection failure).

While you can try to use dial options grpc.WithBlock() and
grpc.FailOnNonTempDialError(true), in my experience this still usually
results in only a timeout error from grpc.Dial. In order to get visibility
into the actual errors, you need a custom dialer that also performs the TLS
handshake so that you can adequately capture the error (log it or
otherwise). This will likely shed much light on why all connections are
always in transient failure state.




*Josh Humphries*
jh...@bluegosling.com

On Fri, Dec 22, 2017 at 8:56 PM, Ravi Jonnadula  wrote:

> Hi Josh,
>
> Thanks for sharing your thoughts.
>
> In my case, grpc.Dial is successful, there is no error for this call.
> The error occurs when the rpc call is invoked.
>
>
> On Fri, Dec 22, 2017 at 3:42 PM, Josh Humphries 
> wrote:
>
>> If you use a custom dialer, specify the "insecure" dial option in the
>> GRPC client, but then handle TLS in your custom dialer, you can get at the
>> actual error messages that are causing the transport failure.
>>
>> Here's an example I used in a command-line tool, where I wanted to be
>> able to show users a good error message when there was a TLS issue
>> preventing things from working:
>> https://github.com/fullstorydev/grpcurl/blob/master/grpcurl.go#L916
>>
>> I've considered filing a bug with the grpc-go project about this. The
>> ClientConn has information about the actual errors that cause the SubConn
>> transient failure, but provide no API to access it (like for logging/error
>> reporting): https://github.com/grpc/grpc-go/blob/master/clie
>> ntconn.go#L989.
>>
>>
>>
>> 
>> *Josh Humphries*
>> jh...@bluegosling.com
>>
>> On Fri, Dec 22, 2017 at 2:08 PM, Ravi  wrote:
>>
>>> Hi Yufeng,
>>>
>>> My server side code exactly like yours.
>>> My certificates and keys are fine, because when I plug them into example
>>> route_guide code (grpc-go/examples/route_guide) they work.
>>>
>>> My server-client logic is also fine without certificates. The moment I
>>> enable certificates, I get this error:
>>> rpc error: code = Unavailable desc = all SubConns are in
>>> TransientFailure
>>>
>>>
>>> My Server side code:
>>>
>>> lis, err := net.Listen("tcp", port)
>>> if err != nil {
>>> return fmt.Errorf("Failed to listen: %s", err)
>>> }
>>> creds, err := credentials.NewServerTLSFromFile(certFile, keyFile)
>>> if err != nil {
>>> return fmt.Errorf("could not load keys: %s", err)
>>> }
>>>
>>> opts := []grpc.ServerOption{grpc.Creds(creds)}
>>> grpcServer := grpc.NewServer(opts...)
>>>
>>> pb.RegisterHelloServer(grpcServer, newServer())
>>>
>>> if err := grpcServer.Serve(lis); err != nil {
>>> return fmt.Errorf("Failed to start Hello Server: %s", err)
>>> }
>>>
>>>
>>> My Client side code:
>>> 
>>>
>>>
>>> creds, err := credentials.NewClientTLSFromFile(certFile, "")
>>> if err != nil {
>>> log.Fatalf("could not load cert: %s", err)
>>> }
>>> conn, err = grpc.Dial(port, grpc.WithTransportCredentials(creds))
>>> if err != nil {
>>> log.Fatalf("Failed to connect to server: %s", err)
>>> return
>>> }
>>>
>>> defer conn.Close()
>>> c := pb.NewHelloClient(conn)
>>>
>>> r, err := c.HelloServer(context.Background(), {Name:
>>> "Myname", Id:10})
>>>
>>>
>>>
>>>
>>> On Thursday, December 21, 2017 at 7:18:11 PM UTC-8, Yufeng Liu wrote:

 Hi Ravijo,

 I have fixed the issue, I just change the service code below. The cert
 is bought normal cert from “https://www.rapidssl.com/“.

 certificate, err := credentials.NewServerTLSFromFile(conf.CRT,
 conf.KEY)
 if err != nil {
 log.Errorf("could not load server key pair: %s", err)
 }

 I don’t know that can help you anything.


 On 22 Dec 2017, at 10:57 AM, rav...@gmail.com wrote:

 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 

Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

[Ravi Jonnadula]

Hi Josh,

Thanks for sharing your thoughts.

In my case, grpc.Dial is successful, there is no error for this call.
The error occurs when the rpc call is invoked.


On Fri, Dec 22, 2017 at 3:42 PM, Josh Humphries 
wrote:

> If you use a custom dialer, specify the "insecure" dial option in the GRPC
> client, but then handle TLS in your custom dialer, you can get at the
> actual error messages that are causing the transport failure.
>
> Here's an example I used in a command-line tool, where I wanted to be able
> to show users a good error message when there was a TLS issue preventing
> things from working:
> https://github.com/fullstorydev/grpcurl/blob/master/grpcurl.go#L916
>
> I've considered filing a bug with the grpc-go project about this. The
> ClientConn has information about the actual errors that cause the SubConn
> transient failure, but provide no API to access it (like for logging/error
> reporting): https://github.com/grpc/grpc-go/blob/master/clientconn.go#L989
> .
>
>
>
> 
> *Josh Humphries*
> jh...@bluegosling.com
>
> On Fri, Dec 22, 2017 at 2:08 PM, Ravi  wrote:
>
>> Hi Yufeng,
>>
>> My server side code exactly like yours.
>> My certificates and keys are fine, because when I plug them into example
>> route_guide code (grpc-go/examples/route_guide) they work.
>>
>> My server-client logic is also fine without certificates. The moment I
>> enable certificates, I get this error:
>> rpc error: code = Unavailable desc = all SubConns are in TransientFailure
>>
>>
>> My Server side code:
>>
>> lis, err := net.Listen("tcp", port)
>> if err != nil {
>> return fmt.Errorf("Failed to listen: %s", err)
>> }
>> creds, err := credentials.NewServerTLSFromFile(certFile, keyFile)
>> if err != nil {
>> return fmt.Errorf("could not load keys: %s", err)
>> }
>>
>> opts := []grpc.ServerOption{grpc.Creds(creds)}
>> grpcServer := grpc.NewServer(opts...)
>>
>> pb.RegisterHelloServer(grpcServer, newServer())
>>
>> if err := grpcServer.Serve(lis); err != nil {
>> return fmt.Errorf("Failed to start Hello Server: %s", err)
>> }
>>
>>
>> My Client side code:
>> 
>>
>>
>> creds, err := credentials.NewClientTLSFromFile(certFile, "")
>> if err != nil {
>> log.Fatalf("could not load cert: %s", err)
>> }
>> conn, err = grpc.Dial(port, grpc.WithTransportCredentials(creds))
>> if err != nil {
>> log.Fatalf("Failed to connect to server: %s", err)
>> return
>> }
>>
>> defer conn.Close()
>> c := pb.NewHelloClient(conn)
>>
>> r, err := c.HelloServer(context.Background(), {Name:
>> "Myname", Id:10})
>>
>>
>>
>>
>> On Thursday, December 21, 2017 at 7:18:11 PM UTC-8, Yufeng Liu wrote:
>>>
>>> Hi Ravijo,
>>>
>>> I have fixed the issue, I just change the service code below. The cert
>>> is bought normal cert from “https://www.rapidssl.com/“.
>>>
>>> certificate, err := credentials.NewServerTLSFromFile(conf.CRT, conf.KEY)
>>> if err != nil {
>>> log.Errorf("could not load server key pair: %s", err)
>>> }
>>>
>>> I don’t know that can help you anything.
>>>
>>>
>>> On 22 Dec 2017, at 10:57 AM, rav...@gmail.com wrote:
>>>
>>> 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, yuf...@chope.co 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.

Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

[Josh Humphries]

If you use a custom dialer, specify the "insecure" dial option in the GRPC
client, but then handle TLS in your custom dialer, you can get at the
actual error messages that are causing the transport failure.

Here's an example I used in a command-line tool, where I wanted to be able
to show users a good error message when there was a TLS issue preventing
things from working:
https://github.com/fullstorydev/grpcurl/blob/master/grpcurl.go#L916

I've considered filing a bug with the grpc-go project about this. The
ClientConn has information about the actual errors that cause the SubConn
transient failure, but provide no API to access it (like for logging/error
reporting): https://github.com/grpc/grpc-go/blob/master/clientconn.go#L989.




*Josh Humphries*
jh...@bluegosling.com

On Fri, Dec 22, 2017 at 2:08 PM, Ravi  wrote:

> Hi Yufeng,
>
> My server side code exactly like yours.
> My certificates and keys are fine, because when I plug them into example
> route_guide code (grpc-go/examples/route_guide) they work.
>
> My server-client logic is also fine without certificates. The moment I
> enable certificates, I get this error:
> rpc error: code = Unavailable desc = all SubConns are in TransientFailure
>
>
> My Server side code:
>
> lis, err := net.Listen("tcp", port)
> if err != nil {
> return fmt.Errorf("Failed to listen: %s", err)
> }
> creds, err := credentials.NewServerTLSFromFile(certFile, keyFile)
> if err != nil {
> return fmt.Errorf("could not load keys: %s", err)
> }
>
> opts := []grpc.ServerOption{grpc.Creds(creds)}
> grpcServer := grpc.NewServer(opts...)
>
> pb.RegisterHelloServer(grpcServer, newServer())
>
> if err := grpcServer.Serve(lis); err != nil {
> return fmt.Errorf("Failed to start Hello Server: %s", err)
> }
>
>
> My Client side code:
> 
>
>
> creds, err := credentials.NewClientTLSFromFile(certFile, "")
> if err != nil {
> log.Fatalf("could not load cert: %s", err)
> }
> conn, err = grpc.Dial(port, grpc.WithTransportCredentials(creds))
> if err != nil {
> log.Fatalf("Failed to connect to server: %s", err)
> return
> }
>
> defer conn.Close()
> c := pb.NewHelloClient(conn)
>
> r, err := c.HelloServer(context.Background(), {Name:
> "Myname", Id:10})
>
>
>
>
> On Thursday, December 21, 2017 at 7:18:11 PM UTC-8, Yufeng Liu wrote:
>>
>> Hi Ravijo,
>>
>> I have fixed the issue, I just change the service code below. The cert is
>> bought normal cert from “https://www.rapidssl.com/“.
>>
>> certificate, err := credentials.NewServerTLSFromFile(conf.CRT, conf.KEY)
>> if err != nil {
>> log.Errorf("could not load server key pair: %s", err)
>> }
>>
>> I don’t know that can help you anything.
>>
>>
>> On 22 Dec 2017, at 10:57 AM, rav...@gmail.com wrote:
>>
>> 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, yuf...@chope.co 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 a topic in the
>> Google Groups "grpc.io" group.
>> To unsubscribe from this topic, visit https://groups.google.co
>> m/d/topic/grpc-io/yCUwuHycNWk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> grpc-io+u...@googlegroups.com.
>> To post to this group, send email to 

Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

[Ravi]

Hi Yufeng,

My server side code exactly like yours.
My certificates and keys are fine, because when I plug them into example 
route_guide code (grpc-go/examples/route_guide) they work.

My server-client logic is also fine without certificates. The moment I 
enable certificates, I get this error:
rpc error: code = Unavailable desc = all SubConns are in TransientFailure


My Server side code:
   
lis, err := net.Listen("tcp", port)
if err != nil {
return fmt.Errorf("Failed to listen: %s", err)
}
creds, err := credentials.NewServerTLSFromFile(certFile, keyFile)
if err != nil {
return fmt.Errorf("could not load keys: %s", err)
}

opts := []grpc.ServerOption{grpc.Creds(creds)}
grpcServer := grpc.NewServer(opts...)

pb.RegisterHelloServer(grpcServer, newServer())

if err := grpcServer.Serve(lis); err != nil {
return fmt.Errorf("Failed to start Hello Server: %s", err)
}


My Client side code:


  
creds, err := credentials.NewClientTLSFromFile(certFile, "")
if err != nil {
log.Fatalf("could not load cert: %s", err)
}
conn, err = grpc.Dial(port, grpc.WithTransportCredentials(creds))
if err != nil {
log.Fatalf("Failed to connect to server: %s", err)
return
}

defer conn.Close()
c := pb.NewHelloClient(conn)

r, err := c.HelloServer(context.Background(), {Name: "Myname"
, Id:10})




On Thursday, December 21, 2017 at 7:18:11 PM UTC-8, Yufeng Liu wrote:
>
> Hi Ravijo,
>
> I have fixed the issue, I just change the service code below. The cert is 
> bought normal cert from “https://www.rapidssl.com/“. 
>
> certificate, err := credentials.NewServerTLSFromFile(conf.CRT, conf.KEY)
> if err != nil {
> log.Errorf("could not load server key pair: %s", err)
> }
>
> I don’t know that can help you anything.
>
>
> On 22 Dec 2017, at 10:57 AM, rav...@gmail.com  wrote:
>
> 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, yuf...@chope.co 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 a topic in the 
> Google Groups "grpc.io" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/grpc-io/yCUwuHycNWk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> grpc-io+u...@googlegroups.com .
> To post to this group, send email to grp...@googlegroups.com 
> .
> 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.
>
>
>

-- 
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 grpc-io+unsubscr...@googlegroups.com.
To post to this group, send email to grpc-io@googlegroups.com.
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/92a3a883-14af-4c00-a0c5-90ad04d1ee29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [grpc-io] Re: Getting "all SubConns are in TransientFailure" sending to local grpc service.

[Yufeng Liu]

Hi Ravijo,

I have fixed the issue, I just change the service code below. The cert is 
bought normal cert from “https://www.rapidssl.com/“. 

certificate, err := credentials.NewServerTLSFromFile(conf.CRT, conf.KEY)
if err != nil {
log.Errorf("could not load server key pair: %s", err)
}

I don’t know that can help you anything.


> On 22 Dec 2017, at 10:57 AM, rav...@gmail.com wrote:
> 
> 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, yuf...@chope.co <> 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 a topic in the Google 
> Groups "grpc.io" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/grpc-io/yCUwuHycNWk/unsubscribe 
> .
> To unsubscribe from this group and all its topics, send an email to 
> grpc-io+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to grpc-io@googlegroups.com 
> .
> 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 
> .

-- 
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 grpc-io+unsubscr...@googlegroups.com.
To post to this group, send email to grpc-io@googlegroups.com.
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/CD6E0D17-DFF7-4BF5-9521-AA6427B6DB0F%40chope.co.
For more options, visit https://groups.google.com/d/optout.