The GUI reports: (NODE2-DD27) Allocated to mike == The node is reachable via hostname from the MAAS server: $ ping NODE2-DD27 PING NODE2-DD27 (172.23.1.84) 56(84) bytes of data. 64 bytes from NODE2-DD27 (172.23.1.84): icmp_req=1 ttl=64 time=0.296 ms 64 bytes from NODE2-DD27 (172.23.1.84): icmp_req=2 ttl=64 time=0.464 ms ^C --- NODE2-DD27 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 0.296/0.380/0.464/0.084 ms ==
SSH seems to work fine: $ juju ssh 0 2012-04-26 11:31:46,496 INFO Connecting to environment... 2012-04-26 11:31:47,729 INFO Connected to environment. 2012-04-26 11:31:47,818 INFO Connecting to machine 0 at NODE1-86F0 Welcome to Ubuntu 12.04 LTS (GNU/Linux 3.2.0-23-generic x86_64) * Documentation: https://help.ubuntu.com/ System information as of Thu Apr 26 12:31:47 EDT 2012 System load: 0.0 Processes: 73 Usage of /: 19.3% of 7.47GB Users logged in: 0 Memory usage: 41% IP address for eth0: 172.23.1.161 Swap usage: 0% Graph this data and manage this system at https://landscape.canonical.com/ Last login: Thu Apr 26 12:28:15 2012 from maasserver.local == juju debug-log returns: $ juju debug-log 2012-04-26 17:11:51,030 INFO Connecting to environment... 2012-04-26 17:11:53,850 INFO Connected to environment. 2012-04-26 17:11:53,851 INFO Enabling distributed debug log. 2012-04-26 17:11:53,865 INFO Tailing logs - Ctrl-C to stop. ^Cuser@maasserver:~$ Am I supposed to perform some action during the indefinite pause, or did I not wait long enough? Thanks, Mike On Thu, Apr 26, 2012 at 9:25 AM, Francis J. Lacoste <[email protected]> wrote: > > > On 12-04-26 09:49 AM, Michael Hughes wrote: >> I'm succeeding to the point of deploying mysql and it went fine (no >> errors,) but MAAS refuses to acknowledge my second node (NODE2-DD27) >> is running: >> >> $ juju status >> 2012-04-26 08:40:24,362 INFO Connecting to environment... >> 2012-04-26 08:40:25,672 INFO Connected to environment. >> machines: >> 0: >> agent-state: running >> dns-name: NODE1-86F0 >> instance-id: >> /MAAS/api/1.0/nodes/node-c5500a72-f0dd-11e1-91d8-088e02002735/ >> instance-state: unknown >> 1: >> agent-state: not-started >> dns-name: NODE2-DD27 >> instance-id: >> /MAAS/api/1.0/nodes/node-dee7c086-8edf-1271-bb60-0802f01e0035/ >> instance-state: unknown > > > Hi Michael, > > What does the MAAS UI says. Is NODE2-DD27 marked as Allocated or still > ready? > > If it's 'Allocated', it probably means that Juju has trouble connecting > to nodes using the DNS name. Does NODE2-DD27 resolve on the bootstrap > node. You should be able to ssh in the bootstrap node by using `juju ssh 0` > > Make sure NODE2-DD27 resolves and is reachable from there. > > juju debug-log might also give you a better idea of what is the problem. > > Cheers > > > > -- > Francis J. Lacoste > [email protected] > -- Mailing list: https://launchpad.net/~maas-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~maas-devel More help : https://help.launchpad.net/ListHelp
