Teamcity is broken after a restart with multiple critical errors in configuration files - help!!
Hi folks,
I'm running Teamcity on Debian and have been for years quite reliably. Today I restarted it to load a new plugin and it is suddenly extremely unhappy - it doesn't load most of the Projects and the UI is in a very confused state.
In the logs and UI I see a lot of errors like:
We recently moved some Project into sub-Projects, could this have caused the problem?
As an example of the problem, when I click on the Projects drop-down I see the error:
Stack Trace: java.lang.IllegalStateException: Projects model is not loaded yet
....
Any ideas? This is a critical server for us as it handles all our builds and deployments, so I'm really unhappy that it has suddenly broken after a restart :(
Many thanks,
Mark Baker
I'm running Teamcity on Debian and have been for years quite reliably. Today I restarted it to load a new plugin and it is suddenly extremely unhappy - it doesn't load most of the Projects and the UI is in a very confused state.
In the logs and UI I see a lot of errors like:
Critical error in configuration file /data/teamcity/.BuildServer/config/projects/Project25Internationalisation/buildTypes/bt1156.xml:
Build configuration template with external id "btTemplate55" does not exist
Build configuration template with external id "btTemplate55" does not exist
We recently moved some Project into sub-Projects, could this have caused the problem?
As an example of the problem, when I click on the Projects drop-down I see the error:
Unexpected Error
This was not supposed to happen. Please provide the error details to your TeamCity server maintainer.
If you maintain this TeamCity installation please report this error to JetBrains.
Error message: Projects model is not loaded yet
TeamCity: 8.0.1 (build 27435)
Operating system: Linux (2.6.32-5-amd64, amd64)
Java: 1.6.0_26-b03 (Sun Microsystems Inc.)
Servlet container: Apache Tomcat/7.0.37
This was not supposed to happen. Please provide the error details to your TeamCity server maintainer.
If you maintain this TeamCity installation please report this error to JetBrains.
Error message: Projects model is not loaded yet
TeamCity: 8.0.1 (build 27435)
Operating system: Linux (2.6.32-5-amd64, amd64)
Java: 1.6.0_26-b03 (Sun Microsystems Inc.)
Servlet container: Apache Tomcat/7.0.37
Stack Trace: java.lang.IllegalStateException: Projects model is not loaded yet
....
Any ideas? This is a critical server for us as it handles all our builds and deployments, so I'm really unhappy that it has suddenly broken after a restart :(
Many thanks,
Mark Baker
Please sign in to leave a comment.
Poking around the files, it looks like all the build templates are still present, but Teamcity is not finding them for some reason...
e.g. in .BuildServer/config/projects/
we have _Root/buildTypes/ and that's got btTemplate50.xml (and many others)
But I have error messages like this:
[2014-01-07 18:15:46,544] WARN - jetbrains.buildServer.SERVER - <strong>Critical error in configuration file /data/teamcity/.BuildServer/config/projects/Tools_OkrTool/buildTypes/Tools_OkrTool_DeployToLive.xml:</strong><br />
Build configuration template with external id "btTemplate50" does not exist
(incidentally - this is not a WARN level error, it's an ERROR surely!)
When I look inside the project xml file I see this:
<build-type>
<name>Deploy to Live</name>
<description />
<settings ref="btTemplate50">
Which seems correct to me -- so I'm really stumped as to why it isn't finding the templates.
Pavel from JetBrains support fixed this - the issue was actually the first error in the server log:
[2014-01-07 18:15:36,814] WARN - jetbrains.buildServer.SERVER - <strong>Critical error in configuration file /data/teamcity/.BuildServer/config/projects/_Root/vcsRoots/Root_DevopsScalaDeploys1.xml:</strong><br />
VCS root with name "devops/scala-deploys optional-branch" already exists in project "<Root project>"
Somehow we ended up with two VCS roots with the same name, so I renamed one and it all works again.
PHEW!!!