Hello, site is suddenly stuck at Welcome to nginx! so debugging and running into these errors. Success. You can now start the database server using: pg_ctlcluster 10 main start Warning: The selected stats_temp_directory /var/run/postgresql/10-main.pg_stat_tmp is not writable for the cluster o…

[image] jameshahnii: The source cluster was not shut down cleanly. There is a FAQ entry just for this in PostgreSQL 12 update .

Thanks for the quick response! Yes, I tried that as well. root@bitkcor:/var/discourse# ./launcher start app starting up existing container + /usr/bin/docker start app Error response from daemon: driver failed programming external connectivity on endpoint app (49f1fdf896618efc824e50f782c1fba91bf813…

[image] jameshahnii: listen tcp 0.0.0.0:80: bind: address already in use Somehow, someone installed nginx on your host. You should remove any extraneous web servers from your VPS and then follow the instructions.

nginx is installed because this has been a working forum for a couple years now. Was late with Digital Ocean and the Droplet got turned off. After turning it back on, I’m getting a 521 error going to the address. When I go to the IP Address I’m back to the Welcome screen. The Cloudflare configurati…

[image] jameshahnii: the Droplet got turned off So you had nginx installed but not running. Turning the droplet off and turning it back on restarted the service and now it blocks the web port. You should really uninstall it so this doesn’t happen every time the server restarts…

Has something changed? When I built this the nginx welcome screen was part of the install process. I was under the impression nginx was necessary to run Discourse. How do I uninstall it?

[image] jameshahnii: shared/data/log/var-log/postgres/current Please change the path to tail -f shared/standalone/log/var-log/postgres/current The path mentioned in guide references the two container install data container whereas it seems your install is the single container one.

Done. Gives me this. root@bitkcor:/var/discourse# tail -f shared/standalone/log/var-log/postgres/current 2020-07-19 03:33:56.864 UTC [19933] discourse@discourse LOG: duration: 279.207 ms statement: COPY public.scheduler_stats (id, name, hostname, pid, duration_ms, live_slots_start, live_slots_fin…

Looks like postgres is running. Did you shut down Discourse container before checking logs? ./launcher stop app

I can’t seem to stop it. root@bitkcor:/var/discourse# ./launcher stop app + /usr/bin/docker stop -t 10 app app root@bitkcor:/var/discourse# tail -f shared/standalone/log/var-log/postgres/current 2020-07-19 03:33:56.864 UTC [19933] discourse@discourse LOG: duration: 279.207 ms statement: COPY publ…

MISE À NIVEAU DE POSTGRES ÉCHOUÉE - J'ai tout essayé

Soutien Installation

Falco (Falco) Août 24, 2020, 2:42 2

Il existe une entrée de FAQ dédiée à ce sujet dans Mise à jour PostgreSQL 12.

Sujet		Réponses	Vues
Can't rebuild due to failed postgres 12 upgrade Self-hosting	44	4060	Juillet 13, 2020
Forum crashes after upgrading from 2.4.0 Self-hosting	10	1298	Août 3, 2020
Updated to latest version: ./analyze_new_cluster.sh message Self-hosting	14	3876	Juin 25, 2020
Upgrade of postgres failed Self-hosting	1	1117	Septembre 25, 2020
Site Won't Start After Update Self-hosting	7	1118	Juillet 30, 2018

MISE À NIVEAU DE POSTGRES ÉCHOUÉE - J'ai tout essayé

Sujets connexes