After upgrading from 2.4.2 to 2.6.x discourse is no longer working for us. The issue is discourse is trying to connect to port 3000 on 127.0.0.1. I have rebuilt web_only numerous times with ./launcher rebuild web_only Questions. What is supposed to be running on 127.0.0.1:3000? How to restart t…

[image] csmu: What is supposed to be running on 127.0.0.1:3000? as far as i know, that is the ruby install running on 3000 [image] csmu: How to restart that service? maybe do a full reboot reboot or sudo reboot

P.s please tell me you did a backup before you upgraded.

[image] IAmGav: please tell me you did a backup before you upgraded Yes. Auto backup. The data container is up and running.

[image] IAmGav: maybe do a full reboot It’s on a production server. Other services are running on that server.

You need to rebuild your data container and then rebuild web_only. There are some hints in PostgreSQL 12 update .

[image] pfaffman: You need to rebuild your data container I’ve run ./launcher rebuild data more than 5 times with no error messages. I’m grateful this is happening our server and not on a clients :slight_smile:

seems like the upgrade to postgres 12 failed somehow. Pups::ExecError: /root/upgrade_postgres failed with return #<Process::Status: pid 47 exit 1> Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn' exec failed with the params "/root/upgrade_postgres" 5a74b447cdef6a2db5ea79c2ae1e31f7…

[image] csmu: upgrade to postgres 12 failed somehow In this case the tables for the discourse database were all dropped somehow. I decided to roll back to 2.4 and restore the discourse database.

Discourse ne parvient pas à se connecter au port 3000

Assistance produit

csmu (Keith John Hutchison - Ceiteach Seán Mac Úistin) Septembre 23, 2020, 9:00 11

Dans ce cas, les tables de la base de données Discourse ont toutes été supprimées d’une manière ou d’une autre.
J’ai décidé de revenir à la version 2.4 et de restaurer la base de données Discourse.

Sujet		Réponses	Vues
Why would discourse want to connect to port 3000 Product Support	5	1330	Septembre 23, 2020
Can't rebuild due to failed postgres 12 upgrade Self-hosting	44	4583	Juillet 13, 2020
Discourse on postgres 12 breaks upgrades Self-hosting	16	1243	Août 27, 2021
Bootstrap failed, please help :( Self-hosting	6	1089	Janvier 3, 2023
Rebuild fails on db:migrate w/PG12 Self-hosting	18	2289	Décembre 31, 2022

Discourse ne parvient pas à se connecter au port 3000

Sujets connexes