You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Evan Hlavaty (Jira)" <ji...@apache.org> on 2020/01/27 13:47:00 UTC

[jira] [Closed] (AIRFLOW-6633) S3 Logging Configurations Are Ignored For Local

     [ https://issues.apache.org/jira/browse/AIRFLOW-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Evan Hlavaty closed AIRFLOW-6633.
---------------------------------
    Resolution: Not A Problem

Finally found logs in the dask worker and found out s3 url needed https:// prepended to it

> S3 Logging Configurations Are Ignored For Local
> -----------------------------------------------
>
>                 Key: AIRFLOW-6633
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6633
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: logging
>    Affects Versions: 1.10.7
>         Environment: Ubuntu 16.04 LTS
>            Reporter: Evan Hlavaty
>            Priority: Major
>
> When using the following config settings and S3 connection ID created in Admin UI, Local logs are still being used and no logs are uploaded to S3. No errors are ever thrown to indicate if connection settings are working.
> [core] # Airflow can store logs remotely in AWS S3. Users must supply a remote # location URL (starting with either 's3://...') and an Airflow connection # id that provides access to the storage location.
> remote_logging = True
> remote_base_log_folder = s3://my-bucket/path/to/logs
> remote_log_conn_id = MyS3Conn
> encrypt_s3_logs = False



--
This message was sent by Atlassian Jira
(v8.3.4#803005)