I was not referring to the build log but to the logs created by the ccnet service/console, which is probable located in (c:\program files\) CruiseControl.NET\server\ccnet.log This log contains the ccnet log messages while the build log contains information from running the build scripts. As long as you talk about a crash I suspect that this is a ccnet service failing. Beside this log files you might also be able to see some information in windows event log in case the crash was so severe that it was only detected by the operating system.
Hope this might help in the future. florin On Oct 27, 12:27 pm, Petal Wang <[email protected]> wrote: > The log doesn't give much useful information. It only shows: > <build date="2009-10-23 01:00:00" buildtime="00:08:03" error="true" > buildcondition="ForceBuild"> > > So I thought there should be another crash dump file located somewhere... > > Anyway, the problem has been solved by reducing the in-memory log > information... > > Thanks for your help. > > Regards, > Petal > > On Tue, Oct 27, 2009 at 5:34 PM, florin <[email protected]> wrote: > > > You are not helping.... Where do you see that error? > > > Normally you have a file 'ccnet.log' under <ccnet foder>\server. Look > > on that file and try find any error messages (do NOT post the whole > > file here..) > > How do you run ccnet? fom command line or as a service ? > > > florin > > > On Oct 27, 10:37 am, Petal Wang <[email protected]> wrote: > > > Hi Florin, > > > > Sorry I don't know where I can find the crash dump file. Any information > > > about it? The crash shows general information like "CC.Net Console Runner > > > has encountered a problem and needs to close. ..." > > > > I suspected the crash is due to that it runs out of memory since the > > build > > > log informaitonis too large (around 70M). I have workarounded by > > suppressing > > > some log information and so far it works fine. > > > > But may know what's the limitation size for the build log? > > > > Thanks, > > > Petal > > > > On Mon, Oct 26, 2009 at 4:56 PM, florin <[email protected]> wrote: > > > > > Can you also define this 'crash'? It is like going to the doctor, it > > > > is not enough to tell that it hurts, you also have to way what & when. > > > > > Do not expect help unless you provide minimum information on this and > > > > the CPU speed does not qualify as useful information. > > > > > florin > > > > > On Oct 23, 4:24 am, Petal <[email protected]> wrote: > > > > > Hi, > > > > > > We have two machines runing the same task which requires to delete > > and > > > > > pull a lot of files from perforce (this means CCNet needs to collect > > a > > > > > lot of log information at runtime, and usually the size of the > > > > > buildlog is around 70M). The problem is that one machine is quite > > > > > stable but the other often got crash. I compared the hardware > > > > > configuration between the two machines: > > > > > > stable machine: > > > > > Intel(R) COre(TM)2 Quad CPU > > > > > Q9550 @ 2.83GHz > > > > > 2.83GHz, 3.25GB of RAM > > > > > > unstable machine: > > > > > Intel(R) Xeon(R) CPU > > > > > W3520 @ 2.67GHz > > > > > 2.67GHz, 3.00GB of RAM > > > > > > I am not sure whether the issue comes this. But it is the only > > > > > difference I can found between the two machines since the error > > report > > > > > doesn't give me more meaningful information. > > > > > > Anybody else encountered the same problem before? > > > > > > Any suggestion is greatly appreciated. > > > > > > Thanks, > > > > > petal
