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

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/12/21 18:29:09 UTC

[GitHub] [airflow] potiuk edited a comment on issue #13200: CLI `airflow scheduler -D --pid ` fails silently if PIDFile given is a relative path

potiuk edited a comment on issue #13200:
URL: https://github.com/apache/airflow/issues/13200#issuecomment-749125767


   Confirmed. 
   
   
   The reason is that default "working_directory" is used in  in DaemonContext https://github.com/apache/airflow/blob/97eee350e41f6f00ad3076489a5dac2e5beaa266/airflow/cli/commands/scheduler_command.py#L48 
   
   By default the "working_directory" is set to "/" which means that the pid file is attempted to be created as "/<FILE>" - which for non-root user will fail. This works for example in Breeze as we use root user there, but in productionsetup with non-root user it will fail. 
   
   I think we should assume (extending to the code in https://github.com/apache/airflow/blob/97eee350e41f6f00ad3076489a5dac2e5beaa266/airflow/utils/cli.py#L222) than when relative path is specified, it is relative to ${AIRFLOW_HOME}.


----------------------------------------------------------------
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:
users@infra.apache.org