No database selected on TeamCity start
I've been tasked with testing the upgrade from TeamCity 10.0.2 to the latest. I have cloned our TeamCity server to a new instance, both running Ubuntu in AWS. The external database on the production TC server is MySQL, and it is an RDS instance running in AWS as well. I cloned the RDS instance, gave it a new name, and changed its endpoint URL in the database.properties file. I changed all of the URLs in the TeamCity tree to the new URL. I've gotten the server to the point that it is trying to connect to the database, but I am receiving the below error message. From the command line of the new staging server, I am able to connect to the mysql database with the user specified in the properties file. I can "use" the teamcity database from the command line just fine. However, when automatically connecting, it doesn't seem to connect to the database. Am I missing something?
TeamCity has failed to start
TeamCity server startup error
Unexpected exception SQLException: SQL error when doing: Executing a SQL statement
SQL query: create temporary table if not exists agent_pool$ ( agent_pool_id int not null )
SQL exception: No database selected
Current Startup State
Startup status
Current step: TeamCity server startup error
Next step: not defined yet
Data Directory
Directory path: /srv/.BuildServer exists
Database properties file exists
Internal database file: not found
Database
Database type: MYSQL
Database connection URL: jdbc:mysql://[URL]
JDBC driver version: 5.1 (MySQL Connector Java)
Database system version: 5.6.29 (MySQL)
Versions
Software version: 787
Data directory version: 787
Database version: unknown
Logs
Logs path: /srv/TeamCity-10.0.2/logs
Please sign in to leave a comment.