Replies: 4 comments 1 reply
-
Hi, default redis address is argocd-redis:6379 or you can override it inside
Could you please check that redis is up and running for you? |
Beta Was this translation helpful? Give feedback.
-
+1 I have exactly the same error using the latest argocd helm chart version... any redis connection timeouts from any pod. I have no notwork policies or other restrictions |
Beta Was this translation helpful? Give feedback.
-
I got the same error with
|
Beta Was this translation helpful? Give feedback.
-
I restarted argo-cd-dex deployment, no joy. I would guess the argo-cd-server deployment restart fixed based on the logs. It looks like as if once redis is down and comes back online then argo-cd-server can not recconnect to it. For redis I use existing secret with this config: redis:
auth:
existingSecret: argocd-passwords
existingSecretPasswordKey: redis-password With the helm chart bitnami/argo-cd 6.0.14 https://artifacthub.io/packages/helm/bitnami/argo-cd/6.0.14 Argo CD v2.10.8+37b1cf5 |
Beta Was this translation helpful? Give feedback.
-
Can any body help to resolve this error, this error is comming after redploying redis pod. Sync is failing
ComparisonError: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp 10.43.15.14:8081: connect: connection timed out"
Below error is on argo-cd server.
evel=warning msg="Failed to resync revoked tokens. retrying again in 1 minute: dial tcp 10.43.17.160:6379: i/o timeout
Beta Was this translation helpful? Give feedback.
All reactions