I used the one-click browser upgrade to attempt to upgrade from 2.7.0.beta1 to 2.7.0.beta3. It first updated docker, apparently successfully. Then, as instructed, I executed the following on the server: cd /var/discourse git pull ./launcher rebuild app It completed and said I needed t…

Can you paste more lines of the rebuild output? We need some lines earlier than that in order to be able to troubleshoot.

It looks like the culprit may be: I, [2021-02-01T22:13:56.638190 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' 2021-02-01 22:14:05.011 UTC [4123] discourse@discourse ERROR: duplicate key value violates unique constraint "index_users_on_username" 2021-0…

[이미지] rcauvin: ERROR: duplicate key There have been a few recent topics about fixing the duplicates. Example: [이미지] 2.7.0.beta2 upgrade failed with ERROR: duplicate key Self-hosting I was upgrading from 2.7.0.beta1 and got this error message: 2021-01-2…

Thanks. I am having trouble gettting psql to work. I restarted the container: ./launcher start app Then I executed: ./launcher enter app then: su postgres -c 'psql discourse' But the output was: psql: error: could not connect to server: could not connect to server: No such file or directory …

Try sudo -u postgres psql discourse

Try sudo -u postgres psql discourse Same error message, unfortunately.

[이미지] rcauvin: Same error message Did it run through the first iteration of launcher rebuild OK? If it did, your database was already upgraded to Psql 13, while your Psql binaries in the old app image still expect a database version 10 or 12, depending on what you’re upgrading from. cd /var…

I followed these steps and successfully renamed the duplicate user. But then I encountered this issue when trying to re-index. @sam had suggested in that thread: “Yes please nuke the dupe rows”, but I don’t know what that means in the context of the warnings and error messages I get when re-indexin…

Those are temporary indexes that were created while the reindexing was working. Every time it crashed due to duplicates, it would leave at least one temporary index behind. You can tell by the name, which ends in ccnew, ccnew1, ccnew2, and so on. You can get rid of them by entering Psql and issuing…

Thanks again, Gunnar. I was able to drop some of the ccnew indexes but not all: discourse=# DROP INDEX public.index_incoming_referers_on_path_and_incoming_domain_id_ccnew; DROP INDEX discourse=# DROP INDEX public.incoming_referers_pkey_ccnew1; DROP INDEX discourse=# DROP INDEX public.index_incoming…

2.7.0.beta1에서 2.7.0.beta3로 업그레이드 실패

지원 자체 호스팅

omarfilip 2월 1, 2021, 10:40오후 7

There have been a few recent topics about fixing the duplicates. Example:

글		댓글	조회수
Forum offline due to failed rebuilds on Tests-Pass Self-hosting	1	1199	12월 11, 2020
Forum crashes after upgrading from 2.4.0 Self-hosting	9	1555	7월 4, 2020
Help! Upgrade led to complete fail Self-hosting	7	1471	3월 9, 2021
PostgreSQL 13 update Announcements	2	11245	9월 13, 2023
Failed upgrade from 2.5.0beta4 to 2.5.0beta5 Self-hosting	5	1233	5월 30, 2020

2.7.0.beta1에서 2.7.0.beta3로 업그레이드 실패

Related topics