-
Notifications
You must be signed in to change notification settings - Fork 252
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
r2r container failed to become healthy. #1117
Comments
Can you share the logs in your R2R server container (should be marked r2r-r1r-1 or similar.) This can happen if it fails to respond to a health check, so I expect that it's binding somewhere. |
This was happening for me last night with v3.1.19, when I upgraded to v3.1.21 by |
@linuxreitt - We are pushing a correct fix right now for the other github issue that you brought to our attention. Can you follow what @br00t4c has advised and try updating your R2R version? If the error persists we will investigate the hatchet configuration. |
I have upgraded r2r to the very latest version, I still have issues. 2024-09-11 20:07:45,465 - INFO - core.main.app_entry - Environment CONFIG_PATH: /usr/local/lib/python3.10/site-packages/pydantic/_internal/_config.py:341: UserWarning: Valid config keys have changed in V2:
/usr/local/lib/python3.10/site-packages/pydantic/_internal/_config.py:341: UserWarning: Valid config keys have changed in V2:
/usr/local/lib/python3.10/site-packages/pydantic/_internal/_config.py:341: UserWarning: Valid config keys have changed in V2:
|
Has anyone, any ideas for this? Have any users who have successfully built with docker any advise on changes they may have made? The project itself seems fantastic but I feel the docker implementation completely lets the project down, I'd love to spend more time trying to figure out what the issue is but my feeling is if the devs can't then I have no chance and so I'll have to find a different solution. |
Same Started serving multiple time using: |
Describe the bug
After setting up the Hatchet engine using Docker Compose, the hatchet-engine service is marked as unhealthy, and I receive a "connection refused" error when attempting to connect to 172.17.0.1:7077. The alias host.docker.internal seems to be misconfigured within the docker-compose network, causing issues with the hatchet-engine healthcheck and service communication.
To Reproduce
Steps to reproduce the behavior:
2.R2R now runs on port 7272 by default!
Pulling Docker images...
[+] Pulling 22/22
✔ setup-token Skipped - Image is already being pulled by hatchet-setup-config 0.0s
✔ neo4j Pulled 1.9s
✔ r2r-dashboard Pulled 2.1s
✔ hatchet-dashboard Pulled 1.3s
✔ hatchet-rabbitmq Pulled 1.9s
✔ postgres Pulled 2.0s
✔ r2r Pulled 1.9s
✔ hatchet-setup-config Pulled 35.8s
✔ c6a83fedfae6 Already exists 0.0s
✔ a7adfaf8acb2 Already exists 0.0s
✔ 2e1aee94ff63 Pull complete 34.1s
✔ 0cc9b3b5c238 Pull complete 34.1s
✔ abcedb1bd74f Pull complete 34.4s
✔ hatchet-engine Pulled 1.5s
✔ traefik Pulled 2.1s
✔ hatchet-migration Pulled 37.6s
✔ 5a08e4bb3ddd Pull complete 33.6s
✔ 8a86e811c654 Pull complete 36.0s
✔ 2bc6a5dc2d85 Pull complete 36.0s
✔ c5978cfa4652 Pull complete 36.0s
✔ a6d3ef985032 Pull complete 36.0s
✔ hatchet-api Pulled 1.5s
Starting Docker Compose setup...
[+] Running 12/12
✔ Container r2r-hatchet-rabbitmq-1 Healthy 11.8s
✔ Container r2r-traefik-1 Started 0.6s
✔ Container r2r-hatchet-dashboard-1 Started 0.5s
✔ Container r2r-postgres-1 Healthy 13.8s
✔ Container r2r-r2r-dashboard-1 Started 0.6s
✔ Container r2r-neo4j-1 Healthy 21.8s
✔ Container r2r-hatchet-migration-1 Exited 12.1s
✔ Container r2r-hatchet-setup-config-1 Exited 12.8s
✔ Container r2r-hatchet-api-1 Started 13.1s
✔ Container r2r-hatchet-engine-1 Started 13.1s
✔ Container r2r-setup-token-1 Exited 13.6s
✔ Container r2r-r2r-1 Started 21.7s
Waiting for all services to become healthy...
Timeout waiting for r2r to be healthy.
r2r container failed to become healthy.
Navigating to R2R application at http://localhost:7273.
R2R$ Opening in existing browser session.
Expected behavior
Healty containers, ability to access webui.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: