Your second point there would lead me to believe that the scheduler is still actually running with the default SequentialExecutor.
Which config file did you edit? What output is shown when you (re)start the scheduler? Thanks, -ash On May 6 2020, at 11:00 am, Andreas Balke <andreas.ba...@now-extern.de> wrote: > Dear Airflow community, > > not sure if I’m targeting the right audience here. Just trying though > :) > > In a basic setup, like described here: > https://www.cloudwalker.io/2019/09/30/airflow-scale-out-with-redis-and-celery/ > <https://www.cloudwalker.io/2019/09/30/airflow-scale-out-with-redis-and-celery/>, > using `airflow_version: 1.10.10`, I discover two issues: > > 1) Even though the `airflow.cfg` is configured to use `CeleryExecutor` > +Redis and all the logs mention to use it, there is no Task visible in > Flower. When a DAG is started, it will only be processed via the DB > > 2) Many times, especially once a DAG is running, in the UI I see the > warning "The scheduler does not appear to be running.” > > Do you have any advice how to solve those? > > Best, Andreas
