TeamCity not detecting pending changes

Hi all,

I'm using TeamCity   6.5.4 (build 18046) with HSQL internal data storage, and we have VCS roots setup to detect any changes from Subversion.

The issue is that I have committed and pushed my latest changes via Tortoise HG (version 2.0.4), and these have been pushed successfully to BitBucket. However, TeamCity does not seem to have picked up these changes, and I haven't touched any configuration that would affect this.

I have checked my projects VCS Root and there is one VCS attached (see screenshot 1), and checking the VCS settings it all looks okay and testing the connection here is successful (screenshot 2). I've checked the following logs on the server where TeamCity is hosted:

teamcity-server.log has the following messages:

[2014-09-22 07:46:59,893]  ERROR - verSide.impl.BuildServerRunner - java.lang.IllegalStateException: TeamCity data source is not connected.
java.lang.IllegalStateException: TeamCity data source is not connected.
    at jetbrains.buildServer.serverSide.db.TeamCityDataSource.checkConnected(TeamCityDataSource.java:206)
    at jetbrains.buildServer.serverSide.db.TeamCityDataSource.getConnection(TeamCityDataSource.java:212)
    at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:113)
    at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:79)
    at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:331)
    at jetbrains.buildServer.serverSide.db.DBFacade._runSql(DBFacade.java:429)
    at jetbrains.buildServer.serverSide.db.DBFacade.runSql(DBFacade.java:407)
    at jetbrains.buildServer.serverSide.db.queries.GenericQuery.execute(GenericQuery.java:109)
    at jetbrains.buildServer.a.f.k(f.java:16)
    at jetbrains.buildServer.a.m.isMaxNumberOfAuthorizedAgentsExceeded(m.java:9)
    at jetbrains.buildServer.serverSide.impl.BuildServerImpl.flushQueue(BuildServerImpl.java:452)
    at jetbrains.buildServer.serverSide.impl.BuildServerRunner$2.doSomething(BuildServerRunner.java)
    at jetbrains.buildServer.serverSide.impl.BuildServerRunner$BuildServerWorker.run(BuildServerRunner.java:10)
    at java.lang.Thread.run(Unknown Source)


teamcity-vcs.log:

[2014-09-11 11:24:08,183]   WARN [tor 757 {id=49}] -      jetbrains.buildServer.VCS - Error while loading changes for root mercurial: https://bitbucket.org/frontier/voiceflex {instance id=49, parent id=7}, cause: '"C:\Program Files\TortoiseHg\hg.exe" pull https://frontier:******@bitbucket.org/frontier/voiceflex' command failed.
stdout: pulling from https://frontier:***@bitbucket.org/frontier/voiceflex

stderr: abort: error: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full


I didn't install and administer TeamCity so I'm not sure where else to check for issues, so I'm hoping what I've provided so far will help get an answer of what's going on.

I really appreciate if anyone has had any experience with this issue to assist in solving this issue.

Kind regards,
Deepal



Attachment(s):
teamcity-vcs log.txt.zip
teamcity-server log.txt.zip
2 VCS Root configuration.PNG
1 Project VCS Root.PNG
3 comments
Comment actions Permalink

Hi,

This error “An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full” means that you run out of resources or memory. For example see this link.

TeamCity 6.5.4 is outdate version which we do not support. Please upgrade TeamCity server to the latest version.

The HSQL database is not stable, so I would recommend you to migrate to one of supported external database (PostgreSQL, MySQL, Oracle, MS SQL). The details how to migrate are here:

http://confluence.jetbrains.com/display/TCD8/Migrating+to+an+External+Database

How to restore from backup is described here:
http://confluence.jetbrains.com/display/TCD8/Restoring+TeamCity+Data+from+Backup

0
Comment actions Permalink

Hi Alina,

Thanks for your response.

I looked at the link you provided, but I believe this fix only applies to older versions of Windows Server. I followed the instructions in this link, as this has instructions for potentially fixing the socket issue for Windows Server 2008 R2. I've applied the changes to the registries, restarted the server but TeamCity still doesn't detect any new changes. I even committed a new change and pushed to bitbucket, but nothing was detected.

I've attached the complete logs from the server, and if you check the teamcity-vcs log, you'll see that the file hasn't been updated since 22/09/2014, whereas the others have more recent logs. I'm not sure if it is the HSQL database issue, as I applied an older version of the buildserver data files, and it shows the same VCS settings as present.

Is there any other way to trigger a VCS change? Is there any other way to make TeamCity recognise the changes from bitbucket?

Your help is much appreciated.

Kind regards,
Deepal



Attachment(s):
teamcity-vcs.log.zip
teamcity-notifications.log.zip
teamcity-activities.log.zip
teamcity-server.log.zip
0
Comment actions Permalink

Hi Alina,

So I managed to solve this issue finally. Looking through the available VCS Roots in TeamCIty, there was one setup for BitBucket but not used in any project. So I added this VCS root to the 'Default - Build' configuration and after a restart of the Build Agent service, it started picking up the changes successfully.

I'll look into upgrading TeamCity and migrating the database in the scenario that the instability of the internal data storage was the issue here.

Kind regards,
Deepal

0

Please sign in to leave a comment.