Server is maintaining its database at the moment. It may take from several minutes to several hours depending on the size of the database.

It's going on 6 hours of this database maintenance now. I need to get this operational. Any help from JB is appreciated.

You can change time of the cleanup at the "Configure clean-up policy" page in the Administration area. Note that you may experience long cleanup after the upgrade to 4.0.2 build if there were deleted build configurations.

Please attach your server logs.

All of the logs?

No, just teamcity-server.log, if you prefer you can send it to teamcity-feedback [at] jetbrains.com

Email has been sent with log.

Hi, I didn't see a resolution to this problem.  I am having the same issue as well.  We decided to turn on some cleanup and we currently can't afford to have it in cleanup mode at this moment.  Ours is going on 6 hours right now and have no idea how much longer it may run.  Is there a way to stop this and then start it back up at a later time?  Will restart the teamcity server have any effect or could this cause problems?  I am running with TeamCity 4.0 build 8080 and I'm using mysql.  This is the tail of my teamcity-server.log.  HELP PLEASE!

[2009-05-29 03:00:23,659]   INFO -  jetbrains.buildServer.CLEANUP - Performing cleanup EVERYTHING for 8342 builds
[2009-05-29 03:00:23,659]   INFO -  jetbrains.buildServer.CLEANUP - Cleaning extensions data...
[2009-05-29 03:01:07,751]   INFO -  jetbrains.buildServer.CLEANUP - Deleting build logs...
[2009-05-29 03:08:04,667]   INFO -  jetbrains.buildServer.CLEANUP - Cleaning build history data from the database...

Thanks,
Jay

Try to restart server. Long cleanup problem should be fixed in TeamCity 4.5, so please upgrade to this version. If it does not help please submit a bug report with debug logs attached (http://www.jetbrains.net/confluence/display/TCD4/Reporting+Issues)

I stopped the TeamCity server and the windows service said problem stopping service after awhile.  Might be because it was running a long query.  Right now it still shows the database running the DELET from test_info...  Do you suggest I restart the mysql database service to kill that process as well then start the mysql database back up then the teamcity server?

I think you can kill this query from the mysql console. It will not hurt the server and no backup will be required after that. The only side effect is some of the records will not be cleaned from the database but since there are no builds referencing these records it does not really matter.

I ended up just killing th the query through the mysql client and started teamcity back up.  Everything looks good now.   Thanks for the help and will be upgrading to 4.5 next week.

Hi,

We upgraded to 4.5 awhile back and turned on some more rigirous cleanup and the maintenance still takes a long time.  We are currently using mysql and the TeamCity 4.5.3 build 9035.