Hello Community! I’m sorry we have to meet under these circumstances. Discourse is offline after a failed upgrade. Same story as. Discourse offline after failed upgrade "bootstrap failed with exit code 5" Attempted to upgrade to v3.2.0.beta3 I’m still on Ubuntu 16.04. I DO have the previous d…

[image] Discourse offline after failed upgrade "bootstrap failed with exit code 5" installation Did you try ./launcher start app to try and get the pre-rebuild one back up? While I have the old images, I did remove the newest image… docker rmi 51421f454322 -f I have…

The easier thing is to go ahead and spin up a new droplet and copy /var/discourse to it and rebuild there. That will solve the problem rather than mitigate it. There is a launcher command that will give you the docker command which might help. You can look at the launcher script to find its name (b…

Looks like you’re suggesting: ./launcher start-cmd app It outputs quite a bit, starting with + true run --shm-size=512m -d --restart=always... Going out on a limb, I tried: docker + true run 984f729957df --shm-size=512m -d --restart=always ... to no avail. container_linux.go:247: starting contai…

Yeah. Something like that. I don’t know how to do it. You might have deleted the only usable image. My recommendation remains to spin up a new droplet and copy stuff over. If you were one of my clients, that’s what I’d do.

[image] Jay Pfaffman: new droplet and copy stuff over. Thanks for the suggestion. Not a fan of unplanned migrations, but it seems like that’s in the cards. I’m gonna presume that you’re referring to this? Move a Discourse site to another VPS with rsync Will there be any extra instructions if…

[image] Sasquatch_Kinetic: Will there be any extra instructions if we’ve enabled DO Spaces (S3 storage)? Not if you followed Configure an S3 compatible object storage provider for uploads . If you have the settings in the database it might be more complicated if you try to do a restore rather …

Configure an S3 compatible object storage provider for uploads I configured this service in 2016, so unfortunately it would appear that we have the settings in a db? There are no S3 params in app.yml Any other landmines I should be made aware of?

Thanks again for your assist. As for the rsync, I am a little worried with how the instructions state in so many words: setup the new server and sync stop the service on the old server sync again but with --delete That sounds volatile, and also not possible in my scenario. Will that be a concern?…

Update: We’re back online with a whole new Droplet. I’m glad I know now that a migration is relatively straightforward. Would have been a lot cooler if the update didn’t break the old droplet. I know it’s a holiday, but it’d be great if someone on the dev team could spend some time looking into t…

Another discourse offline "bootstrap failed with exit code 5"

Support Self-hosting

pfaffman (Jay Pfaffman) December 31, 2023, 4:54pm 9

If you rsync it over, you should be fine. Then you can switch over to the recommended setup. You might have trouble if your try a database restore.

1 Like

Topic		Replies	Views
How to recover my broken (not web-accessible) Discourse installation after failed upgrade Self-hosting	4	832	February 16, 2020
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	17	1965	November 26, 2021
Site down after upgrade via SSH - how to fix? Self-hosting	4	540	October 16, 2023
Discourse offline after failed upgrade "bootstrap failed with exit code 5" Self-hosting	24	1366	February 22, 2024
An upgrade knocked my site offline; how long until it's restored? Self-hosting	16	325	August 9, 2025

Another discourse offline "bootstrap failed with exit code 5"

Related topics