This is a post is a very condensed version of my last 24hrs, although it hasn’t actually worked yet so i’m also hoping someone will post where it went wrong below this. My Discourse update failed due to a duplicate key, one of my tags is doubled up. To fix the update issue i needed to do a fresh Di…

[画像] Drew: My Discourse update failed due to a duplicate key, one of my tags is doubled up. To fix the update issue i needed to do a fresh Discourse install Why? Why could you not fix this ‘online’ by restarting the app, entering the container, entering postgres and then dealing with the d…

I wasn’t expecting the error so had already put the new version of Discourse onto my server. The duplicate key error was in the backup and not in the clean installed app, but i couldn’t restore the backup because it wanted the error fixed first. So i had to try and edit the tag inside the backup.

But you saw the error on update? Next time make your life easier and fix in place.

The app wasn’t running and i couldn’t reload it, so i updated to a fresh Discourse version in an attempt to fix that. Which meant that i didn’t have access to the database anywhere other than the backup. Certainly this is a niche case i’ve posted here, the better option would be to notice the issue…

No worries. At least you’ve shown it is possible, learned some new stuff and given others an additional option. Good work! :clap:

Thanks, although the original file was 128MB and the new one is 29MB, so i think rezipping on the server may have truncated the file due to its length. This process seems like it should work, but the file i ended up with could not be used to restore my discourse.

The path you took was more risky but surely doable? Maybe someone can chime in with some advice on this issue. You can presumably repeat this again from the backup so …

Is this problem resolved? It reads as if it’s a how-to, but it seems like your site is still broken. [画像] Drew: This process seems like it should work, but the file i ended up with could not be used to restore my discourse. [画像] Drew: The app wasn’t running and i couldn’t reload it Ma…

Thanks for replying. [画像] Jay Pfaffman: ./launcher start app to start the old container, was there a reaason that you couldn’t do that? It refused to start as we were a few upgrades behind, so i updated to the latest Discourse by creating a new one and uploading our old backup, but it reject…

[画像] Jay Pfaffman: Is this problem resolved? It reads as if it’s a how-to I was hoping someone might see an error in it and correct me, so it would become a ‘how to’ guide.

復元時に失敗しないように、重複キータグを削除するためにバックアップ内のデータベースを変更する

サポートインストール

merefield (Robert) 2023 年 7 月 27 日午後 12:48 2

なぜですか？

アプリを再起動したり、コンテナに入ったり、Postgres に入ったりしてから、すぐにデータ入力に対処したりして、この問題を「オンライン」で解決できなかったのはなぜですか？

トピック		返信	表示
SQL Error during import Self-hosting	18	2374	2015 年 5 月 3 日
Can't restore due to corrupt indexes (with some clues on how to deal with corrupt indexes) Self-hosting	12	4769	2020 年 1 月 6 日
Problems while updating from 3.0.0 to 3.0.1 Self-hosting	16	1264	2023 年 6 月 14 日
Problem with restore Discourse from backup (3.4, quite large DB) Support	17	338	2025 年 1 月 14 日
Error restoring backup "key is duplicated" Self-hosting	7	1866	2017 年 8 月 30 日

復元時に失敗しないように、重複キータグを削除するためにバックアップ内のデータベースを変更する

関連トピック