continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marica Tan <>
Subject Re: What should happen when a distributed agent dies?
Date Tue, 29 Sep 2009 23:37:13 GMT
On Wed, Sep 30, 2009 at 5:19 AM, Wendy Smoak <> wrote:

> On Mon, Sep 28, 2009 at 10:03 AM, Wendy Smoak <> wrote:
> > I'm all for having the system automatically disable any agent that is
> > not behaving properly.  At first, the admin may have to manually
> > re-enable it.  In the future we might come up with a way for it to
> > auto-recover.
> Unfortunately, disabling the agent doesn't seem to help.  The second
> time I tried this, I _was_ able to edit the agent to disable it, but
> the Queues page was still broken.  Same after I deleted the offending
> agent, Continuum still tried to contact it.
> In possibly related news, I notice that even though the agent no
> longer shows on the 'Build Agents' page, it is still in the
> continuum.xml config file, at least until you re-start.
> Interestingly, if you add a new agent that does not respond, it will
> get added as disabled, and this does _not_ break the Queues page.
> Where is the "real" data about what agents there are and which ones
> are enabled?
> Anecdotally, it seems like it's working from continuum.xml and not
> what I see in the web UI.
> Wendy

Continuum reads the continuum.xml for the build agents. The way it should
work is when you update or remove a build agent, it should be reflected
immediately in the continuum.xml. So all "real" data about the agents should
be in the continuum.xml. Apparently, this is not the case and should be
filed as a bug.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message