I am running TeamCity 5.0.1 Enterprise (build 10715). After a few days of uptime, TeamCity seems to stop collecting changes. When this happens, even forcing the server to check for pending changes does not find anything. If you start a build manually, the pending changes do get collected and show up in the UI.
Also, when the server is in this state, VCS triggers do not work obviously, but even time-based triggers do not work, so I think the two may be related.
The last occurrence of this was yesterday, Jan 13 at 17:19. When I look through the teamcity-vcs.log file, I can see that there are constantly log entries for VCS change collections, until that time. Then it only seems to collect changes when a build is run. When I watch the log file and force collecting changes through the UI, nothing shows up in the log. After bouncing the server, everything goes back to normal.
If there is any more data I can collect that might be useful, please let me know, otherwise any help with this issue would be great. I've looked through all the other server logs around the time the collection stopped and did not see anything out of the ordinary, but if you'd like to see the logs I have saved them off.
I have attached the teamcity-vcs.log from this time, with the repository urls and project names removed. Our VCS changes check interval is set to 300 seconds and we use subversion for our VCS.