TC system log messages build Ids and REST API call

I am observing that if i look into TC_data_dir/system/messages/CH*/* then we have whole bunch of log files with build Ids as the name of the log files. (buildId.msg5, buildId.msg5.i5 files).
When i do a query on these buildIds using REST API then call hangs forever for some of the build Ids. Can anyone let me know the reason for the same? Is this a bug in TC rest APIS? how can this be handled to avoid hang?

Also, is it possible that due to some stale build Ids daily cleanup of TC doesn't go through and it stucks forever?

On a similar note, is there a way to cleanup teamcity system log messages similar to cleaning of artifacts?  As of now, it seems that it needs to be done manually?


Please sign in to leave a comment.