You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Andrew Harmon (JIRA)" <ji...@apache.org> on 2019/07/09 18:58:00 UTC
[jira] [Created] (AIRFLOW-4922) If a task crashes, host name is not
committed to the database so logs aren't able to be seen in the UI
Andrew Harmon created AIRFLOW-4922:
--------------------------------------
Summary: If a task crashes, host name is not committed to the database so logs aren't able to be seen in the UI
Key: AIRFLOW-4922
URL: https://issues.apache.org/jira/browse/AIRFLOW-4922
Project: Apache Airflow
Issue Type: Bug
Components: logging
Affects Versions: 1.10.3
Reporter: Andrew Harmon
Sometimes when a task fails, the log show the following
{code}
*** Log file does not exist: /usr/local/airflow/logs/my_dag/my_task/2019-07-07T09:00:00+00:00/1.log***
Fetching from: http://:8793/log/my_dag/my_task/2019-07-07T09:00:00+00:00/1.log***
Failed to fetch log file from worker. Invalid URL 'http://:8793/log/my_dag/my_task/2019-07-07T09:00:00+00:00/1.log': No host supplied
{code}
I believe this is due to the fact that the row is not committed to the database until after the task finishes. https://github.com/apache/airflow/blob/a1f9d9a03faecbb4ab52def2735e374b2e88b2b9/airflow/models/taskinstance.py#L857
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)