Update failure

Hello,

I’m having a failure rebuilding the app.

Get:15 https://apt.postgresql.org/pub/repos/apt bookworm-pgdg/main amd64 Packages [361 kB]
Fetched 10.2 MB in 3s (3,813 kB/s)
Reading package lists...Reading package lists...Stopping PostgreSQL 15 database server: main.

check for "/usr/lib/postgresql/13/bin" failed: No such file or directory

Failure, exiting
-------------------------------------------------------------------------------------
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

Following the provided link https://meta.discourse.org/t/postgresql-15-update/349515 and running the manual update procedure also fails. Entering the app and running only apt-get update fails, and leads to an error message that leads the same error as in this issue Debian install fails on Bookworm in FIPS mode · Issue #1096 · docker/docker-ce-packaging · GitHub

And indeed, my system is in FIPS mode, and trying to only update libgcrypt fails with the same error message as in the GitHub issue above.

Does anyone have any ideas on how to proceed?

Thank you!

-Steve

Is your OS beyond end of life?

What version of Docker do you have?

Can you start the existing container with ./launcher start app or maybe docker start app? If so, I’d probably recommend making a backup, spinning up a new VM, installing Discourse, and restoring that backup.

2 Likes

Can you provide the complete log output?

There may be more failures above that we missed that eventually caused this one.

Some more information about your setup would also help:

  • what OS is running on the host?
  • what setup are you using (i.e. standalone?)

No argument with this. Step #1 should always be “make a backup”.

e.g.:

  • take a Discourse backup
  • shut down the containers
  • move postgres data out of the way
  • do a rebuild
  • restore the backup

But first we need to know what we’re working with.

1 Like