Comment 4 for bug 1583683

I downloaded, compiled and ran the mgopurge script on the MongoDB and it cleaned up a long list of transactions in the database. I then restarted the machine agent on machine-0 and it came up correctly without the errors from the previous tries. After about 2 minutes juju logs recorded that juju started the "upgrader" service and it completed correctly and juju queries no longer stated that juju was upgrading.

So, that did solve the problem.

With regards to how the mongoDB got into this state in the first place, we would have to dig into it more to find some clues as the log files for the original error were rotated out of the current log files before capture.

The state server was rebooted originally because of slow performance of queries to the API.