Recover when Audit Ledger is out of sync with other ledgers

[AlexJonsson]

config / domain / plugins ledgers -> audit (holds latest hash of above three) Part 1 of config txn types is permissions (did the writer have the correct permission ledger?)

• Issue: if killing indy-node after writing latest hash on audit ledger, but not the first three, so node says we can't run
• Desired behavior: discard newer transactions and then play catchup

Comment origination

[WadeBarnes]

@lynnbendixsen, Have you ever run into this issue?

[lynnbendixsen]

Possibly (I didn't dig deep enough to know the root cause). The issue i saw that might be related was that I think I didn't wait long enough for catchup to complete on a new node, restarted it, and the new node would not come into consensus and had a lot of troubles catching up.