Mise à niveau de Discourse : plusieurs échecs

Soutien
1

J’essaie de faire la mise à niveau actuelle. Elle a échoué et je ne peux pas accéder à mon discourse.
Il y a plusieurs erreurs. Toute aide est appréciée.

# 502 Bad Gateway
---
nginx

Journal joint.

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 #<Process::Status: pid 1356 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 {"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
2

S’agit-il d’une installation standard ? Est-ce juste un fichier app.yml (et non des conteneurs séparés web_only et data) ?

Pour une raison quelconque, il ne parvient pas à se connecter à vos bases de données.

3

Installation standard. Une seule app.yml.

4

Peut-être mettre à niveau docker. Quelle est la commande

docker --version
5

Discourse m’a demandé de faire une mise à niveau Docker en premier. Je l’ai fait.
Je ne peux pas vérifier la version maintenant car j’ai dû annuler le serveur pour le remettre en production, donc tous les changements ont été annulés.

6

Alors vous n’avez aucun moyen de déboguer.

Ce que je recommanderais probablement, c’est de lancer une nouvelle VM, d’y installer Discourse et de restaurer une sauvegarde. Quand cela fonctionne, mettez le site existant en mode lecture seule, sauvegardez, restaurez et changez le DNS (ou une adresse IP statique si vous y avez accès).

Vous pouvez utiliser Déplacer un site Discourse vers un autre VPS avec rsync afin que le nouveau site ait des certificats valides et que vous puissiez y jeter un œil en modifiant votre DNS local pour qu’il pointe vers la nouvelle adresse IP.