Hi Shaun Even during startup, CC.Net should be logging to the ccnet.log file. By default you can find this in C:\Program Files\CruiseControl.Net\server. That should give you more information about why it failed to restart.
Like Ruben said, CC.Net will automatically detect configuration changes and reload ccnet.config. At least by default, you can turn this off by modifying ccnet.exe.config or ccservice.exe.config. I should point out that before reloading the config it will allow any builds in progress to complete. If you have a long-running build going it could be a while before you see your changes take effect. Also, when shutting down it will give builds time to complete as well. This could be why the service does not stop and start cleanly as well. Cheers, Dave On Wed, Jan 14, 2009 at 11:14 PM, CinnamonDonkey <[email protected]> wrote: > > Rebooting the server is NOT fixing a bad config file because the > config file is not bad ;-) > > It is fixing the CC.Net Service which fails to restart once stopped > for some unknown reason. > > Cheers, > Shaun > > > On 14 Jan, 11:29, Ruben Willems <[email protected]> wrote: >> Hi >> >> CCNet detects chaning of ccnet.config, so there is no real need of stopiing >> the service / console program >> for making changes. >> >> I find it weird that rebooting a server will fix a bad config file. >> never saw that happening before. >> >> with kind regards >> Ruben Willems >> >> On Wed, Jan 14, 2009 at 12:02 PM, CinnamonDonkey < >> >> [email protected]> wrote: >> >> > Hi All, >> >> > I was wondering... does the CC.Net service detect when the >> > ccnet.config (or any other config file changes) and automatically >> > reload it? >> >> > Currently I go through the process of: >> >> > stop CC.Net Service >> > change ccnet.config >> > save ccnet.config >> > start CC.Net Service (at which point it generally fails and I reboot >> > which fixes it!) >> >> > Cheers, >> > Shaun
