Comment 9 for bug 1287718

Hi,

We're having the same issue on one of our juju environment after an upgrade from 1.18.3.1 to 1.20.11. The log of a manual launch is attached. mongo seems to be running fine.

It looks like jujud is not even trying to start the apiserver, for reasons unknown to me.

Could this be because of bad data in the mongo database ?

Let me know if I can provide any additionnal details, thanks.