Juju instances in aganet-state: down after turning them off (and back on) on EC2
- by Tyler McAdams
I turned my Juju instances off on EC2 for a while and after bringing them back online they seem to be in an odd state:
[code]
claude-vm@claude-vm-fusion:~/Documents/Shell Scripts$ juju status
2012-11-17 17:06:44,094 INFO Connecting to environment...
2012-11-17 17:06:45,590 INFO Connected to environment.
machines:
0:
agent-state: not-started
dns-name: ec2-54-242-142-196.compute-1.amazonaws.com
instance-id: i-b0996fcf
instance-state: running
1:
agent-state: down
dns-name: ec2-50-19-186-245.compute-1.amazonaws.com
instance-id: i-8c8375f3
instance-state: running
2:
agent-state: down
dns-name: ec2-54-242-255-238.compute-1.amazonaws.com
instance-id: i-56807629
instance-state: running
services:
wordpress:
charm: cs:precise/wordpress-9
exposed: true
relations:
db:
- wordpress-db
loadbalancer:
- wordpress
units:
wordpress/0:
agent-state: down
machine: 2
open-ports:
- 80/tcp
public-address: ec2-54-242-227-57.compute-1.amazonaws.com
wordpress-db:
charm: cs:precise/mysql-10
relations:
db:
- wordpress
units:
wordpress-db/0:
agent-state: down
machine: 1
public-address: ec2-54-242-212-177.compute-1.amazonaws.com
2012-11-17 17:06:47,274 INFO 'status' command finished successfully
[/code]
Can I not take my instances down for a while? Or is this something else?
