Getting TeamCity database is empty or doesn't exist after a low-diskspace situation

Our Linux server running TeamCity ran low on diskspace a few nights ago and stopped working.  We removed some of the old system logs to free up space and restarted the server.

When we try to login to the server, we are prompted for a key to go into maintenance.  Once there, there is a message on the screen that "TeamCity database is empty or doesn't exist.  If you proceed, a new empty database will be created."

It also shows:

Installed TeamCity Software

Version: 6.5.1 (build 17834)
Required data format version: 454

Data directory

Path: /opt/apache-tomcat-6.0.32/temp/.BuildServer
Data format version: 454


Database: default (using internal datbase)
Data format version: empty

The server.log file shows the following:

[2012-10-29 10:56:59,208]   INFO -   jetbrains.buildServer.SERVER - Starting TeamCity server
[2012-10-29 10:56:59,252]   INFO -   jetbrains.buildServer.SERVER - TeamCity version: 6.5.1 (build 17834), data format version 454
[2012-10-29 10:56:59,263]   INFO -   jetbrains.buildServer.SERVER - TeamCity data directory: /opt/apache-tomcat-6.0.32/temp/.BuildServer
[2012-10-29 10:56:59,707]   INFO -   jetbrains.buildServer.SERVER - Data directory format version: 454
[2012-10-29 10:56:59,707]   INFO -   jetbrains.buildServer.SERVER - Database format version: neither internal database nor '' file found
[2012-10-29 10:56:59,709]   INFO -   jetbrains.buildServer.SERVER - Administrator login is required from web UI using authentication token: 6312217494704899843

Can someone help me identify if the database is truly gone or if there is something preventing the system from seeing it properly?

1 comment
Comment actions Permalink

Resolved the problem.  Someone had accidentally deleted the database from the server.

I restored a copy from backup and everything is operational again.


Please sign in to leave a comment.