Unfortunately automatic updates was enabled and rebooted our teamcity server last night. Now, whenever we try to access the server via browser we get "TeamCity Maintenance: Connecting to the database". I looked at the teamcity logs and sure enough that's the last thing that's logged. We haven't had the time to migrate to an external database so it's still using the internal HSQL DB. Attached is a portion of our logs starting from just before the windows updates last night. The reboot was initiated at 3:08:48 AM. At 3AM our box executes cleanup but that was done 7 minutes before the restart was triggered. After looking through the teamcity log and Windows Event Viewer it doesn't look like windows signaled the TeamCity Server service to shutdown but it DID signal the build agent service, running on the same box, to shutdown.
Other possibly helpful information:
TeamCity 8.0.1 (build 27435)
Windows Server 2008 R2
I need this up and running ASAP and have not run into issues like this before.
Let me know what other information or logs could be useful.
I'd also like to add that the buildserver.log file in E:\ProgramData\JetBrains\TeamCity\system has not been modified since right before the reboot last night @ 3:08AM while buildserver.backup and buildserver.data have.
I rebooted the server twice but the TeamCity service still cannot connect to the database. The java process for the service appears to have one thread using 15% CPU (100% for 1 of 8 Cores).
This is the only update that was installed last night http://support.microsoft.com/kb/2858725/en-us