Hi,
I am doing a self hosted Discourse (a contractor installed it) and updating to the latest beta (via the auto-update) today it said there was an error during update and it all stopped working. Site is offline.
What shall I do ?
AI-generated summary
A self-hosted Discourse user, Markus_Moenig, encountered a critical failure during a PostgreSQL 15 upgrade, rendering their site offline. After attempting to rebuild via SSH using ./launcher rebuild app as advised by eisammy, they received an error indicating the PostgreSQL upgrade failed, with a suggestion to consult this guide. eisammy recommended restoring from a snapshot and waiting for a fix, noting their own server also failed to start after the update. Frustrated after hours of troubleshooting, Markus_Moenig abandoned Discourse for a static Hugo site, criticizing the lack of warning for potentially hazardous updates despite the platform’s “noob-proof” UI. NateDhaliwal and david urged users to follow the debugging steps in the official PostgreSQL 15 update topic and offered support, noting no immediate fixes are pending but encouraging detailed reports. Later, eisammy confirmed their instance was successfully restored using the guide. david expressed regret over the experience, acknowledged the frustration, and closed the topic while inviting further issues in Product Support. The thread highlights the risks of automated updates in self-hosted environments and the importance of backups and community support during outages.
1 Like
I’m tried this and does’t works
if you have an snapshot do it and wait until be fixed.
Thanks for the reply. Where do I enter “./launcher rebuild app” ?
SSH
cd ..
cd var/discourse
./launcher rebuild app
1 Like
Thanks, but I get stuff like
UPGRADE OF POSTGRES FAILED
Please visit https://meta.discourse.org/t/postgresql-15-update/349515 for support.
You can run ./launcher start app to restart your app in the meanwhile
-------------------------------------------------------------------------------------
FAILED
--------------------
Pups::ExecError: if [ -f /root/install_postgres ]; then
/root/install_postgres && rm -f /root/install_postgres
elif [ -e /shared/postgres_run/.s.PGSQL.5432 ]; then
socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
fi
failed with return #<Process::Status: pid 18 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"tag"=>"db", "cmd"=>"if [ -f /root/install_postgres ]; then\n /root/install_postgres && rm -f /root/install_postgres\nelif [ -e /shared/postgres_run/.s.PGSQL.5432 ]; then\n socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1\nfi\n"}
bootstrap failed with exit code 1
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
c5b5958a65b830ae97f279c6df70e8b485b2d9d594af68767a953ff59e6ca286
Exactly what I said, use snap to restore old container and wait this be fixed I tried update too and my web server don’t start for some reason.
Thanks for trying to help. I have no time for this. Going back to a static Hugo site. Bye Discourse.
I would advise you to post in the topic mentioned.
Discourse just needs a little patience, and it’ll work.
2 Likes
Yup, please do follow the debugging steps in that topic, and let us know if you have any more info @eisammy @Markus_Moenig
We don’t have any fixes waiting for release. So if stuff is still not working for you, we need more information to help.
2 Likes
What I don’t understand is why you invest a lot of work to create a noob proof easy to use UI to attract web-tech noobs like me and than put potentially hazardous updates in there without any warning.
I rage destroyed my droplet after trying to get it to work for 4 hours today. So there is no way back for me.
Absolute correct! I did this now and my instance was updated and is running normally thank you.
And @Markus_Moenig , this tutorial it’s enough to solve this trouble
2 Likes
Glad to hear it’s working @eisammy
@Markus_Moenig I’m sorry things didn’t work out. We do our best to keep these kinds updates as seamless as possible, but sometimes things do go wrong. I agree that can be frustrating. We do our best to be as responsive as possible here on Meta, but I understand that’s not always enough.
I’m going to close out this topic. But if you or anyone else has any related issues please feel free to open a fresh one in Support.
5 Likes