edgemesh icon indicating copy to clipboard operation
edgemesh copied to clipboard

Edgemesh-agent cannot connect to Edgemesh-server tunnel server

Open vickiyan opened this issue 4 years ago • 5 comments

What happened: edgemesh-agent cannot establish connection with edgemesh-server successfully. error is as below: 366867407289700629

What you expected to happen: edgemesh-agent can establish connection successfully. How to reproduce it (as minimally and precisely as possible): kubeedge 1.8.2 version + edgemesh 1.8.0 version , edge and master nodes are in private network without internet access.

Anything else we need to know?: master node ip :30.23.5.58 ,it's public ip also. edgenode ip is 30.23.6.135 kubectl get node and edgemesh-server-cfg cm as below: 591244637289384269

edgenode could telnet tunnelserver 20004 successfully, screenshot as below: 500617650170106220

edgenode ifconfig screenshot 447534892447986727

master node ifconfig screenshot 116870794476073899

edgemesh server pod logs screenshot: 815335423273890661

Environment:

  • EdgeMesh version: 1.8.0 version

  • Kubernetes version (use kubectl version): 1.15.2

  • KubeEdge version(e.g. cloudcore --version and edgecore --version): 1.8.2

  • Cloud nodes Environment:
    • Hardware configuration (e.g. lscpu):
    • OS (e.g. cat /etc/os-release): centos 7.6
    • Kernel (e.g. uname -a):
    • Go version (e.g. go version):
    • Others:
  • Edge nodes Environment:
    • edgecore version (e.g. edgecore --version):
    • Hardware configuration (e.g. lscpu):
    • OS (e.g. cat /etc/os-release):
    • Kernel (e.g. uname -a):
    • Go version (e.g. go version):
    • Others:

vickiyan avatar Nov 18 '21 07:11 vickiyan

感觉和下面的问题有点像 https://github.com/libp2p/go-libp2p/issues/968

vickiyan avatar Nov 21 '21 09:11 vickiyan

Do you try to connect 30.23.5.58:40001 in edgemesh-agent container? And it seems that the edgemesh-agent do not have the permission to edit the /etc/resolv.conf? How do you install the edgemesh? Helm?

kason-huang avatar Nov 22 '21 01:11 kason-huang

/assign

kason-huang avatar Nov 22 '21 01:11 kason-huang

I have a similar problem with edgemesh v1.8.0.

I have a cluster with 4 edge nodes and 1 cloud node. In my case, only the edgemesh-agent running on the cloud node is not able to connect to the edgemesh-server with the following error:

W0322 09:55:59.742042       1 tunnel.go:28] Connection between agent and server [/ip4/7.182.9.110/tcp/10005 /ip4/127.0.0.1/tcp/10005 /ip4/7.182.9.110/tcp/10005] is not established, try connect
I0322 09:55:59.742101       1 tunnel.go:31] Tunnel agent connecting to tunnel server
W0322 09:55:59.742769       1 tunnel.go:34] Connect to server err: failed to dial QmPiD14D2xtBGtGgjA7C7k396M4NZAjrqJuvTm5EXwQuVf: all dials failed
  * [/ip4/7.182.9.110/tcp/10005] failed to negotiate security protocol: protocol not supported
  * [/ip4/127.0.0.1/tcp/10005] failed to negotiate security protocol: protocol not supported

The edgemesh-agents running on the edge nodes can connect without issues.

vcozzolino avatar Mar 22 '22 08:03 vcozzolino

@vcozzolino Seems to be using a different version of edgemesh-agent. You can checkout every edgemesh-agent image ID.

Poorunga avatar Apr 14 '22 09:04 Poorunga