Comment 14 for bug 1797816

Hello, John.

We are trying this on a 'isolated' mongodb, where we imported the dump pointed to by Felipe earlier in this bug. After applying all the .update and .remove commands you suggesteed mgopurge now breaks with different message:

2018-10-17 09:06:49 ERROR failed stage resume: cannot find document {actions 6a783ac4-0b48-45a3-87fc-9646f8bd82de:5c141543-7e4b-4bbb-8881-7458104cc334} for applying transaction 5ac24a1e5540e3051792857b_ded72eda

Indeed, I can not find that document in the database. Is it safe to just remove this transaction? (5ac24a1e5540e3051792857b_ded72eda)? Also, if we run into more of this 'orphaned' transactions, can we safely remove them?

Here is the full output of the commands run just after the import of the dump: https://paste.ubuntu.com/p/GP4ksw7xjK/