Q:

CruiseControl .Net problems after server is restarted

I've got a problem with CruiseControl .Net (version 1.4.3.4023) in that when the server is restarted, a random selection of projects are 'broken' even though the codebase has not changed.
As the servers in our place are restarted every Sunday evening, my job Monday morning is to run through CCTray, starting each project in turn, so that our output display monitor shows a green (fixed) status.
I can replicate the problem, simply by stop/starting the CruiseControl service, as this does exactly the same thing.  Again, a random selection of projects appear as failed.
Any suggestions as to how to fix it?

A:

First, have you checked the CCNet logfile?  That will most likely have your solution.
My guess is that your SCC server may have been inaccessible for a period of time for some reason (scheduled reboots/etc?) and CCNET has "given up" on reaching it for a handful of projects.  We had the same problem, and I believe that it went away when we upgraded to CCNET 1.5.

