Running airflow (v1.10.5) with LocalExecutor and finding that when wanting to restart or otherwise kill the scheduler daemon (started via airflow scheduler -D), need to *manually* kill -9 ... each scheduler process, eg...
[airflow@airflowetl airflow]$ ps -aux | grep scheduler airflow 9137 2.0 0.1 723196 72964 ? S 11:06 0:00 /usr/bin/python3 /home/airflow/.local/bin/airflow scheduler -D airflow 9141 0.5 0.1 1503344 72724 ? Sl 11:06 0:00 /usr/bin/python3 /home/airflow/.local/bin/airflow scheduler -D airflow 9149 0.0 0.1 722940 71408 ? S 11:06 0:00 /usr/bin/python3 /home/airflow/.local/bin/airflow scheduler -D airflow 9150 0.0 0.1 722940 71408 ? S 11:06 0:00 /usr/bin/python3 /home/airflow/.local/bin/airflow scheduler -D airflow 9154 0.0 0.1 722940 71412 ? S 11:06 0:00 /usr/bin/python3 /home/airflow/.local/bin/airflow scheduler -D airflow 9157 0.0 0.1 722940 71408 ? S 11:06 0:00 /usr/bin/python3 /home/airflow/.local/bin/airflow scheduler -D airflow 9162 0.0 0.1 722940 71412 ? S 11:06 0:00 /usr/bin/python3 /home/airflow/.local/bin/airflow scheduler -D airflow 9166 0.0 0.1 722940 71416 ? S 11:06 0:00 /usr/bin/python3 /home/airflow/.local/bin/airflow scheduler -D airflow 9171 0.0 0.1 722940 71412 ? S 11:06 0:00 /usr/bin/python3 /home/airflow/.local/bin/airflow scheduler -D airflow 9175 0.0 0.1 722940 71412 ? S 11:06 0:00 /usr/bin/python3 /home/airflow/.local/bin/airflow scheduler -D airflow 9181 0.7 0.1 723344 72808 ? S 11:06 0:00 airflow scheduler -- DagFileProcessorManager [airflow@airflowetl airflow]$ kill -9 $(cat $AIRFLOW_HOME/airflow-scheduler.pid) 9181 9175 ... Is there an easier way to kill the scheduler (and webserver) daemon(s)? Ie. without having to kill all scheduler daemon instances manually (not just the PID in airflow-scheduler.pid file and named PID). -- This electronic message is intended only for the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.
