continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mykel Alvis" <>
Subject Re: All builds failing suddenly
Date Mon, 30 Apr 2007 14:42:09 GMT
Interestingly, this same thing has been happening to me very regularly under
Linux (FC6 virtual instances).  It seems to be that at some point in the
night, the web server stopped responding and once that happened, the build
would never try again.  I suppose continuum assumed that there was "no
change" after the error.

My solution, poor as it is, is to use cron to shut down continuum on the
continuum server, restart apache on the subversion server, and then start
continuum a few minutes later.  I've no longer had the problem with
continuum failing to update.

On the other hand, the icons on the left of the projects are generally stop
signs ("error") when run from the schedules, even though the last build in
the build history was listed as "successful".

On 4/26/07, David Roussel <> wrote:
> Maybe there is more information in the SVN/apache logs?
> On Thu, 26 Apr 2007 12:06:17 -0400, "Doug Tanner"
> <> said:
> > Yes.  I had to restart all of the continuum services, some of them
> > several times before the problem was resolved.  Nothing had changed on
> > the machine since the beginning of this month.  So it just seems strange
> > that all 6 continuum services would have the same problem at the same
> > time this morning.  They are all still running as Local System so if
> > anyone has a definitive reason for changing the services' logon please
> > inform me.
> >
> > Thanks,
> >
> > Doug Tanner
> >
> >

I'm just an unfrozen caveman software developer.  I don't understand your
strange, "modern" ways.

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