Comment 5 for bug 1583683

Unfortunately, there is not much more information to go on.
By the time we were able to look into the logs the relevant time had been rotated out and all we could see was the juju and mongodb logs after the reboot.

So, no information on how it got into this state in the first place. We only know that Juju queries were extremely slow, but were completing. Operations decided to reboot the machine in an attempt to fix the slow performance.