huankimtran commented on issue #19886: URL: https://github.com/apache/superset/issues/19886#issuecomment-1374713722
Encountered same problem. This seems to be caused by the db service was not able to start by the time superset_app try to connect to it. The root cause for db service failure need to be addressed first. In my case, I found the root cause for db service failure by bringing up only db service ``` # Bring down everything first docker-compose down # Bring up only db service docker-compose up db ``` The problem in my case was ``` db_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization db_1 | db_1 | 2023-01-08 04:16:00.303 UTC [1] FATAL: database files are incompatible with server db_1 | 2023-01-08 04:16:00.303 UTC [1] DETAIL: The data directory was initialized by PostgreSQL version 14, which is not compatible with this version 10.21 (Debian 10.21-1.pgdg90+1). ``` so my previous docker-compose up runs have created a database and the database is not at the right version. The old database is saved in superset_db_home volume. So what I had to do was remove this volume ``` docker volume rm superset_db_home ``` Then rerun docker-compose up -- 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: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
