-
Notifications
You must be signed in to change notification settings - Fork 3k
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
OPAHealthCheck Internal Server Error for url: http://opa:8181/health?bundles #8451
Comments
Please attach full log from cvat_server container |
`docker logs cvat_server WARNINGS: 163 static files copied to '/home/django/static'. WARNINGS: 2024-09-17 21:35:51,546 DEBG 'smokescreen' stderr output: 2024-09-17 21:35:51,549 DEBG 'uvicorn-0' stderr output: 2024-09-17 21:35:51,550 DEBG fd 14 closed, stopped monitoring <POutputDispatcher at 140408520552560 for <Subprocess at 140408520541808 with name nginx-0 in state STARTING> (stderr)> 2024-09-17 21:35:51,553 DEBG 'uvicorn-1' stderr output: 2024-09-17 21:35:51,556 DEBG 'uvicorn-1' stderr output: 2024-09-17 21:35:51,558 DEBG 'uvicorn-0' stderr output: 2024-09-17 21:35:51,560 DEBG 'uvicorn-1' stderr output: 2024-09-17 21:35:52,562 INFO success: nginx-0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) |
Actions before raising this issue
Steps to Reproduce
CVAT Version:
CVAT:DEV
Been running this for awhile now. Only decided to rebuild the container and since then this appears to be happening.
Error:
OPAHealthCheck ... unknown error: 500 Server Error: Internal Server Error for url: http://opa:8181/health?bundles
Command used to build:
sudo -E docker compose -f docker-compose.yml -f docker-compose.external_db.yml -f components/serverless/docker-compose.serverless.yml -f docker-compose.https.yml up --build --force-recreate
cvat_opa
Health Check
OpenPolicyAgent appears to be running.
Expected Behavior
I expected the built container to work properly. I'm not using a specific version of CVAT. Just using CVAT:DEV which could ultimately be my problem. But it's what was already established as I already have data both in a volume and on the database I need access to.
Possible Solution
No response
Context
No response
Environment
The text was updated successfully, but these errors were encountered: