Restarting jujud on machine-0 seems to have resolved the situation:
# restart jujud-machine-0
I noticed whilst doing that that mongo seems to have burped: /var/log/upstart/juju-db.log.1.gz
https://pastebin.canonical.com/146061/
Restarting jujud on machine-0 seems to have resolved the situation:
# restart jujud-machine-0
I noticed whilst doing that that mongo seems to have burped: /var/log/ upstart/ juju-db. log.1.gz
https:/ /pastebin. canonical. com/146061/