[02:00] <jumpkick> .
[03:04] <jumpkick> I feel like an idiot, I can't figure out how to tell Juju to bring up a down unit
[03:04] <jumpkick> - juju-gui/0: 10.0.3.151 (down) 80/tcp, 443/tcp
[03:07] <jumpkick> Can anyone hit me with a clue?  I'm searching the docs and "juju run" isn't it thats for running stuff on the units
[03:07] <jumpkick> there's no "juju start" or "juju up"
[03:24] <X-Rob> jumpkick: I think that means the agent is down
[03:24] <X-Rob> I could be wrong though
[03:25] <X-Rob> do a 'juju status' of the node
[03:25] <X-Rob> uh service
[04:00] <jumpkick> X-Rob: the agent-state is down, and it doesn't respond to ping
[04:01] <X-Rob> jumpkick: so, go push the power button, however you do it
[04:01] <jumpkick> exactly what I don't know how to do
[04:01] <X-Rob> walk over to the machine and push the button on the front that says 'power'
[04:01] <X-Rob> It often looks like a circle with a line through the top
[04:02] <jumpkick> I'm on the host
[04:02] <jumpkick> I don't want to reboot my workstation because an LXC container didn't autostart
[04:02] <X-Rob> So it's a virtual machine?
[04:02] <X-Rob> Right
[04:02] <X-Rob> you want to know how to start a LXC container
[04:03] <jumpkick> I figured juju would have a way to manage the start up of the container, since juju created it and juju was supposed to see that it was started
[04:03] <X-Rob> https://help.ubuntu.com/lts/serverguide/lxc.html
[04:03] <X-Rob> Something turned it off
[04:05] <jumpkick> machine-0: 2014-12-21 03:59:41 WARNING juju.worker.instanceupdater updater.go:247 cannot get instance info for instance "user-local-machine-1": no instances found
[04:05] <jumpkick> this is probably what shut it off