this post was submitted on 06 Feb 2023
4 points (100.0% liked)

Lemmy Support

4772 readers
93 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
[email protected]
4
Messed up the update to 0.17 (lemmy.ml)
submitted 2 years ago by [email protected] to c/[email protected]
8 comments fedilink hide all child comments
 

Hello,

I tried to update my instance but I forgot to read the release notes and used ansible to update. Of course it failed. After the update I decided to check what is new and I realized my mistake. I tried to run the postgress update script but it fails with the message

Error response from daemon: Container {container hash} is restarting, wait until the container is running

The logs say that the db hasn't been updated.

I don't know what else to upload here to help troubleshooting. Thanks in advance!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 2 years ago (1 children)

You'll have to post your docker logs.

sudo docker-compose logs lemmy

[–] [email protected] 1 points 2 years ago (1 children) 

donkysocial-lemmy-1  | thread 'main' panicked at 'Error connecting to postgres://lemmy:pass@postgres:5432/lemmy', crates/db_schema/src/utils.rs:157:56
donkysocial-lemmy-1  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
donkysocial-lemmy-1  | thread 'main' panicked at 'Error connecting to postgres://lemmy:pass@postgres:5432/lemmy', crates/db_schema/src/utils.rs:157:56
donkysocial-lemmy-1  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
donkysocial-lemmy-1  | thread 'main' panicked at 'Error connecting to postgres://lemmy:pass@postgres:5432/lemmy', crates/db_schema/src/utils.rs:157:56
donkysocial-lemmy-1  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
donkysocial-lemmy-1  | thread 'main' panicked at 'Error connecting to postgres://lemmy:pass@postgres:5432/lemmy', crates/db_schema/src/utils.rs:157:56
donkysocial-lemmy-1  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
donkysocial-lemmy-1  | thread 'main' panicked at 'Error connecting to postgres://lemmy:pass@postgres:5432/lemmy', crates/db_schema/src/utils.rs:157:56
donkysocial-lemmy-1  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
donkysocial-lemmy-1  | thread 'main' panicked at 'Error connecting to postgres://lemmy:pass@postgres:5432/lemmy', crates/db_schema/src/utils.rs:157:56
donkysocial-lemmy-1  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
donkysocial-lemmy-1  | thread 'main' panicked at 'Error connecting to postgres://lemmy:pass@postgres:5432/lemmy', crates/db_schema/src/utils.rs:157:56
donkysocial-lemmy-1  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
donkysocial-lemmy-1  | thread 'main' panicked at 'Error connecting to postgres://lemmy:pass@postgres:5432/lemmy', crates/db_schema/src/utils.rs:157:56
donkysocial-lemmy-1  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[–] [email protected] 1 points 2 years ago (1 children)

It can't connect to the DB because you didn't do the upgrade properly. Follow these instructions: https://github.com/LemmyNet/lemmy/blob/main/RELEASES.md#upgrade-instructions

[–] [email protected] 1 points 2 years ago (1 children)

I have followed them. Whenever I run the sudo sh postgres_12_to_15_upgrade.sh I get

Do not stop in the middle of this upgrade, wait until you see the message: Upgrade complete.
Stopping lemmy and all services...
Stopping donkysocial_postgres_1 ... done
Stopping donkysocial-lemmy-ui-1 ... done
Stopping donkysocial-lemmy-1    ... done
Stopping donkysocial-pictrs-1   ... done
Stopping donkysocial-postfix-1  ... done
Make sure postgres is started...
Starting donkysocial_postgres_1 ... done
Exporting the Database to 12_15.dump.sql ...
Error response from daemon: Container a1e2ddeced29b9060049e920b49bcea87189b0122a68f015ada202a6181bd2a0 is restarting, wait until the container is running
[–] [email protected] 3 points 2 years ago (1 children)

That error tells me nothing. Please ask in the matrix channel, I'm very busy with coding.

[–] [email protected] 1 points 2 years ago

Alright, sorry for bothering you.