Discourse rebuild fails due to unclean shutdown

[mwaniki (Mwaniki Wairungu)]

I’ve updated the steps in the FAQ. Could you try them out and let us know if that helps?

@mwaniki

Now shut it down again with ./launcher stop app. After that tail the logs to see if it was a clean one:

tail -f shared/standalone/log/var-log/postgres/current
2025-01-24 09:19:06.437 UTC [37] LOG:  received smart shutdown request
2025-01-24 09:19:06.444 UTC [37] LOG:  background worker "logical replication launcher" (PID 54) exited with exit code 1
2025-01-24 09:19:06.446 UTC [49] LOG:  shutting down
2025-01-24 09:19:06.468 UTC [37] LOG:  database system is shut down

If the logs do not indicate that the database is shut down, you can start the old container again, enter with ./launcher enter app, run these commands and tail the logs again once done.

export SVWAIT=300
sv stop nginx
sv stop unicorn
sv stop postgres
exit

If the logs look like above, you can now try to upgrade again using ./launcher rebuild app.