Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to connect to Dapr port 3500 #7776

Closed
kiranagalpady83 opened this issue May 31, 2024 · 3 comments
Closed

unable to connect to Dapr port 3500 #7776

kiranagalpady83 opened this issue May 31, 2024 · 3 comments
Labels
kind/bug Something isn't working stale Issues and PRs without response

Comments

@kiranagalpady83
Copy link

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.

@kiranagalpady83 kiranagalpady83 added the kind/bug Something isn't working label May 31, 2024
@pyjads
Copy link

pyjads commented Jun 18, 2024

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

@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale Issues and PRs without response label Aug 17, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically closed because it has not had activity in the last 67 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

@dapr-bot dapr-bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working stale Issues and PRs without response
Projects
None yet
Development

No branches or pull requests

3 participants