Today’s upgrade to latest failed: FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 3194 exit 1> Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn' exec failed with the params…

[Bild] 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 and getting this: discourse-data-explorer is already at latest compatible version I, [2020-08-28T17:53:57.578920 #1…

Thanks, but I can’t get into the app: ./launcher enter app Error response from daemon: Container 694b24a2a235e90456fb0ca770c86ac14bb914ad33ada8a18fc4777a1188d848 is not running root@gaoa-discourse:/var/discourse# And also: root@gaoa-discourse:/var/discourse# su - postgres No passwd entry for user…

So restart the container? ./launcher start app Then you want something like: ./launcher enter app then: su postgres -c 'psql discourse'

Thanks! Not sure why it wasn’t starting the first time I tried. It looks like I have a duplicate “10” id: 4374 | discourse-data-explorer | q:-10 | JSON | {"id":-10,"name":"Inactive Users with no posts","description":"analyze pre-Discourse signups.","sql":"SELECT\ n u.id,\n u.username_lo…

The numbers in the ID column are 4374 and 4114. Delete the highest numbered one. Do NOT run DELETE from plugin_store_rows WHERE id = 10!! or you will delete the wrong entry!

Ah, so this? DELETE from plugin_store_rows WHERE id = 4374;

Yes. You should see the correct column header in the plsql query output no?

Now that you mention it, yes. I’d scrolled down because the output is like this: [psql output]

Yep, also, in general consider running commands to see their impact before committing, see: [Bild] PostgreSQL - TRANSACTIONS - Tutorialspoint Then if you find you have deleted 500 rows when you meant to hit just one, you have the chance to rollback without fear.

Success! :tada: Thanks for the guidance @merefield . My DELETE command was missing a closing semicolon (updated above).

[Bild] omarfilip: My DELETE command was missing a closing semicolon (updated above). Oh yes, that gets me every time :wink:

Fehlgeschlagenes Upgrade: UniqueViolation: doppelter Schlüsselwert verletzt eindeutige Beschränkung "data_explorer_queries_pkey"

Unterstützung Installation

merefield (Robert) 10. September 2020 um 19:57 4

Also den Container neu starten?

./launcher start app

Dann möchtest du so etwas wie:

./launcher enter app

dann:

su postgres -c 'psql discourse'

Modifying the database inside of a backup to remove a duplicate key tag so that it doesn't fail when restoring

Problem after Discourse update

Urgent, upgraded build failed UniqueViolation

Thema		Antworten	Aufrufe
Duplicate data explorer key blocking rebuild Support	6	1096	5. Oktober 2020
Upgrade failed with "duplicate key value violates unique constraint" error Self-hosting	18	2513	30. März 2020
2.7.0.beta2 upgrade failed with ERROR: duplicate key Self-hosting	25	2286	25. Februar 2021
Upgrade fails while migrating Self-hosting	6	906	31. Dezember 2022
Update failed - PG::UniqueViolation: ERROR Self-hosting	8	844	14. November 2021

Fehlgeschlagenes Upgrade: UniqueViolation: doppelter Schlüsselwert verletzt eindeutige Beschränkung "data_explorer_queries_pkey"

Verwandte Themen