Site Offline Since Update - pg15 upgrade failed

Bug
1

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 ?

1 Like
2

I’m tried this and does’t works

if you have an snapshot do it and wait until be fixed.

3

Thanks for the reply. Where do I enter “./launcher rebuild app” ?

4

SSH

cd ..
cd var/discourse
./launcher rebuild app
1 Like
5

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
6

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.

7

Thanks for trying to help. I have no time for this. Going back to a static Hugo site. Bye Discourse.

8

I would advise you to post in the topic mentioned.

Discourse just needs a little patience, and it’ll work.

2 Likes
9

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
10

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.

11

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
12

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.

4 Likes