`discourse remap` falló

Soporte Instalación
1

Acabo de mover un foro de name.com a forum.name.com, pero falló:

Error: ERROR: el valor de clave duplicado viola la restricción de unicidad “unique_post_links”
DETALLE: La clave (topic_id, post_id, url)=(246, 813, http://forum.name.com) ya existe.
El remapeo solo se aplicó parcialmente debido al error anterior. Por favor, vuelve a ejecutar el script.

Así que lo ejecuté de nuevo (falló de nuevo), luego ejecuté rake posts:rebake y revisé el foro, encontrando algunas instancias de forum.forum.name.com. (Entonces, ¿debo ejecutar discourse remap forum.forum.name.com forum.name.com y rake posts:rebake para intentar solucionarlo? Con cierto éxito; tuve que cambiar algunas instancias manualmente).

Tengo algunas preguntas:

  • ¿discourse remap name.com forum.name.com solo se aplica al contenido de las publicaciones? De no ser así, ¿son solo los Ajustes del Sitio los que debo revisar para encontrar posibles problemas?
  • ¿Debe ejecutarse en algún tipo de transacción? (De ser así, no pareció hacerlo cuando falló en mi caso)
2

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

4 Me gusta
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 me gusta