Q: If you have an old DB from Discourse install, v2.0 > export - import > 2.9 - will it fail or is there a conversion process built into import to allow a successful importation?

Thank you for your replay but simply removing polls is not a solution to duplicate records. I assume somewhere early on the import from phpbb3 was incorrect and created those records. They are valid they just have duplicate UUID’s since original imported did not check for that. Anyway, the solution…

Ah thanks, that seems to work, except now failing to bootstrap on rebuild app. Seems to be a “discourse database already exists: type error” in there as well as ruby/gems error at the boot strap warning.

I’ve read through some of the errors. For context, this 2.2b4 build (PG10) is the original import setup and build used to import form another old school forum platform - this it has not had any updates or changes made since afaik. My impression is the solution may be to comment out some lines some…

You’d need to include your file for real help. If you see stuff like apt get Or something about modifying Gemfile, that would be stuff to remove. What I would probably do =given that the database upgrade worked) is rename your app.yml and run discourse-setup (assuming that your current file has…

Cool thanks for the pointers. I’ll try the rm app.yml and see what happens. When you say file do you mean errors in terminal or the app.yml or a different file? Extra info - I’m spinning up a droplet for learning and puzzling it out so I better understand how to maintain with the bonus of peace of…

Ok, tried all that - spun up new droplet, :white_check_mark: updates OS/Docker :white_check_mark: stopped container :white_check_mark: rm app.yml :white_check_mark: discourse-setup = upgraded PG10 :x: rebuild FAILED bootstrap (looks identical to yesterday’s error messages.) The errors that I…

[이미지] agemo: I didn’t run this on/and trash a live forum In that case, just do a new installation, backup the old site, and restore it to the new site.

Ha ha, that was kind of my OP angling. If it’s that simple then all my problem are solved. See, my concern was I’d be exporting from PG10 into shiny new 2.9 which is PG13 is it not, and so will it suck in the database - my assumption would be no. Thus in backup and restore scenario, in this conte…

[이미지] agemo: Is admin export/import sufficient without first upgrading the older DB Yes, it is, but you might need to fix a problem with your current DB before you can restore it on 2.9. [이미지] agemo: duplicate key value violates unique constraint "index_poll_options_on_poll_id_and_digest…

So it sounds like you have a corrupt index? (I didn’t notice but that’s what the last reply suggests). If that’s the car then you can look around for some examples. Mostly, you try to reindex and see which indexes won’t rebuild, then delete (or fix if you’re clever) the errant records.

구버전 데이터베이스를 최신 버전으로 가져오기

제품 지원 자체 호스팅

gerhard (Gerhard Schlager) 5월 20, 2022, 11:30오전 10

네, 충분합니다. 하지만 2.9에서 복원하기 전에 현재 DB의 문제를 수정해야 할 수 있습니다.

다음은 작동할 수 있는 해결책입니다. 하지만 귀하의 경우 문제를 일으키는 투표 ID가 84b9c1be0d88b6592595e6e16827dbc1이므로, value로 %84b9c1be0d88b6592595e6e16827dbc1%를 사용해야 합니다.

글		댓글	조회수
Upgrade failed with "duplicate key value violates unique constraint" error Self-hosting	17	2705	2월 29, 2020
Migration from discourse v2.8.13 (on Ubuntu 20.04.6 LTS) to latest Self-hosting	3	873	8월 15, 2023
Error upgrading from 3.0.1 to 3.1.0 Self-hosting	14	969	3월 28, 2023
Import failing with `could not create unique index` Self-hosting	5	2968	6월 13, 2020
Upgrade failed: ERROR: relation "idx_regular_post_search_data" already exists Self-hosting	2	752	8월 21, 2020

구버전 데이터베이스를 최신 버전으로 가져오기

Related topics