-
Notifications
You must be signed in to change notification settings - Fork 89
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
Lemmy from scratch install instructions fail with "thread ‘main’ panicked at ‘Couldn’t run DB Migrations’, crates/db_schema/src/utils.rs:165:25" #201
Comments
Could you do a PR to add that to the docs? |
Adding superuser privileges is not an ideal solution - it means that Lemmy won't work on any managed cloud database which prevents superuser access. This PR seems like a better solution: LemmyNet/lemmy#3002 |
FYI as LemmyNet/lemmy#3002 was merged, I believe this issue can be closed |
This is not working for me, and I'm puzzled why. I confirmed it was added, but I'm still getting the migrations error. When will the patch be available via crates.io? I'm anxious to get my instance up and running. :)
|
That fix is not released yet, it will be in 0.18 |
@ffolkes I had same issue. Found out database server was missing postgresql extensions ltree and pgcrypto. |
Thank you! That did it. :) On Rocky 9 I needed to do "dnf install postgresql-contrib" and then "CREATE EXTENSION IF NOT EXISTS pgcrypto;" and "CREATE EXTENSION IF NOT EXISTS ltree;" then grant lemmy superuser to start it until the patch rolls out. |
had trouble finding this since it was already closed almost updated my postgres version oh no thank you for the workaround! |
As a workaround, before starting the lemmy server:
sudo -iu postgres psql -c “ALTER USER lemmy WITH SUPERUSER;”
It seems that the problematic SQL has been identified in this pull request?
LemmyNet/lemmy@29c4144
The text was updated successfully, but these errors were encountered: