jitenadav opened a new issue, #38108:
URL: https://github.com/apache/airflow/issues/38108

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   2.8.0
   
   ### What happened?
   
   Currently, when executing airflow scheduler in daemon mode, a pidfile is 
generated in the designated AIRFLOW_HOME directory even when specifying the 
--pid option with an absolute path to an alternative directory, the pidfile 
continues to be created in the default AIRFLOW_HOME directory.
   
   Webserver in daemon mode creates the PID file at the specified location, its 
just the Scheduler acting up.
   
   ### What you think should happen instead?
   
   When running in daemon mode and specifying an alternative path for the 
pidfile using the --pid option, the pidfile should be created in the specified 
directory rather than the default AIRFLOW_HOME directory.
   
   ### How to reproduce
   
   `airflow scheduler --daemon --pid 
/opt/bti/airflow/pids/airflow-scheduler.pid --log-file 
/opt/bti/airflow/logs/airflow-scheduler.log`
   
   Just change the location
   
   ### Operating System
   
   Ubuntu 20.04
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-common-io==1.3.0
   apache-airflow-providers-common-sql==1.11.1
   apache-airflow-providers-ftp==3.7.0
   apache-airflow-providers-http==4.10.0
   apache-airflow-providers-imap==3.5.0
   apache-airflow-providers-smtp==1.6.1
   apache-airflow-providers-sqlite==3.7.1
   
   
   ### Deployment
   
   Virtualenv installation
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to