=== kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [02:00] . === kadams54 is now known as kadams54-away [03:04] I feel like an idiot, I can't figure out how to tell Juju to bring up a down unit [03:04] - juju-gui/0: 10.0.3.151 (down) 80/tcp, 443/tcp [03:07] 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] there's no "juju start" or "juju up" [03:24] jumpkick: I think that means the agent is down [03:24] I could be wrong though [03:25] do a 'juju status' of the node [03:25] uh service === kadams54 is now known as kadams54-away [04:00] X-Rob: the agent-state is down, and it doesn't respond to ping [04:01] jumpkick: so, go push the power button, however you do it [04:01] exactly what I don't know how to do [04:01] walk over to the machine and push the button on the front that says 'power' [04:01] It often looks like a circle with a line through the top [04:02] I'm on the host [04:02] I don't want to reboot my workstation because an LXC container didn't autostart [04:02] So it's a virtual machine? [04:02] Right [04:02] you want to know how to start a LXC container [04:03] 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] https://help.ubuntu.com/lts/serverguide/lxc.html [04:03] Something turned it off [04:05] 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] this is probably what shut it off === mhall119_ is now known as mhall119 === mwhudson_ is now known as mwhudson === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob === scuttlemonkey is now known as scuttle|afk === scuttle|afk is now known as scuttlemonkey === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob