juju-core fails to bootstrap on ec2

[Matthew Williams]

On 31/03/13 10:11, Zhengpeng Hou wrote:
> Hi
> Installed the release from go ppa, generated config with juju init
> then tried to bootstrap, the instance on ec2 has been launched 
> successfully, but not bootstraped.
> ^Cfreeflying at x220:/tmp$ juju status  --debug
> 2013/03/31 16:04:08 INFO JUJU:juju:status environs/ec2: opening 
> environment "amazon"
> 2013/03/31 16:04:09 INFO JUJU:juju:status environs/ec2: waiting for 
> DNS name(s) of state server instances [i-5a9f0439]
> 2013/03/31 16:04:12 INFO JUJU:juju:status state: opening state; mongo 
> addresses: ["ec2-184-73-133-195.compute-1.amazonaws.com:37017 
> <http://ec2-184-73-133-195.compute-1.amazonaws.com:37017>"]; entity ""
> 2013/03/31 16:04:18 INFO JUJU:juju:status state: connecting to 
> 184.73.133.195:37017 <http://184.73.133.195:37017>
> 2013/03/31 16:04:18 ERROR JUJU:juju:status state: connection failed: 
> dial tcp 184.73.133.195:37017 <http://184.73.133.195:37017>: 
> connection refused
> 2013/03/31 16:04:18 INFO JUJU:juju:status state: connecting to 
> 184.73.133.195:37017 <http://184.73.133.195:37017>
> and there is no agent and mongodb being launched when I ssh into the 
> instance.
> Is this my own corner case or a bug I shall file to lp?
> Cheers
> Zhengpeng
>
>
Hi Zhenpeng,

Sounds similar to an issue I had
https://bugs.launchpad.net/juju-core/+bug/1159885

Are you using a 32 bit version of ubuntu?

Thanks

Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130402/e34a11d2/attachment-0001.html>