Recovering Discourse from a failed update
A user, barryparr, encountered issues while updating Docker and Discourse, resulting in a non-functional installation without a backup. watchmanmonitor suggested posting logs and Docker version to diagnose the issue. After reviewing the logs, watchmanmonitor and Steven pointed out that the ./launcher rebuild command needed to be run with the correct syntax: ./launcher rebuild app. sjmscott also experienced the same issue, and codinghorror clarified the correct command. watchmanmonitor suggested improving the error message to provide the correct command. With the correct command, barryparr was able to recover their site.
I wrecked my installation while trying to update Docker and nothing is working now. And I don’t have a backup.
How to do I tell what the state of my docker and in discourse installations are and figure out how to put this back together?
Is it possible to recover the data from my discourse installation and start over?
Define “wrecked” ?
Post some logs into a gist.github.com (etc) and post your docker version as well?
The link to the log is below. I tried update Discourse, but had to update Docker first. I followed the directions on meta for updating, but had some problems.
near the end, it says Please run ./launcher rebuild again what happened then?
I just re-ran it:
root@coastsider:/var/discourse# ./launcher rebuild
Config file was not found, ensure containers/.yml exists
Available configs ( app )
root@coastsider:/var/discourse#
With ./launcher rebuild app wouldn’t it work ?
I got stuck upgrading and I tried to the following:
I am getting the identical message.
That’s because the command is
./launcher rebuild app
not
./launcher app rebuild
Ah, I didn’t even catch that… I’d rebuild enough times that I used the up arrow key & return to rerun the same command.
Maybe instead of:
Please run ./launcher rebuild again
the line should be
Please re-run:
./launcher rebuild app
EDIT - PR Submitted
My site is back.
Thank you for walking through that.