juju status fails with connection timed out (1.9.12-precise-i386)

[Matthew Williams]

On precise, after running juju bootstrap --upload-tools followed by juju status -v I get the following error:

juju version = 1.9.12-precise-i386

juju status -v
2013/03/25 16:03:03 INFO JUJU:juju:status environs/ec2: opening environment "ama
zon"
2013/03/25 16:03:04 INFO JUJU:juju:status environs/ec2: waiting for DNS name(s)
of state server instances [i-d894b2b1]
2013/03/25 16:03:05 INFO JUJU:juju:status state: opening state; mongo addresses:
 ["ec2-50-16-55-110.compute-1.amazonaws.com:37017"]; entity ""
2013/03/25 16:03:05 INFO JUJU:juju:status state: connecting to 50.16.55.110:3701
7
2013/03/25 16:04:08 ERROR JUJU:juju:status state: connection failed: dial tcp 50
.16.55.110:37017: connection timed out
2013/03/25 16:04:08 INFO JUJU:juju:status state: connecting to 50.16.55.110:3701
7
2013/03/25 16:05:11 ERROR JUJU:juju:status state: connection failed: dial tcp 50
.16.55.110:37017: connection timed out

...etc

The same happens when I try to juju ssh 0.

By logging into the aws web management console I can see the state server has started and can see the following in the system log.

juju-db start/running, process 8434
2013/03/25 15:44:59 INFO JUJU:jujud:bootstrap-state state: opening state; mongo addresses: ["localhost:37017"]; entity ""
2013/03/25 15:44:59 INFO JUJU:jujud:bootstrap-state state: connecting to 127.0.0.1:37017
2013/03/25 15:44:59 ERROR JUJU:jujud:bootstrap-state state: connection failed: dial tcp 127.0.0.1:37017: connection refused

Scrolling up I can see a 404 error when it looks like we're trying to get the mongo package:

Setting up liberror-perl (0.17-1) ...
Setting up git-man (1:1.7.9.5-1) ...
Setting up git (1:1.7.9.5-1) ...
2013-03-25 15:44:59 URL:https://s3.amazonaws.com/juju-.............
http://juju-dist.s3.amazonaws.com/tools/mongo-2.2.0-precise-i386.tgz:
2013-03-25 15:44:59 ERROR 404: Not Found.

[John A Meinel (jameinel)]

=== modified file 'environs/ec2/ec2.go'
--- environs/ec2/ec2.go 2013-03-21 04:04:27 +0000
+++ environs/ec2/ec2.go 2013-03-25 17:54:17 +0000
@@ -244,6 +244,7 @@
        flags := environs.HighestVersion | environs.CompatVersion
        v := version.Current
        v.Series = env.Config().DefaultSeries()
+ v.Arch = "amd64"
        // TODO: set Arch based on constraints (when they are landed)
        return environs.FindTools(env, v, flags)
 }
@@ -286,7 +287,7 @@
        }
        v := version.Current
        v.Series = tools.Series
- v.Arch = tools.Arch
+ v.Arch = "amd64"
        mongoURL := environs.MongoURL(e, v)
        inst, err := e.startInstance(&startInstanceParams{
                machineId: "0",
@@ -449,7 +450,7 @@
        spec, err := findInstanceSpec(&instanceConstraint{
                region: e.ecfg().region(),
                series: scfg.series,
- arches: []string{scfg.tools.Arch},
+ arches: []string{scfg.tools.Arch, "amd64"},
                constraints: scfg.constraints,
        })
        if err != nil {

[John A Meinel (jameinel)]

That would force it to bootstrap and amd64 instance, so that it has the right mongod tools

[Matthew Williams (mattyw)]

I guess another solution for now is to just use 64bit ubuntu with juju-core?

[William Reade (fwereade)]

We don't cross-compile at the moment, so this won't work with --upload-tools for developers, but i386 versions of tools are also released.

[William Reade (fwereade)]

created lp:1191430 to track the remaining (known) arch issue