Yesterday I had an admin message about upgrades. From the web UI, I did the Docker upgrade first and this seemed to go well. After it finished, the upgrade button for Discourse was enabled and I initiated that. At some point something broke and now our site is down. I was on my phone at the time and I didn’t manage to look at the log carefully to see where exactly things broke, before I’m currently pocking around over SSH and about to try ./launcher rebuild app to hopefully get a better idea about what exactly is the problem in the upgrade. I’ve never done Discourse command-line repair and I want to make sure that I don’t blow away our data. Looking over app.yml, I see that the container is stateless - great - and that all the data is on the host, accessed as a shared volume. I ran discourse-doctor and it looks like disk space is not the issue. Will the rebuild app command touch the local data store?

Yes, do the ./launcher rebuild app that should do it. It will not blow away your data. If you’d rather not to it yourself, please see Automatic Rebuilds When You Need Them.

Thanks, the rebuild seems to have worked - the GitHub avatars and favicon don’t show for some reason, though.

Hi! I have upgraded and the page gave me a 504 Gateway Time-out error. I did this, and it still doesn´t work. cd /var/discourse git pull; ./launcher rebuild app Do you have any idea why it still not working?

No. There is not much chance of having any idea. My best guess is that you didn’t wait for the server to fully restart, but it could be about anything. Did the rebuild complete without error? Are you out of disk space? Does docker ps show that the container is running?

Docker ps shows me this: [Captura de pantalla 2020-11-04 a las 16.52.52] If a put ./launcher enter app, it tells me that Container is not running. How can I do it to run? In the log file I see this: Could not find rake-13.0.1 in any of the sources Run bundle install to install missing gems. Does it have any importance? Thanks

it finnished the rebuild and it puts only this: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES And for ./launcher enter app I receive this: Error response from daemon: Container … is not running

So the rebuild is failing at some step. Try a new rebuild with just ./launcher rebuild app and watch the logs. When it stops with another failure, scroll up and search for error messages, those will show what is the problem. Copy those here and we can help.

@Falco if I put ./launcher logs app I have this: Could not find rake-13.0.1 in any of the sources Run bundle install to install missing gems.

Is this the whole logs? Can you share a larger portion of the logs? Is this server behind some weird firewall or corporate environment? Or is it a simple VPS on the internet?

Upgrade failed - could use some help to try and fix using SSH

Product Support

Falco (Falco) November 4, 2020, 4:04pm 8

That container name means that the rebuild is still going, and for just 4 minutes.

You can tail the logs with

docker logs -tf sweet_chatelet

Are the logs moving?

Topic		Replies	Views
Recovering Discourse from a failed update Product Support	9	3646	July 2, 2016
Sorry there was an error upgrading Discourse Product Support	5	777	March 20, 2021
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2484	November 26, 2021
Discourse thinks it is upgrading but it is not Product Support	6	2674	July 2, 2016
Error `rebuild app` broken, at the last discourse upgrade Product Support	9	468	May 7, 2025

Upgrade failed - could use some help to try and fix using SSH

Related topics