Sagun Garg

01/31/2021, 5:16 PM
Hi Prefect Team, I continue to get following errors in #prefect-server #towel container log definition (PFA below), not sure if this is worrisome or not. Disclaimer: I am able to access my UI and all other container logs for UI, GraphQL, Apollo and Hasura are all stable and fine. I am also able to access GraphQL playground, Hasura Console and healthcheck endpoint properly. I am yet to test my flows with this AWS Fargate #prefect-server setup. This is when I am hosting #prefect-server in AWS ECS Fargate as a single task definition with the following configuration converted from docker-compose.yml ( to 5 multi-container task definition for AWS Fargate. I am able to host Prefer Server using the following task definition (PFA the screenshot). Note I have used Prefect core 0.14.5 tags for my images. Please note all configurations were done using AWS Console for task definition configuration. I have used managed Postgres in AWS RDS for Hasura's underlying DB What is the most stable version where I can avoid these errors, should I pass something to my towel container using "command" at runtime to fix this?
2021-02-01 01:06:15{"severity": "DEBUG", "name": "prefect-server.ZombieKiller", "message": "Sleeping for 120.0 seconds..."}
2021-02-01 01:04:48{"severity": "ERROR", "name": "prefect-server.Lazarus", "message": "Unexpected error: ConnectError(gaierror(-2, 'Name or service not known'))"}
2021-02-01 01:04:48{"severity": "DEBUG", "name": "prefect-server.Lazarus", "message": "Sleeping for 600.0 seconds..."}
2021-02-01 01:04:25{"severity": "ERROR", "name": "prefect-server.Scheduler", "message": "Unexpected error: ConnectError(gaierror(-2, 'Name or service not known'))"}
2021-02-01 01:04:25{"severity": "DEBUG", "name": "prefect-server.Scheduler", "message": "Sleeping for 300.0 seconds..."}
2021-02-01 01:04:15{"severity": "ERROR", "name": "prefect-server.ZombieKiller", "message": "Unexpected error: ConnectError(gaierror(-2, 'Name or service not known'))"}