assistant_sdk failed, error: lame client channel

[njust-wxd]

hi, I get a error when Start run_assistant:
wxd@suntec:~/assistant-sdk-cpp$ ./run_assistant --audio_input ./resources/weather_in_mountain_view.raw --credentials_file ./credentials.json --credentials_type USER_ACCOUNT
assistant_sdk robots_pem:
assistant_sdk CreateCustomChannel(embeddedassistant.googleapis.com:443, creds, arg)

E0223 16:30:13.280134655 398 resolver_registry.cc:111] don't know how to resolve 'embeddedassistant.googleapis.com:443' or 'dns:///embeddedassistant.googleapis.com:443'
E0223 16:30:13.280234059 398 resolver_registry.cc:111] don't know how to resolve 'embeddedassistant.googleapis.com:443' or 'dns:///embeddedassistant.googleapis.com:443'
E0223 16:30:13.280285295 398 resolver_registry.cc:111] don't know how to resolve 'dns:///embeddedassistant.googleapis.com:443' or 'dns:///dns:///embeddedassistant.googleapis.com:443'
E0223 16:30:13.280332102 398 channel.cc:90] channel stack builder failed: {"created":"@1519374613.280306935","description":"resolver creation failed","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":769}
assistant_sdk wrote first request: config { audio_in_config { encoding: LINEAR16 sample_rate_hertz: 16000 } audio_out_config { encoding: LINEAR16 sample_rate_hertz: 16000 } converse_state { context { third_party_context: "{'current_channel': 'News'}" } } }
AudioOutputALSA Start() succeeded
assistant_sdk waiting for response ...
AudioOutputALSA Stop() succeeded
assistant_sdk failed, error: lame client channel
terminate called without an active exception

[Fleker]

don't know how to resolve 'embeddedassistant.googleapis.com:443'

This looks like a connectivity issue

[njust-wxd]

hi, this is the result of the ping and telnet command:
wxd@suntec:/assistant-sdk-cpp$ telnet embeddedassistant.googleapis.com 443
Trying 172.217.160.74...
Connected to googleapis.l.google.com.
Escape character is '^]'.
Connection closed by foreign host.
wxd@suntec:/assistant-sdk-cpp$ ping embeddedassistant.googleapis.com
PING googleapis.l.google.com (172.217.160.74) 56(84) bytes of data.
64 bytes from tsa01s09-in-f10.1e100.net (172.217.160.74): icmp_seq=1 ttl=32 time=525 ms
64 bytes from tsa01s09-in-f10.1e100.net (172.217.160.74): icmp_seq=2 ttl=32 time=535 ms
64 bytes from tsa01s09-in-f10.1e100.net (172.217.160.74): icmp_seq=3 ttl=32 time=527 ms
64 bytes from tsa01s09-in-f10.1e100.net (172.217.160.74): icmp_seq=4 ttl=32 time=530 ms
64 bytes from tsa01s09-in-f10.1e100.net (172.217.160.74): icmp_seq=5 ttl=32 time=530 ms
64 bytes from tsa01s09-in-f10.1e100.net (172.217.160.74): icmp_seq=6 ttl=32 time=536 ms
64 bytes from tsa01s09-in-f10.1e100.net (172.217.160.74): icmp_seq=7 ttl=32 time=528 ms
^C
--- googleapis.l.google.com ping statistics ---
8 packets transmitted, 7 received, 12% packet loss, time 7000ms
rtt min/avg/max/mdev = 525.030/530.642/536.057/3.804 ms