bouke-nederstigt edited a comment on issue #13325: URL: https://github.com/apache/airflow/issues/13325#issuecomment-752072506
Thanks for the pointers. I originally used the upgrade_check and upgrade scripts to execute the upgrade. Nevertheless I double checked everything again. Some notes: - The upgrade_check script only fails on ```Users must delete deprecated configs for KubernetesExecutor```. However non of the config items listed there are actually part of my airflow.cfg (or available as an environment variable). I assume this isn't a problem considering that I'm not using the KubernetesExecutor. - After reverting back to 1.10.14, reverting the database using a backup, and changing back to old style imports for a DAG the scheduler immediately starts working again. Tasks are also executed correctly as expected. - I ran through the upgrade process as described in https://airflow.apache.org/docs/apache-airflow/stable/upgrading-to-2.html once again. FYI: I manually removed the known_event, chart and users tables because the migrations aren't working correctly. But other than that there were no issues. After upgrading the scheduler shows the same behaviour as before. Tasks get scheduled, but not executed. Of course I might be mistaken but I have a strong feeling this isn't related to configuration. I've attached files with logs generated by the scheduler in scheduler.log. This shows logs from a couple of minutes running the scheduler. There's a single dag running and it transitions a couple of tasks to the scheduled state. I've also added a copy of the scheduler/knmi_weather.py logs. For completeness sake I've also added the result of airflow config list. [knmi_weather.py.txt](https://github.com/apache/airflow/files/5750787/knmi_weather.py.txt) [scheduler.log.txt](https://github.com/apache/airflow/files/5750788/scheduler.log.txt) [config.txt](https://github.com/apache/airflow/files/5750798/config.txt) Finally, this is the result of executing the airflow info command. ```Apache Airflow: 2.0.0 System info OS | Linux architecture | x86_64 uname | uname_result(system='Linux', node='b3dd1f534368', release='4.19.121-linuxkit', version='#1 SMP Tue | Dec 1 17:50:32 UTC 2020', machine='x86_64', processor='') locale | ('en_US', 'UTF-8') python_version | 3.7.9 (default, Dec 11 2020, 15:01:14) [GCC 6.3.0 20170516] python_location | /usr/local/bin/python Tools info git | git version 2.11.0 ssh | OpenSSH_7.4p1 Debian-10+deb9u7, OpenSSL 1.0.2u 20 Dec 2019 kubectl | NOT AVAILABLE gcloud | NOT AVAILABLE cloud_sql_proxy | NOT AVAILABLE mysql | mysql Ver 15.1 Distrib 10.1.47-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 sqlite3 | NOT AVAILABLE psql | NOT AVAILABLE Paths info airflow_home | /usr/local/airflow system_path | /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin python_path | /usr/local/bin:/usr/local/airflow/config:/usr/local/airflow/great_expectations/plugins}:/usr/local/airflow:/usr/local/lib/python37.zip:/usr/local/lib/p | ython3.7:/usr/local/lib/python3.7/lib-dynload:/usr/local/lib/python3.7/site-packages:/usr/local/airflow/dags:/usr/local/airflow/plugins airflow_on_path | True Config info executor | CeleryExecutor task_logging_handler | airflow.providers.amazon.aws.log.s3_task_handler.S3TaskHandler sql_alchemy_conn | mysql://root:root@airflow_db:3306/airflow_dev dags_folder | /usr/local/airflow/dags plugins_folder | /usr/local/airflow/plugins base_log_folder | /usr/local/airflow/logs Providers info apache-airflow-providers-amazon | 1.0.0 apache-airflow-providers-celery | 1.0.0 apache-airflow-providers-ftp | 1.0.0 apache-airflow-providers-http | 1.0.0 apache-airflow-providers-imap | 1.0.0 apache-airflow-providers-jdbc | 1.0.0 apache-airflow-providers-mysql | 1.0.0 apache-airflow-providers-sqlite | 1.0.0 ``` Happy to provide extra information or spend some time investigating this issue. Unfortunately I'm pretty blank at this stage as to what could be the issue. So any help would be greatly appreciated. ---------------------------------------------------------------- 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: [email protected]
