The user csmu is experiencing issues with Discourse after upgrading from 2.4.2 to 2.6.x, where the application is trying to connect to port 3000 on 127.0.0.1. IAmGav suggests that the issue might be related to the Ruby install running on port 3000 and recommends a full reboot. However, csmu mentions that a reboot is not feasible as the server is in production and other services are running on it.
csmu later discovers that the upgrade to Postgres 12 failed, resulting in the tables for the Discourse database being dropped. pfaffman suggests rebuilding the data container and then rebuilding web_only, but csmu has already tried this multiple times without success. Ultimately, csmu decides to roll back to version 2.4 and restore the Discourse database.
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.
Cheers and thanks!
as far as i know, that is the ruby install running on 3000
maybe do a full reboot
reboot or sudo reboot
P.s please tell me you did a backup before you upgraded.
Yes. Auto backup. The data container is up and running.
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.
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 
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"
5a74b447cdef6a2db5ea79c2ae1e31f71d1d476179a3f61ea61fc21bf8382229
** 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.
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.