dapr / dapr

Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
https://dapr.io
Apache License 2.0
23.58k stars 1.85k forks source link

unable to connect to Dapr port 3500 #7776

Open kiranagalpady83 opened 1 month ago

kiranagalpady83 commented 1 month ago

Hello All, We have deployed Dapr to our Cluster, and all the Dapr control plane components are installed. When we start the application by enabling annotations to inject the Dapr sidecar in the application, I don't see it being injected. When I check the application pod log, I found the following error: the application pod is unable to connect to Dapr port 3500. Could you please help if you have already deployed Dapr in a kubernetes cluster? I have attached the Dapr deployment file and the application deployment file. Please review and update me if I missed any configuration in our cluster. App Pod log: Health check on http://127.0.0.1:3500/v1.0/healthz/outbound failed: [Errno 111] Connection refused Health check on http://127.0.0.1:3500/v1.0/healthz/outbound failed: [Errno 111] Connection refused Health check on http://127.0.0.1:3500/v1.0/healthz/outbound failed: [Errno 111] Connection refused Health check on http://127.0.0.1:3500/v1.0/healthz/outbound failed: [Errno 111] Connection refused Health check on http://127.0.0.1:3500/v1.0/healthz/outbound failed: [Errno 111] Connection refused Traceback (most recent call last): File "/app/workflow_api.py", line 28, in dapr_client = DaprClient() File "/home/1000/.local/lib/python3.9/site-packages/dapr/clients/init.py", line 81, in init super().init(address, interceptors, max_grpc_message_length) File "/home/1000/.local/lib/python3.9/site-packages/dapr/clients/grpc/client.py", line 131, in init DaprHealth.wait_until_ready() File "/home/1000/.local/lib/python3.9/site-packages/dapr/clients/health.py", line 47, in wait_until_ready raise TimeoutError(f'Dapr health check timed out, after {timeout}.') TimeoutError: Dapr health check timed out, after 60.

pyjads commented 3 weeks ago

Which Dapr version are you using? Could you try version 1.12.1. I was able to resolve the error by using version 1.12.1