I was upgrading from 2.7.0.beta1 and got this error message: 2021-01-22 20:16:22.015 UTC [4055] discourse@discourse LOG: duration: 75335.241 ms statement: UPDATE notifications SET processed = true 2021-01-22 20:16:23.792 UTC [4055] discourse@discourse LOG: duration: 1776.591 ms statement: ALTER…

I think you can get the site back up with ./launcher start app Then take a look at ways to delete the duplicate: [image] Duplicate data explorer key blocking rebuild support Hey all, Rare I ask for help, but I’m puzzled about how to resolve this. Just rebuilt my site a…

More information I should probably provide: This is a single container install. The first rebuild completed without any errors. This error occurred when I was running the second rebuild, after the first rebuild completed successfully. Thanks, Gunnar

Do you have enough disk space? Error related to the required PostgreSQL update to version 13 afaik. Did you follow this upgrade method ? cd /var/discourse git pull ./launcher rebuild app If you search the forum for those errors you’ll see a lot of past information and possible fixes. [image] …

I got the site back up by renaming postgres_data_old back to postgres_data and then running ./launcher start app to start the old image. So, I’m back to square 1, but at least the site is up. I tried to find the duplicate key, by entering this: select * from users WHERE username = 'DaveW'; (user…

You do have two, possibly capitalized differently in the DB: [Screen Shot 2021-01-22 at 3.25.53 PM]

[image] omarfilip: You do have two Did you visit my site? :wink: I see what you mean, when I search the in the GUI, I do see two. However, when I click on both as an admin and bring up the details page, they appear to be the same user. I can’t find a single detail that’s different between th…

[image] Gunnar: Did you visit my site? :wink: Of course! :grinning: That should delete 19732 but I can’t guarantee the absence of any ill effects. In any case, a backup before proceeding further is advisable.

You might also change the username of one of the duplicates.

[image] pfaffman: change the username Right. Once I do, should I be able to restart the upgrade from scratch? I.e. run rebuild twice? Thanks! Gunnar

That should work. Unless there are other duplicate users.

[image] pfaffman: Unless there are other duplicate users. Turns out there are, at least one. PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_users_on_username_lower" DETAIL: Key (username_lower)=(robs) already exists. Is there any way I can scan the datab…

La mise à niveau 2.7.0.beta2 a échoué avec l'erreur : clé dupliquée

Soutien Installation

omarfilip Janvier 22, 2021, 8:37 2

Je pense que vous pouvez remettre le site en ligne avec ./launcher start app

Ensuite, jetez un œil aux méthodes pour supprimer la doublon :

5 « J'aime »

Sujet		Réponses	Vues
Upgrade failed with "duplicate key value violates unique constraint" error Self-hosting	18	2499	Mars 30, 2020
PG::UniqueViolation Problem during 3.1.0.beta4 upgrade Self-hosting	6	606	Mai 19, 2023
Upgrade Issues: Failed Upgrade due to Duplicate Key, Failed Snapshot Restore Self-hosting	7	1689	Avril 25, 2023
[Site Down :(] Upgrade\Rebuild Failure - DB Migration Issue? Self-hosting	9	681	Juin 19, 2023
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Self-hosting	13	2005	Février 15, 2021

La mise à niveau 2.7.0.beta2 a échoué avec l'erreur : clé dupliquée

Sujets connexes