On 03/14/2013 08:17 AM, Marius B. Kotsbak wrote:
> Yes, I encountered it again, using juju-gui-source: trunk. and
> "cs:precise/juju-gui". Maybe this was a slightly different problem, but
> still at loading the main page and failing to connect to the API. I also
> saw this in the log:
>
> "Starting or restarting Juju API agent." and "Failed to perform start
> on service juju-api-agent"
This is new to me. I'll pass it along to a pyjuju dev in case anyone
else has seen it. A pastebin of a longer bit of log output might be
helpful.
> I changed back to "stable" and deployed again, and then it worked fine.
> What other combo is recommended for a newer version?
ATM, for what I believe to be the specific issue you are encountering:
That's bleeding edge. Using the GUI release (the charm default
behavior) means it has been better tested. Moreover, on the charm
trunk, using a GUI release is also about eight minutes faster to deploy
on ec2 than a branch. Once we make a release with this fix (version
number > 0.2.2) we suggest you go back to using releases.
On 03/14/2013 08:17 AM, Marius B. Kotsbak wrote: juju-gui" . Maybe this was a slightly different problem, but
> Yes, I encountered it again, using juju-gui-source: trunk. and
> "cs:precise/
> still at loading the main page and failing to connect to the API. I also
> saw this in the log:
>
> "Starting or restarting Juju API agent." and "Failed to perform start
> on service juju-api-agent"
This is new to me. I'll pass it along to a pyjuju dev in case anyone
else has seen it. A pastebin of a longer bit of log output might be
helpful.
> I changed back to "stable" and deployed again, and then it worked fine.
> What other combo is recommended for a newer version?
ATM, for what I believe to be the specific issue you are encountering:
charm: cs:~juju- gui/precise/ juju-gui
juju-gui-source: lp:juju-gui
That's bleeding edge. Using the GUI release (the charm default
behavior) means it has been better tested. Moreover, on the charm
trunk, using a GUI release is also about eight minutes faster to deploy
on ec2 than a branch. Once we make a release with this fix (version
number > 0.2.2) we suggest you go back to using releases.
Gary