Comment 2 for bug 1469077

I am using juju 1.24.2 and I am still seeing this problem.
Jujud goes a bit mad when started and goes to 100% cpu and spews out a lot of messages about leadership elections.
Then the API can be unresponsive and I get a lot of messages about the api exiting.
If I restart jujud on node 0, it fixes the unresponsiveness for a while, but then fails again after a while.

Here is my all-machines.log from the juju bootstrap node, in case the log files help.