User merge never finish

[Julien_Palard]

Hi!

Running a self-hosted Discourse 3.5.0.beta6-dev ( da0b303568 ), I tried a user merge today and it never completed.

Nothing interesting in /logs/.

Looks like the merge have been done (messages from the old merged account appears in the new account, inscription date of the new account has been updated to the inscription date of the merged account), so maybe it’s OK and the merge is successfull. Maybe it is only partial

Graphically it looks like it’s still working:

It’s been more than 30 minutes now, to merge two very small accounts (like 20 messages), so I bet it’s blocked or something. The load average on the server is 0.05 so it’s not working hard.

[per1234]

Hi @Julien_Palard.

@Julien_Palard

maybe it’s OK and the merge is successfull

Was the “from” account deleted? If not, the merge process didn’t complete.

I encountered a account merge hanging like this and reported my findings and the solution for the specific cause of the problem I had here:

I'm attempting to merge user accounts

I encountered a problem like this and thought I should share my findings here in case it might help anyone else who experiences it. In my case, the account merge operation hung forever with the “Merge progress” dialog cycling back and forth between the “Changing post ownership…” and “Updating username…” messages. From looking at the staff action logs (/admin/logs/staff_action_logs), I could see that, although the ownership of many posts was transferred immediately after I triggered the merge…

Even if you are able to solve the problem, I do think the lack of communication about the error could be considered a defect (even if one that only affects a very small percentage of users). It is not a very friendly behavior for the admin to have to go hunting through the logs to discover that the process has failed and the merge is never going to finish.

[Julien_Palard]

@per1234

Was the “from” account deleted? If not, the merge process didn’t complete.

Ohh good question! Yes the “form” account was deleted. That’s reassuring.

So, few hours later I still have the popup, I opened the console just in case, and found:

ℹ️ Discourse v3.5.0.beta6-dev — https://github.com/discourse/discourse/commits/da0b303568 — Ember v5.12.0 app.js:239:10
Erreur d’analyse XML : mal formé
Emplacement : https://discuss.afpy.org/message-bus/0dae6fbaeb7542e68e9ba597dee034e0/poll?dlp=t
Numéro de ligne 1, Colonne 4 : 4 poll:1:4
Erreur d’analyse XML : mal formé
Emplacement : https://discuss.afpy.org/message-bus/0dae6fbaeb7542e68e9ba597dee034e0/poll
Numéro de ligne 1, Colonne 4 : poll:1:4

[kris.kotlarek (Kris)]

Thank you for reporting this bug. A background job does the merge user action, and once finished, MessageBus sends a message to the user to inform them about the result and close the modal.

Based on your console output and check that the original user was deleted, only the last step failed.

One reason for XML parsing error: malformed is problems with the SSL certificate.

I see that your certificate was issued 25th of May, so I wonder if that can be related.

Do you see that error in the console only during merge or also while regular use of the forum?

The easiest way to test if MessageBus is working correctly would be to open the browser console and change any Site Setting (when the site setting is updated, MessageBus also sends a message to clients). Do you see errors in that case?

[Julien_Palard]

@kris.kotlarek

One reason for XML parsing error: malformed is problems with the SSL certificate.

Are you sure? How SSL and XML are related? I don’t see any relation here.

Do you see that error in the console only during merge or also while regular use of the forum?

I tried to reproduce by just navigating and BOOM I’ve seen one occurrence happening by just opening the admin interface, the response to the message-bus was triggering the XML parse failure was:

You’ve performed this action too many times. Please wait 1 minute before trying again.