`discourse remap` falhou

Suporte Instalação
1

Acabei de mover um fórum de name.com para forum.name.com, mas falhou:

Erro: ERRO: valor de chave duplicada viola a restrição de unicidade “unique_post_links”
DETALHE: A chave (topic_id, post_id, url)=(246, 813, http://forum.name.com) já existe.
O remapeamento foi aplicado apenas parcialmente devido ao erro acima. Por favor, execute o script novamente.

Então, executei-o novamente (falhou novamente), depois fiz rake posts:rebake e verifiquei o fórum, encontrando algumas instâncias de forum.forum.name.com. (Então, executei discourse remap forum.forum.name.com forum.name.com e rake posts:rebake para tentar corrigir — com algum sucesso; precisei alterar algumas instâncias manualmente).

Tenho algumas perguntas:

  • O comando discourse remap name.com forum.name.com aplica-se apenas ao conteúdo das postagens? Caso contrário, devo verificar apenas as Configurações do Site para encontrar possíveis problemas?
  • Ele deve ser executado dentro de alguma transação? (Se sim, não pareceu ser o caso quando falhou para mim).
2

No, it applies to the entire database. Posts, site settings, themes, uploads, everything.

4 curtidas
3

Ah yeah looking at the full error again now it seems to have gone through these:

backup_metadata=1
categories=6
email_logs=306
email_tokens=1
groups=1
incoming_domains=3
incoming_emails=3
javascript_caches=4
post_custom_fields=275
post_revisions=134
posts=441
post_search_data=50
search_logs=8
site_settings=5
stylesheet_cache=540
theme_fields=9
theme_settings=3

I’ve checked all site settings and they’re fine (as are themes) and I guess all the above were done - can you see anything that should have been done that wasn’t? Do you think it is safe to continue as is or do you think it needs to be redone from scratch?

Also any ideas why duplicate key value violates unique constraint errors are becoming more frequent on Discourse? I’ve noticed a few topics on this and I think this is the third time I’ve had such an issue myself.

4

Not from the output, no. We only output tables with changes. No way to know if a table not in the list because it of the error, or simply because there were no instances of name.com in the (not listed) table.

Unfortunately that’s beyond my expertise.

5

Thanks Joshua.

Any ideas what the numbers signify? Number of changes?

What is the recommended way forward now? Fix the unique constraint error then reverse (go from forum.name.com back to name.com, then back again) or do something else?

Edit: done

I entered the app and Rails console then deleted the TopicLink in question then went from forum.name.com back to name.com, then back again.

backup_metadata=1
categories=6
email_logs=318
email_tokens=2
groups=1
incoming_domains=3
incoming_emails=3
javascript_caches=4
post_custom_fields=277
post_revisions=140
posts=444
post_search_data=51
search_logs=10
site_settings=5
stylesheet_cache=564
theme_fields=9
theme_settings=3
topic_links=281
topics=30
topic_search_data=8
translation_overrides=1
uploads=54
user_auth_token_logs=48
user_emails=2
user_histories=189
Done
1 curtida