Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure to start redash with a local docker install (InFailedSqlTransaction) #6973

Closed
stephendwolff opened this issue May 15, 2024 · 3 comments

Comments

@stephendwolff
Copy link

Issue Summary

I tried following the developer set up instructions here:

I did this on an M2 Macbookpro and an Ubuntu 20.04LTS virtual machine.

Bug is that the WSGI app fails to start when trying to fetch the initial "Organisation" with g.org = Organization.get_by_slug(slug) (File "/app/redash/authentication/org_resolving.py", line 18, in _get_current_org)

SQLAlchemy returns this error:

sqlalchemy.exc.InternalError: (psycopg2.errors.InFailedSqlTransaction) current transaction is aborted, commands ignored until end of transaction block

[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
FROM organizations
WHERE organizations.slug = %(slug_1)s
LIMIT %(param_1)s]
[parameters: {'slug_1': 'default', 'param_1': 1}]
(Background on this error at: http://sqlalche.me/e/13/2j85)
@stephendwolff
Copy link
Author

I have investigated a bit further, and there are no tables in the postgress database, so it appears that no database migrations have run.

@stephendwolff
Copy link
Author

and have fixed my issue i think:

make create_database

was what was needed to get past this issue

@justinclift
Copy link
Member

Oh, that's unexpected. The database initialisation step is supposed to be automatically done these days when it's needed. That was a recent development though.

Hmmm. I wonder... we did a rollback of some code over the last few days, so maybe the automatic-database-initialisation thing has been caught up in that somehow? Will need to take a look at that later on and check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants