Hi is there not another problem with the server, low harddisk space or so? I've never seen CCNet behave like this.
Keep in mind that CCnet spawns processes, like perforce, if this one is locking up, also ccnet will lock up. (the project being build that is) what do you mean : you cannot kill ccnet remotely? pskill from pstools can kill processes on remote computers. pslist can show a list of the running processes (also from a remote computer) so when this happens again, try the tools from pstools to determine what is going on. with kind regards Ruben Willems On 30 August 2011 00:40, [email protected] <[email protected]>wrote: > I have Cruise Control.Net setup on a Windows Server 2003 R2 box using > CCNet version 1.6 connecting to perforce. For some reason that I'm > unable to figure out yet, the server will lock up intermittently in > such a way that CCNet freezes (cctray) and I cannot RDP or even log > into the console of the server. I can still access various things on > the server using the file system and using mmc I can see some things > like services. I am unable to kill CCNet remotely. This problem > requires a physical hard reboot of the server. > > I have tried a few various things including switching servers to > ensure it wasn't something to do with hardware. I have to run the > service as a user and was using a domain account and switched to a > user on the server itself but this did not help. > > Any help would be appreciated. I have used CCNet before in the past > very successfully our company really likes CCNet as a product when > this doesn't happen; lately, however, the frequency of this issue > seems to have risen. > > The server has no errors in any of the logs (Windows or CCNet) that > would indicate anything odd. The CPU and memory on the server indicate > nothing abnormal before the lock ups occur. > > Again, any help would be appreciated. > Brian Baker > Virtual Radiologic
