7yl4r commented on issue #16025: URL: https://github.com/apache/airflow/issues/16025#issuecomment-854208653
I'm dealing with this too (but mine is 100% of the time on one system only). After researching it looks like this is an old issue that seems to keep popping up after being "fixed". These resources haven't fixed my problem but there are some ideas that might be relevant to your setup: * [some general ideas on astronomer forum](https://forum.astronomer.io/t/log-file-does-not-exist/277). The most important seems to be insufficient RAM. * [thread that suggests hostname could be changing](https://www.debugcn.com/en/article/31263944.html). I suspect you are also seeing [Airflow JIRA issue *If a task crashes, hostname not committed to db so logs not in the UI*](https://issues.apache.org/jira/browse/AIRFLOW-4922) which is a symptom of the `Celery command failed on host`? I am. Do you have one worker failing consistenly among other workers suceesding or are your failures on a worker which is also succeeding sometimes? -- 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. For queries about this service, please contact Infrastructure at: [email protected]
