You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2017/11/09 10:50:00 UTC

[jira] [Created] (AIRFLOW-1796) Badly configured logging config can thwo exception in WWW logs view

Ash Berlin-Taylor created AIRFLOW-1796:
------------------------------------------

             Summary: Badly configured  logging config can thwo exception in WWW logs view
                 Key: AIRFLOW-1796
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1796
             Project: Apache Airflow
          Issue Type: Bug
            Reporter: Ash Berlin-Taylor


It is possible to specify a custom logging config that changes the {{file.task}} handler to {{s3.task}} but forget to update the {{core.task_log_reader}} config section.

This should be validated at start time, and mentioned in the comments of the default logging config that the config setting needs updating to.

This ends up as the following stack trace/error if you don't set it properly when trying to view task logs:

{noformat}
File "/usr/local/lib/python3.5/dist-packages/airflow/www/views.py", line 712, in log
   logs = handler.read(ti)
AttributeError: 'NoneType' object has no attribute 'read'
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)