You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Michael Spector (JIRA)" <ji...@apache.org> on 2018/12/26 07:30:00 UTC

[jira] [Created] (AIRFLOW-3567) Logs are not fetched from S3 when using AIM policy

Michael Spector created AIRFLOW-3567:
----------------------------------------

             Summary: Logs are not fetched from S3 when using AIM policy
                 Key: AIRFLOW-3567
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3567
             Project: Apache Airflow
          Issue Type: Bug
          Components: logging
    Affects Versions: 1.10.1
            Reporter: Michael Spector


The remote logging is configured as follows:

{code:python}
remote_logging=True
remote_log_conn_id=''
remote_base_log_folder='s3://logs-bucket/airflow/analytics-airflow'
encrypt_s3_logs=False
{code}

Logs on S3 are created successfully, however when trying to access them via UI we're getting something like this:

{code:bash}
Log file does not exist: /var/lib/airflow/logs/jobname/taskname/2018-12-25T03:00:00+00:00/1.log 
Fetching from: http://10.118.19.142:50192/log/jobname/taskname/2018-12-25T03:00:00+00:00/1.log
{code}

Which means that logs fetcher falls back to FileTaskHandler.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)