This is a juju issue, not a charm issue; I suspect something bad
happened an caused the juju agent of go wild.
Are you still seeing this issue?
** Changed in: juju (Ubuntu)
Assignee: James Page (james-page) = (unassigned)
--
You received this bug notification because you are a member of
Sure, the cluster is still up at canonistack if you want to poke at
them:
I've used two charms: jenkins x1 and jenkins-slave x2, vanilla on
precise.
My envirionments.yaml looks like this:
environments:
canonistack:
type: ec2
ec2-uri: http://91.189.93.65:8773/services/Cloud
s3-uri:
I'm rapidly running out of time this year so may not be able to. (Might
ask for someone on #juju.)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1078242
Title:
juju cannot connect
Assigning James Page as he is the maintainer of the jenkins charms.
** Changed in: juju (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
Could you please post the charms you were using, your sanitized
environments.yaml, and the set of juju commands you used, to help us
reproduce and debug the issue you had?
** Changed in: juju (Ubuntu)
Importance: Undecided = Medium
** Changed in: juju (Ubuntu)
Status: New = Incomplete
Zookeeper includes a default limit per client of 10 connections; this is
to ensure that a single rogue client can't kill a zookeeper cluster.
This points to something else bad happening in your environment.
If more than ten connections per client are required for juju, then
maxClientCnxns can be
