This message was deleted.
# generala
adamant-kite-43734
02/22/2024, 10:29 PMThis message was deleted.
b
boundless-finland-89190
02/22/2024, 10:31 PMWhen I look at the conditions all I see is [Disconnected] Cluster agent is not connected.
boundless-finland-89190
02/22/2024, 10:35 PMI checked the agent running in the cattle-system namespace and the log is just repeating the following...
time="2024-02-22T21:56:12Z" level=info msg="Connecting to wss://<<RANCHER NODE>>/v3/connect/register with token starting with 5vnt2lvcd4xm525vsjjnjgcj9cs"time="2024-02-22T21:56:12Z" level=info msg="Connecting to proxy" url="wss://<<RANCHER NODE>>/v3/connect/register"time="2024-02-22T21:56:22Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp: lookup <<RANCHER NODE>>: i/o timeout"time="2024-02-22T21:56:22Z" level=error msg="Remotedialer proxy error" error="dial tcp: lookup <<RANCHER NODE>>: i/o timeout"boundless-finland-89190
02/22/2024, 10:35 PMAny ideas?
b
bulky-sunset-52084
02/23/2024, 2:57 AM
That error means the pod is having trouble talking back to Rancher. Make sure there isn't a firewall or something blocking the node from talking to the rancher ingress.
b
boundless-finland-89190
02/23/2024, 1:42 PMHi, @bulky-sunset-52084, I let it run overnight, and things are now connected; my guess is the Rancher node was busy. I don't have Rancher running HA since this is a test installation. When I move to production, I'll setup multiple nodes for an HA config.
🙌 1
b
bulky-sunset-52084
02/23/2024, 1:43 PM
Good to hear you got it running bud!
b
boundless-finland-89190
02/23/2024, 1:45 PMI'm also trying to deploy the monitoring, but that's not working. Do you have any guidance? I'm trying to deploy into the v1.23.17 cluster. Monitoring works on all of the other clusters.