c++ client: Handshaker factory creation failed with TSI_INVALID_ARGUMENT

399 views
Skip to first unread message

sundar ramamoorthy

unread,
Apr 8, 2021, 2:56:53 AM4/8/21
to grpc.io
Hi,

I am seeing an issue where a c++ client is not able to connect to the server from one app but it is able to from a different app on the same VM. 

In the working case, in netstat, I can see the right port: 
tcp6 0 0 GRPC-Secure-Test-:58770 xx.xx.xx.xx:8888 ESTABLISHED 
but in the non-working case, I always see: 
tcp6 0 1 GRPC-Secure-Test-:33222 xx.xx.xx.xx:http SYN_SENT 

I am calling the client API from both the apps in the same way. why would the port be set differently than what I have specified in create Channel?? 

Thanks,
Sundar

sundar ramamoorthy

unread,
Apr 8, 2021, 3:44:08 AM4/8/21
to grpc.io
Sorry, the netstat info. is incorrect. please ignore that. I am still seeing the issue where client is not able to connect to the server from two different apps running on the same VM. 


--
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/ANv8Sp-kIkI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to grpc-io+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/2c0c11f8-f4b6-4d7d-bb2a-a89aaec609bbn%40googlegroups.com.

sundar ramamoorthy

unread,
Apr 8, 2021, 4:49:03 AM4/8/21
to grpc.io

I0408 08:38:10.927269051 4989 ssl_transport_security.cc:908] Invalid nullptr argument to |tsi_set_min_and_max_tls_versions|.
E0408 08:38:10.927316013 4989 ssl_security_connector.cc:116] Handshaker factory creation failed with TSI_INVALID_ARGUMENT.
E0408 08:38:10.927351125 4989 secure_channel_create.cc:107] Failed to create secure subchannel for secure name 'securerelayserver.westus2.cloudapp.azure.com:8888'
E0408 08:38:10.927563105 4989 secure_channel_create.cc:49] Failed to create channel args during subchannel creation.

looks like the ssl_context is null in the non working case, any suggestions on how I can fix the issue?

Reply all
Reply to author
Forward
0 new messages