I’m trying to do the current upgrade. It has failed and I can’t access my discourse. There’s multiple errors. All help appreciated. # 502 Bad Gateway --- nginx Log attached. cap.txt (58.3 KB) I, [2024-12-19T13:12:37.802755 #1] INFO -- : > /usr/local/bin/create_db createdb: error: could not connect to database template1: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? . . . 1353:C 19 Dec 2024 13:13:56.951 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1353:C 19 Dec 2024 13:13:56.951 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=1353, just started 1353:C 19 Dec 2024 13:13:56.951 # Configuration loaded 1353:M 19 Dec 2024 13:13:56.951 * monotonic clock: POSIX clock_gettime 1353:M 19 Dec 2024 13:13:56.952 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use 1353:M 19 Dec 2024 13:13:56.952 # Failed listening on port 6379 (TCP), aborting. . . . Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return # 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 {"cd"=>"$home", "tag"=>"migrate", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]} 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. d7e3c61c9189308cfa984b4f73baf5bece2cdb0ce5ff4034396a0440ae3d7594

Is this a standard install? Is it just one app.yml file (and not separate web_only and data containers?) For some reason it’s unable to connect to your databases.

Maybe upgrade docker. What is docker --version

Discourse asked me to do a Docker upgrade first. I did. I can’t check the version now because I had to revert the server to put it back in production, so all changes have been undone.

[image] Charles Barouch: so all changes have been undone. Then you have no way to debug. What I would likely recommend is to spin up a new VM, install Discourse there, and restore a backup. When it works, put the existing site in read-only mode, backup, restore, and switch the DNS (or a static IP if you have access to such). You can use Move a Discourse site to another VPS with rsync so that the new site has valid certs and you can have a look by hacking your local DNS to point to the new IP address.

Upgrading Discourse: Multiple failures

Product Support

CharlesBarouch (Charles Barouch) December 19, 2024, 7:08pm 3

Standard install. Just one app.yml.

Topic		Replies	Views
Site down after upgrade via SSH - how to fix? Self-hosting	3	714	September 16, 2023
UPGRADE OF POSTGRES FAILED - I've tried everything Self-hosting	17	2910	August 25, 2020
Discourse failing to connect to port 3000 Product Support	8	1423	September 23, 2020
Difficulty installing on vm that includes CPanel and Apache Self-hosting unsupported-install	7	348	March 20, 2025
Trouble updating discourse after some time - UPGRADE OF POSTGRES FAILED Product Support	5	339	November 21, 2025

Upgrading Discourse: Multiple failures

Related topics