potiuk commented on issue #16505: URL: https://github.com/apache/airflow/issues/16505#issuecomment-871436351
This is again, very hard to say without seeing azure service app logs. I am sure there must be some additional logs for the app service managing Airflow. Typically those kinds of problems occur with some resources not being available - connections, memory, disk, DNS querying service being slow, networking configuration, firewalls etc. All those might cause such result. Since there are no logs in Airflow about some errors or warnings, i think one of those might be the culprit. I think the only way to be able to help is to take a look at the app service logs and try to see what kind of resources are problematic. There is no known problem in 2.0.1 that i am aware of that is an obvious candidate that could cause it. Sorry I cannot help but some more digging from your side is needed. We need to be able to see the logs to be able to diagnose it. Unfortunately i know nothing about the Azure App Service to be able to tell you how to do it but there must be a way to review and diagnose all those various resources there as they are manged by the deployment service, not airflow. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
