Continuing the discussion from Backup to S3 command? : Further to attempting to backup via ./launcher enter I have since found what seems to be the reason that the backups have ceased working. pg_dump: Dumping the contents of table "topic_links" failed: PQgetResult() failed. pg_dump: Error message …

[image] wincenworks: Error message from server: ERROR: invalid memory alloc request size 18446744073709551613 That looks like a problem. Is this a standard install ? What version of postgres is this? You said that there was some problem with this server and that’s why you’re trying to move f…

[image] pfaffman: Is this a standard install ? Current install is: 2.7.0.beta1 The server has a complicated history (it’s about five years old) and was a standard install self-hosted, then transferred to Discourse hosting, then transferred back - we’ve tried to keep it as standard as possible…

I think I would copy the entire /var/discourse to a new server to get away from whatever is wrong with that server and then try to get things straight. You may have a corrupt index, but I’m in my phone and can’t quite make sense of the errors.

Just tried that - took some fussing about. New system does not like it, pretty much just outright rejects the database. Launcher is up-to-date Stopping old container + /usr/bin/docker stop -t 60 app app cd /pups && git pull && /pups/bin/pups --stdin Already up to date. I, [2020-12-13T09:23:39.2913…

It’s trying to upgrade postgres. So much of that is expected. Maybe it’ll it over again and change to the pg 10 template as described in PostgreSQL 13 update

The line to prevent upgrade is still in the YML file. I can enter the app and access the SQL on the old server, when I try on the new it returns: psql: error: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix doma…

[image] wincenworks: 2020-12-13 09:23:51.363 UTC [1583] FATAL: database files are incompatible with server The line above seems to be the root problem @wincenworks I cannot tell you what to do, but if I were you @wincenworks , I would install Discourse from scratch; and before building the …

Trying to get a new instance with PG10 running right now, keepings timing out at the final stage of the registration process. [image] neounix: instance from your current PG10 backup I would absolutely love to do that but: It won’t let me make a new backup Previous backups don’t restore He…

[image] wincenworks: Previous backups don’t restore Yes, it will not restore on your current configuration, as I understood you. Have you tried using that backup to restore after a full fresh install, as I mentioned? First, install Discourse from scratch, make sure it is 100% up and running…

Sauvegarde échouée en raison d'erreurs PG/SQL

Soutien Installation

pfaffman (Jay Pfaffman) Décembre 13, 2020, 5:49 6

Il essaie de mettre à niveau PostgreSQL. Une grande partie de cela est attendue.

Peut-être qu’il recommencera et passera au modèle pg 10 comme décrit dans Mise à jour PostgreSQL 13

Sujet		Réponses	Vues
Forum crashes after upgrading from 2.4.0 Self-hosting	10	1183	Août 3, 2020
Stuck and lost updating forum, problems with PG migration Self-hosting	15	392	Juin 12, 2025
Backup has failed. pg_dump: server version: 9.6.3; pg_dump version: 9.5.10 Development	8	9127	Décembre 2, 2017
When rebuild, Discourse removes PostGreSQL 10 and reinstalls version 9.5 Self-hosting	6	1033	Mai 8, 2020
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Self-hosting	13	2005	Février 15, 2021

Sauvegarde échouée en raison d'erreurs PG/SQL

Sujets connexes