Juju status infinite loop on Raring with EC2

[Patrick Hetu]

> I think mongodb on raring is not running on the port that Jujud is expecting:

I was wrong. Mongodb is started by cloud-init on the right port.

Bruno, but I think mongodb in raring don't have tls configuration
option enabled.

See last comment of this bug: https://bugs.launchpad.net/juju-core/+bug/1130209

This is the error I get trying to start it from the command line:

root at juju-dino-machine-0:~# /usr/bin/mongod --auth
--dbpath=/var/lib/juju/db  --sslPEMKeyFile
''/var/lib/juju/server.pem'' --sslPEMKeyPassword ignored --bind_ip
0.0.0.0 --port 37017 --noprealloc --smallfileserror
 command line: unknown option sslPEMKeyFile

You should have the same in your logs.

Patrick