Teamcity not starting on localhost:32112 - Error: Could not find or load main class
Good day,
I've recently installed Teamcity 2018.x and having issues accessing teamcity server on http://localhost:32112
The TeamCity server service starts successfully when using services, however stops when accessing
When using - cmd C:\TeamCity\bin>teamcity-server.bat run or C:\TeamCity\bin>teamcity-server.bat start it fails to start and I get the error below.
Please could anyone assist me with areas I could look at to resolve this issue, I'm stuck :(
Catalina.out - from teamcity logs
Looking for installed Java...
Java executable is found: 'C:\TeamCity\jre\bin\java.exe'
Using CATALINA_BASE: "C:\TeamCity\bin\.."
Using CATALINA_HOME: "C:\TeamCity\bin\.."
Using CATALINA_TMPDIR: "C:\TeamCity\bin\..\temp"
Using JRE_HOME: "C:\TeamCity\jre"
Using CLASSPATH: "C:\TeamCity\bin\..\bin\bootstrap.jar;C:\TeamCity\bin\..\bin\tomcat-juli.jar"
Error: Could not find or load main class C:\ProgramData\JetBrains\TeamCity\lib
Looking for installed Java...
Java executable is found: 'C:\TeamCity\jre\bin\java.exe'
Using CATALINA_BASE: "C:\TeamCity\bin\.."
Using CATALINA_HOME: "C:\TeamCity\bin\.."
Using CATALINA_TMPDIR: "C:\TeamCity\bin\..\temp"
Using JRE_HOME: "C:\TeamCity\jre"
Using CLASSPATH: "C:\TeamCity\bin\..\bin\bootstrap.jar;C:\TeamCity\bin\..\bin\tomcat-juli.jar"
Error: Could not find or load main class C:\ProgramData\JetBrains\TeamCity\lib
Looking for installed Java...
Java executable is found: 'C:\TeamCity\jre\bin\java.exe'
Using CATALINA_BASE: "C:\TeamCity\bin\.."
Using CATALINA_HOME: "C:\TeamCity\bin\.."
Using CATALINA_TMPDIR: "C:\TeamCity\bin\..\temp"
Using JRE_HOME: "C:\TeamCity\jre"
Using CLASSPATH: "C:\TeamCity\bin\..\bin\bootstrap.jar;C:\TeamCity\bin\..\bin\tomcat-juli.jar"
Error: Could not find or load main class C:\ProgramData\JetBrains\TeamCity\lib
Many thanks,
Tiyi
Please sign in to leave a comment.
Hi Tiyi,
It looks like the service was configured in a special manner. Could you check for which error happens when the service starts? It seems like there is some misconfiguration on the server. Please make sure that the user running both the service and the command has permissions to write on the folder mentioned.
While we would probably be able to further debug and trace down the issue, in your situation it might be faster to simply reinstall the server.