Olaf Kober Posted June 21, 2011 Report Share Posted June 21, 2011 I Link to comment Share on other sites More sharing options...
miller Posted June 21, 2011 Report Share Posted June 21, 2011 Olaf, hi, this is definitely an interesting topic. We use a communication file created with the "cm shell" when integrating with CI, in your case TeamCity. Also, a tmp file is created in /tmp for that communication. Did you try to kill the cm.exe process? a new one should fire upon the next build. Interesting places, hints: Your nightly backup/maintenance procedure are they for example cleaning the /tmp directory? Also, try activating logs on the cm.exe and review the logs. Full instructions on the following KB: http://www.plasticscm.com/infocenter/technical-articles/kb-enabling-logging-for-plastic-scm-part-i.aspx You are especially interested in the file cm.log.conf that will activate logs for the cm.exe. I hope the above can be of assistance. Miller Link to comment Share on other sites More sharing options...
Olaf Kober Posted July 14, 2011 Author Report Share Posted July 14, 2011 Hi Miller! I'm a little bit late, but let me first thank you for your hints. Those guided me into the right direction. Fortunately, this morning I was able to capture log files of Plastic, TeamCity and file activity when the issue happened again. Please, find those log files attached. Here is what I know: First, the communication file is located in TeamCity's Temp folder (not the system TeamCityPlasticFileActivityLogs.zip Link to comment Share on other sites More sharing options...
miller Posted July 14, 2011 Report Share Posted July 14, 2011 Olaf, thanks for your feedback. We will look into this, and Ill update you when we have something. Miller Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.