ERROR juju.cmd supercommand.go:300 waited for 10m0s without being able to connect: /var/lib/juju/nonce.txt does not exist

Wed May 14 10:19:56 UTC 2014

Thanks.
Now it works!
I now use the juju from the PPA, which is newer than that in trusty.

sudo add-apt-repository ppa:juju/stable sudo apt-get update && sudo apt-get
install juju-core

root at maas:/home/ceph# juju bootstrap --show-log

2014-05-14 09:07:12 INFO juju.cmd supercommand.go:302 running
juju-1.18.3-trusty-amd64 [gc]

2014-05-14 09:07:12 WARNING juju.cmd.juju common.go:40 ignoring
environments.yaml: using bootstrap config in file
"/root/.juju/environments/maas.jenv"

2014-05-14 09:07:12 INFO juju.environs open.go:177 environment info already
exists; using New not Prepare

2014-05-14 09:07:13 INFO juju.environs.bootstrap bootstrap.go:46
bootstrapping environment "maas"

2014-05-14 09:07:13 INFO juju.environs.tools tools.go:186 filtering tools
by released version

2014-05-14 09:07:13 INFO juju.environs.tools tools.go:86 reading tools with
major.minor version 1.18

2014-05-14 09:07:13 INFO juju.environs.tools tools.go:97 filtering tools by
series: trusty

2014-05-14 09:07:13 INFO juju.utils http.go:55 hostname SSL verification
enabled

2014-05-14 09:07:15 INFO juju.utils http.go:55 hostname SSL verification
enabled

2014-05-14 09:07:19 INFO juju.utils http.go:55 hostname SSL verification
enabled

2014-05-14 09:07:23 INFO juju.utils http.go:55 hostname SSL verification
enabled

2014-05-14 09:07:29 INFO juju.environs.bootstrap bootstrap.go:58 picked
newest version: 1.18.3

Launching instance

2014-05-14 09:07:31 WARNING juju.provider.maas environ.go:233 picked
arbitrary tools &{"1.18.3-trusty-amd64" "
https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgz"
"b54decd84ad21c5a3b924448bc865fa53f6552d230a89ed01d929db4fa8659b6"
%!q(int64=7385591)}

 - /MAAS/api/1.0/nodes/node-a2791000-d375-11e3-9bfb-c81f66b95a0e/

Waiting for address

Attempting to connect to jdreb.maas:22

Attempting to connect to 192.168.10.12:22

Logging to /var/log/cloud-init-output.log on remote host

Running apt-get update

Running apt-get upgrade

Installing package: git

Installing package: curl

Installing package: cpu-checker

Installing package: bridge-utils

Installing package: rsyslog-gnutls

Installing package: juju-mongodb

Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP
%{http_code}; time %{time_total}s; size %{size_download} bytes; speed
%{speed_download} bytes/s ' -o $bin/tools.tar.gz '
https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgz
'

Starting MongoDB server (juju-db)

Bootstrapping Juju machine agent

Starting Juju machine agent (jujud-machine-0)

2014-05-14 09:16:15 INFO juju.cmd supercommand.go:311 command finished

On Tue, May 13, 2014 at 4:06 PM, Andrew Wilkins <
andrew.wilkins at canonical.com> wrote:

> On Tue, May 13, 2014 at 4:04 PM, Andrew Wilkins <
> andrew.wilkins at canonical.com> wrote:
>
>> On Tue, May 13, 2014 at 12:41 PM, John Meinel <john at arbash-meinel.com>wrote:
>>
>>> You might be running into this:
>>>
>>> http://askubuntu.com/questions/458535/how-to-change-juju-bootstrap-time-from-the-10min-it-gives-you
>>> John
>>> =:->
>>>
>>>
>>> On Mon, May 12, 2014 at 4:47 PM, boyd yang <boyd.yang at gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I got juju bootstrap error.
>>>> I used Ubuntu 14.04 LTS.
>>>> How to fix this?
>>>> Thanks!
>>>>
>>>> root at maas:/home/ceph# juju bootstrap --show-log
>>>> 2014-05-12 12:21:06 INFO juju.cmd supercommand.go:297 running
>>>> juju-1.18.1-trusty-amd64 [gc]
>>>> 2014-05-12 12:21:06 INFO juju.environs open.go:177 environment info
>>>> already exists; using New not Prepare
>>>> 2014-05-12 12:21:06 INFO juju.environs.bootstrap bootstrap.go:46
>>>> bootstrapping environment "maas"
>>>> 2014-05-12 12:21:06 INFO juju.environs.tools tools.go:186 filtering
>>>> tools by released version
>>>> 2014-05-12 12:21:06 INFO juju.environs.tools tools.go:86 reading tools
>>>> with major.minor version 1.18
>>>> 2014-05-12 12:21:06 INFO juju.environs.tools tools.go:97 filtering
>>>> tools by series: trusty
>>>> 2014-05-12 12:21:06 INFO juju.utils http.go:55 hostname SSL
>>>> verification enabled
>>>> 2014-05-12 12:21:26 INFO juju.utils http.go:55 hostname SSL
>>>> verification enabled
>>>> 2014-05-12 12:21:30 INFO juju.utils http.go:55 hostname SSL
>>>> verification enabled
>>>> 2014-05-12 12:21:33 INFO juju.utils http.go:55 hostname SSL
>>>> verification enabled
>>>> 2014-05-12 12:22:18 INFO juju.environs.bootstrap bootstrap.go:58 picked
>>>> newest version: 1.18.3
>>>> Launching instance
>>>> 2014-05-12 12:22:20 WARNING juju.provider.maas environ.go:233 picked
>>>> arbitrary tools &{"1.18.3-trusty-amd64" "
>>>> https://streams.canonical.com/juju/tools/releases/juju-1.18.3-trusty-amd64.tgz"
>>>> "b54decd84ad21c5a3b924448bc865fa53f6552d230a89ed01d929db4fa8659b6"
>>>> %!q(int64=7385591)}
>>>>  - /MAAS/api/1.0/nodes/node-a2791000-d375-11e3-9bfb-c81f66b95a0e/
>>>> Waiting for address
>>>> Attempting to connect to jdreb.maas:22
>>>> Attempting to connect to 192.168.10.12:22
>>>> 2014-05-12 12:32:20 ERROR juju.provider.common bootstrap.go:123
>>>> bootstrap failed: waited for 10m0s without being able to connect:
>>>> /var/lib/juju/nonce.txt does not exist
>>>> Stopping instance...
>>>> Bootstrap failed, destroying environment
>>>> 2014-05-12 12:32:21 INFO juju.provider.common destroy.go:14 destroying
>>>> environment "maas"
>>>> 2014-05-12 12:32:21 ERROR juju.cmd supercommand.go:300 waited for 10m0s
>>>> without being able to connect: /var/lib/juju/nonce.txt does not exist
>>>>
>>>
>> The end of the last line there indicates something has gone wrong while
>> initialising the first MAAS node. We run a cloud-init script that creates
>> the nonce.txt file, which we use to verify the machine's identity.
>>
>> It looks like a bug in either Juju or MAAS. Do you know how you got into
>> this situation?
>>
>> Cheers,
>> Andrew
>>
>
> I should also note that there is a possibility that extending the timeout,
> as suggested by John, may resolve the issue. It could be that cloud-init is
> still running, and the nonce.txt file just hasn't been written *yet*.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20140514/c6f1ffc8/attachment.html>