1

Issue Summary

Our redash instance was running fine and suddenly it went down, seeing lot of DB errors in logs, could someone share any inputs

ProgrammingError: (psycopg2.ProgrammingError) relation “organizations” does not exist
Tue, Apr 12 2022 8:16:55 am LINE 2: FROM organizations
Tue, Apr 12 2022 8:16:55 am ^
Tue, Apr 12 2022 8:16:55 am [SQL: ‘SELECT organizations.updated_at AS organizations_updated_at, organizations.created_at AS organizations_created_at, organizations.id AS organizations_id, organizations.name AS organizations_name, organizations.slug AS organizations_slug, organizations.settings AS organizations_settings \nFROM organizations \nWHERE organizations.slug = %(slug_1)s \n LIMIT %(param_1)s’] [parameters: {‘slug_1’: ‘default’, ‘param_1’: 1}] (Background on this error at: Error Messages — SQLAlchemy 1.4 Documentation)
Tue, Apr 12 2022 8:16:55 am [2022-04-12 13:16:55,780] ERROR in app: Exception on /favicon.ico [GET]

Technical details:

  • Redash Version: * Version: 8.0.2+b37747 (a9d7ca43)
  • Browser/OS: Chrome
  • How did you install Redash: github
2

That error means that the database schema doesn’t exist on the database that Redash connected to. Normally, we only see that error when you first set-up Redash. It happens if you start the application before running the create_tables script.

For a production instance there could be a lot of causes, and there isn’t enough information in your post to indicate why. It could be that the IP address or DNS record for the metadata database changed. It could be that the whole database was dropped (this would not happen automatically).

3

thanks Jesse for your reply.
Only thing I see is that the postgresql pod was started yesterday. why would it start by itself and we need to create the database every time the pod restarts.