Builds go to queue without running after migration from HQSLDB to MySQL?
Follow

I just ran the migration from the HQSLDB to MySQL. It seemed to go fine without any errors. The TC server came back up and all projects, agents, etc. and historical data appear to be present. However, now when I run a build, the build goes to the queue and doesn't run - even when several compatible agents are available.

Any ideas? The builds are still sitting there in the queue without any reason as to why they are in the queue instead of running.

Thanks in advance.

Lee

Votes

0

Share

I started looking at the log files for additional information. The migration seemed to complete successfully even though it had a warning related to two records being truncated due to some special characters during the restore. I then started noticing the following errors in the server log after the builds went into the queue:

java.lang.IllegalStateException: Database might be corrupted. at jetbrains.buildServer.serverSide.impl.BuildIdGenerator.updateId(BuildIdGenerator.java:2) at jetbrains.buildServer.serverSide.impl.BuildIdGenerator.getNextId(BuildIdGenerator.java:10) at jetbrains.buildServer.serverSide.impl.BuildServerImpl.startBuild(BuildServerImpl.java:161) at jetbrains.buildServer.serverSide.impl.BuildServerImpl.access$700(BuildServerImpl.java:281) at jetbrains.buildServer.serverSide.impl.BuildServerImpl$5.run(BuildServerImpl.java:18) at jetbrains.buildServer.serverSide.impl.cleanup.ServerCleanupManagerImpl.executeWithInactiveCleanup(ServerCleanupManagerImpl.java:154) at jetbrains.buildServer.serverSide.impl.cleanup.ServerCleanupManagerImpl$$FastClassByCGLIB$$ba2c8525.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at jetbrains.buildServer.serverSide.impl.auth.TeamCityMethodSecurityInterceptor.invoke(TeamCityMethodSecurityInterceptor.java:22) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.Cglib2AopProxy$FixedChainStaticTargetInterceptor.intercept(Cglib2AopProxy.java:582) at jetbrains.buildServer.serverSide.impl.cleanup.ServerCleanupManagerImpl$$EnhancerByCGLIB$$37353c67.executeWithInactiveCleanup(<generated>) at jetbrains.buildServer.serverSide.impl.BuildServerImpl.flushQueue(BuildServerImpl.java:306) at jetbrains.buildServer.serverSide.impl.BuildServerRunner$2.doSomething(BuildServerRunner.java:1) at jetbrains.buildServer.serverSide.impl.BuildServerRunner$BuildServerWorker.run(BuildServerRunner.java:27) at java.lang.Thread.run(Thread.java:595)

I then deleted the database, fixed the errors complained about in the truncation log, and restored the db again without any warnings or errors. When I brought up the server application and tried to start another build I got the same corruption errors as above again.