Teamcity not loading changes from GitHUb and log filling up with errors

Completed

Hi hope someone can help us,

Our teamcity service is suddenly no longer loading changes from GItHub, the teamcity-service log is filled with these errors and growing constantly

Found critical error in configuration: Error while loading VCS history from DB, builds can start on outdated revisions, see teamcity-vcs.log for details.

 

inspecting the teamcity-vcs.log is filled with these error messages

jetbrains.buildServer.VCS - Error while loading VCS changes
java.lang.ArrayIndexOutOfBoundsException: 1
at jetbrains.buildServer.vcs.impl.ArrayBasedLongIndex.optimizeForReadPerformance(ArrayBasedLongIndex.java:82)
at jetbrains.buildServer.vcs.impl.VcsModificationsStorageImpl.lambda$ensureVcsHistoryLoaded$1(VcsModificationsStorageImpl.java:356)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.vcs.impl.VcsModificationsStorageImpl.ensureVcsHistoryLoaded(VcsModificationsStorageImpl.java:228)
at jetbrains.buildServer.vcs.impl.VcsModificationsStorageImpl.getModificationsWithSameVersion(VcsModificationsStorageImpl.java:567)
at jetbrains.buildServer.vcs.impl.VcsModificationsStorageImpl.getModificationsWithSameVersion(VcsModificationsStorageImpl.java:322)
at jetbrains.buildServer.vcs.impl.DBVcsModificationHistory.findModificationByVersion(DBVcsModificationHistory.java:298)
at jetbrains.buildServer.vcs.impl.DBVcsModificationHistory.findModificationIdByVersion(DBVcsModificationHistory.java:45)
at jetbrains.buildServer.serverSide.impl.changeProviders.DagBasedChangesProvider.getModificationId(DagBasedChangesProvider.java:47)
at jetbrains.buildServer.serverSide.impl.changeProviders.DagBasedChangesProvider.getRootUpperBoundModId(DagBasedChangesProvider.java:35)
at jetbrains.buildServer.serverSide.impl.changeProviders.DagBasedChangesProvider.getChanges(DagBasedChangesProvider.java:34)
at jetbrains.buildServer.serverSide.impl.changeProviders.CompositeChangesProvider.getChanges(CompositeChangesProvider.java:7)
at jetbrains.buildServer.serverSide.impl.BuildVcsChangesCalculatorImpl.calculate(BuildVcsChangesCalculatorImpl.java:1)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion.lambda$calculateVcsChanges$3(AbstractBuildPromotion.java:409)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion.calculateVcsChanges(AbstractBuildPromotion.java:161)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion.calculateChangesOnce(AbstractBuildPromotion.java:251)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion.getOwnChanges(AbstractBuildPromotion.java:375)
at jetbrains.buildServer.serverSide.impl.DummyBuildPromotion.getOwnChanges(DummyBuildPromotion.java:81)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion$VcsChangesProvider.addDetectedChanges(AbstractBuildPromotion.java:19)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion.fillDetectedChanges(AbstractBuildPromotion.java:223)
at jetbrains.buildServer.serverSide.impl.AbstractBuildPromotion.getDetectedChanges(AbstractBuildPromotion.java:11)
at jetbrains.buildServer.serverSide.impl.BuildTypeBranchImpl.getDetectedChanges(BuildTypeBranchImpl.java:75)
at jetbrains.buildServer.buildTriggers.vcs.BranchChangesCalculator.getChanges(BranchChangesCalculator.java:22)
at jetbrains.buildServer.buildTriggers.vcs.SingleBranchVcsTrigger.triggerBuild(SingleBranchVcsTrigger.java:114)
at jetbrains.buildServer.buildTriggers.vcs.AllBranchesVcsTrigger.lambda$triggerBuild$0(AllBranchesVcsTrigger.java:61)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.buildTriggers.vcs.AllBranchesVcsTrigger.triggerBuild(AllBranchesVcsTrigger.java:3)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.lambda$callTrigger$6(BuildTriggersChecker.java:50)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.callTrigger(BuildTriggersChecker.java:289)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.access$1400(BuildTriggersChecker.java:14)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker$BuildTriggersGroup.processTriggers(BuildTriggersChecker.java:49)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.lambda$null$1(BuildTriggersChecker.java:286)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:76)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.lambda$triggerBuilds$2(BuildTriggersChecker.java:186)
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1640)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

 

I've tried updating to the latest server version but the error still continues - any ideas?

 

1 comment
Comment actions Permalink

Hi Gareth,

 

may I ask which java version are you using to run the server? I haven't found any instance of this issue in recent times, most of them were pretty old and related to using an unsupported java version at that time.

 

You could try clearing the VCS Cache, you can check it under Administration - Caches. If it only happens with one specific VCS Root, you can access the directory for it directly under the data directory/system/caches/git, check the map file and remove that cache. The next run should take a bit more time while the cache is rebuilt

 

I haven't found any other instance of this specific issue reported so far, so it seems like there is a very specific condition to your setup that triggers the issue. We would need to dig deeper into the issue and the teamcity-vcs.log file for that. Please forward those to us using the "Submit a request" button on top of this page.

0

Please sign in to leave a comment.