potiuk commented on issue #13325: URL: https://github.com/apache/airflow/issues/13325#issuecomment-751831754
It is extremely difficult to say what's wrong without getting any logs. Airflow produces a lot of logs. You can even run scheduler manually and get the logs output to you. Note that for airflow 2.0 we've changed a lot the CLI commands - like `airflow db` `airflow user`, we've also added some configuration changes. All that is documented here: http://airflow.apache.org/docs/apache-airflow/stable/upgrading-to-2.html If you have not followed the steps outlined there and if you did not reconfigure your image/configuration appropriatel, it is very likely that something might be wrong. note that we also have the automated Upgrade Check tool http://airflow.apache.org/docs/apache-airflow/stable/upgrading-to-2.html#step-3-install-and-run-the-upgrade-check-scripts that you can install and run in your old environment and it might actually help you with pointing out what changes you need to do. Finally in the new airflow there is the `airflow info` command that you can run to dump some of the configuraiton information (i,e, where the logs are stored, what configuration is used. Also there is `airflow config list` command that can show you what configuration parameters are being used. those tools are useful to analyse the problems. I am closing that as invalid now, but please let us know in case you manage to go through the steps and see if the problem is in your configuration. If you do the investigation and are still lost - please add this extra information - logs, info, config etc. ---------------------------------------------------------------- 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]
