Clean-Up Critical Error

Hi,
after my last  teamcity update do higher version ( from 10.0.4 to 2017.1.1) in clean-up setting appears a critical error, which inform me that i have errors in configuration files. In teamcity documentation i have read about common problems. The only solution is to edit files which is noted in log files, but my log files said only that teamcity cant run automatin cleanup . I looked into configuration files and everything look as same as in the previous version. I'm thinking about reset caches but in diagostic menu tc inform me that: This is mostly internal stuff. Please do not touch it unless you are advised to do so by a TeamCity team member. so i dont want to spoil TC more. 
Clean-Up Error: Clean-up cannot be started (there could be critical errors in the configuration files)
Any ideas to fix this problem?

1
7 comments

Most likely cache reset won't help. Please attach logs containing the critical errors.

0
Avatar
Permanently deleted user

The issue started on 10.00 am 28/04/2017. 

[2017-04-28 15:58:29,924] INFO - jetbrains.buildServer.CLEANUP - Cleanup time has been set to 22:00:00 daily
[2017-04-28 15:58:29,925] INFO - jetbrains.buildServer.CLEANUP - Cleanup is enabled
[2017-04-28 22:00:00,031] WARN - jetbrains.buildServer.CLEANUP - There are critical errors detected in the configuration files, cleanup process will not work until these errors are fixed.
[2017-04-29 02:00:00,080] INFO - jetbrains.buildServer.CLEANUP - Git cleanup started
[2017-04-29 02:00:00,399] INFO - jetbrains.buildServer.CLEANUP - Git cleanup finished

0

There must be entries in teamcity-server.log explaining what the errors are and you should also see them in admin UI. What are these critical errors?

0
Avatar
Permanently deleted user

In which admin UI menu option i can see this error? In clean-up i have only this:
team-city server.log errors:

[2017-05-16 18:28:42,436] WARN - dServer.updates.VersionChecker - Unable to check for TeamCity version updates via URL "https://www.jetbrains.com/teamcity/update.xml": java.net.ConnectException: Connection timed out: connect (enable debug to see stacktrace)
[2017-05-16 20:30:06,548] WARN - dServer.updates.VersionChecker - Unable to check for TeamCity version updates via URL "https://www.jetbrains.com/teamcity/update.xml": java.net.ConnectException: Connection timed out: connect (enable debug to see stacktrace)
[2017-05-16 22:00:00,078] WARN - jetbrains.buildServer.CLEANUP - There are critical errors detected in the configuration files, cleanup process will not work until these errors are fixed.
[2017-05-16 22:31:30,681] WARN - dServer.updates.VersionChecker - Unable to check for TeamCity version updates via URL "https://www.jetbrains.com/teamcity/update.xml": java.net.ConnectException: Connection timed out: connect (enable debug to see stacktrace)
[2017-05-17 00:00:15,264] INFO - ity.BuildQueuePriorityOrdering - New item Queued build {Build promotion {promotion id=106997, configuration={id=Framework_DevOps_BcDevopsDashboard_CreateDocumentation, internal id=bt611}}, item id=106997} with weight 0.00 inserted at the default position 0 in the end of the queue
[2017-05-17 00:00:16,967] INFO - tbrains.buildServer.ACTIVITIES - Build added to queue; Queued build {Build promotion {promotion id=106997, configuration={id=Framework_DevOps_BcDevopsDashboard_CreateDocumentation, internal id=bt611}, branch=<default>, queued}, triggered by "Schedule Trigger"}
[2017-05-17 00:00:16,996] INFO - ity.BuildQueuePriorityOrdering - New item Queued build {Build promotion {promotion id=106998, configuration={id=Framework_DevOps_BcOctopusSteps_AppDeployToCi, internal id=bt715}}, item id=106998} with weight 0.00 inserted at the default position 1 in the end of the queue
[2017-05-17 00:00:17,189] INFO - tbrains.buildServer.ACTIVITIES - Build added to queue; Queued build {Build promotion {promotion id=106998, configuration={id=Framework_DevOps_BcOctopusSteps_AppDeployToCi, internal id=bt715}, queued}, triggered by "Schedule Trigger"}
[2017-05-17 00:00:17,632] INFO - jetbrains.buildServer.SERVER - Running build saved to DB: build id=106997, promotion id=106997
[2017-05-17 00:00:17,649] INFO - tbrains.buildServer.ACTIVITIES - Build started; DevOps :: BC.DevopsDashboard :: Documentation - Crawl repos & build MkDocs {id=Framework_DevOps_BcDevopsDashboard_CreateDocumentation, internal id=bt611} #312 {build id=106997, promotion id=106997, branch=<default>, history=false, agent="BuildAgent-A" {id=6}, triggered by "Schedule Trigger" (##showAsIs='Schedule Trigger' type='schedule'). Started 2017-05-17 00:00:17.194, running}
[2017-05-17 00:00:17,665] INFO - jetbrains.buildServer.SERVER - Build removed from queue (started): 106997
[2017-05-17 00:00:17,665] INFO - jetbrains.buildServer.SERVER - Flush queue finished in 473ms, number of builds started: 1
[2017-05-17 00:00:18,272] INFO - jetbrains.buildServer.SERVER - Running build saved to DB: build id=106998, promotion id=106998
[2017-05-17 00:00:18,310] INFO - tbrains.buildServer.ACTIVITIES - Build started; DevOps :: BC.OctopusSteps :: App - Deploy To CI {id=Framework_DevOps_BcOctopusSteps_AppDeployToCi, internal id=bt715} #48 {build id=106998, promotion id=106998, history=false, agent="BuildAgent-B" {id=7}, triggered by "Schedule Trigger" (##showAsIs='Schedule Trigger' type='schedule'). Started 2017-05-17 00:00:18.166, running}
[2017-05-17 00:00:18,324] INFO - jetbrains.buildServer.SERVER - Build removed from queue (started): 106998
[2017-05-17 00:00:18,324] INFO - jetbrains.buildServer.SERVER - Flush queue finished in 158ms, number of builds started: 1
[2017-05-17 00:00:21,899] INFO - jetbrains.buildServer.SERVER - Build finished received for build: #312 {build id=106997, buildTypeId=Framework_DevOps_BcDevopsDashboard_CreateDocumentation}
[2017-05-17 00:00:21,986] INFO - ndexer.EventBasedBuildsIndexer - Indexing finishing build: #312 {build id=106997, buildTypeId=Framework_DevOps_BcDevopsDashboard_CreateDocumentation}
[2017-05-17 00:00:22,929] INFO - de.impl.history.DBBuildHistory - Created build history entry; build id: 106997, finish date: 2017-05-17 00:00:21.770
[2017-05-17 00:00:22,955] INFO - tbrains.buildServer.ACTIVITIES - Finished build DevOps :: BC.DevopsDashboard :: Documentation - Crawl repos & build MkDocs {id=Framework_DevOps_BcDevopsDashboard_CreateDocumentation, internal id=bt611} #312 {build id=106997, promotion id=106997, branch=<default>, history=false, agent="BuildAgent-A" {id=6}, triggered by "Schedule Trigger" (##showAsIs='Schedule Trigger' type='schedule'). Started 2017-05-17 00:00:17.194, running}
[2017-05-17 00:01:21,674] INFO - jetbrains.buildServer.SERVER - Build finished received for build: #48 {build id=106998, buildTypeId=Framework_DevOps_BcOctopusSteps_AppDeployToCi}
[2017-05-17 00:01:21,709] INFO - ndexer.EventBasedBuildsIndexer - Indexing finishing build: #48 {build id=106998, buildTypeId=Framework_DevOps_BcOctopusSteps_AppDeployToCi}
[2017-05-17 00:01:21,818] INFO - de.impl.history.DBBuildHistory - Created build history entry; build id: 106998, finish date: 2017-05-17 00:01:20.969
[2017-05-17 00:01:21,834] INFO - tbrains.buildServer.ACTIVITIES - Finished build DevOps :: BC.OctopusSteps :: App - Deploy To CI {id=Framework_DevOps_BcOctopusSteps_AppDeployToCi, internal id=bt715} #48 {build id=106998, promotion id=106998, history=false, agent="BuildAgent-B" {id=7}, triggered by "Schedule Trigger" (##showAsIs='Schedule Trigger' type='schedule'). Started 2017-05-17 00:00:37.402, running}
[2017-05-17 00:32:54,800] WARN - dServer.updates.VersionChecker - Unable to check for TeamCity version updates via URL "https://www.jetbrains.com/teamcity/update.xml": java.net.ConnectException: Connection timed out: connect (enable debug to see stacktrace)
[2017-05-17 01:00:05,752] INFO - ity.BuildQueuePriorityOrdering - New item Queued build {Build promotion {promotion id=106999, configuration={id=AptisPlus_3RunE2eTests, internal id=bt676}}, item id=106999} with weight 0.00 inserted at the default position 0 in the end of the queue
[2017-05-17 01:00:06,040] INFO - tbrains.buildServer.ACTIVITIES - Build added to queue; Queued build {Build promotion {promotion id=106999, configuration={id=AptisPlus_3RunE2eTests, internal id=bt676}, branch=sbu/e2e, queued}, triggered by "Schedule Trigger"}
[2017-05-17 01:00:06,655] INFO - jetbrains.buildServer.SERVER - Running build saved to DB: build id=106999, promotion id=106999
[2017-05-17 01:00:06,670] INFO - tbrains.buildServer.ACTIVITIES - Build started; AptisPlus :: 3. Run e2e Smoke Tests {id=AptisPlus_3RunE2eTests, internal id=bt676} #66 {build id=106999, promotion id=106999, branch=sbu/e2e, history=false, agent="BuildAgent-C" {id=9}, triggered by "Schedule Trigger" (##showAsIs='Schedule Trigger' type='schedule'). Started 2017-05-17 01:00:06.566, running}
[2017-05-17 01:00:06,696] INFO - jetbrains.buildServer.SERVER - Build removed from queue (started): 106999
[2017-05-17 01:00:06,696] INFO - jetbrains.buildServer.SERVER - Flush queue finished in 143ms, number of builds started: 1
[2017-05-17 01:00:14,176] INFO - jetbrains.buildServer.SERVER - Build finished received for build: #66 {build id=106999, buildTypeId=AptisPlus_3RunE2eTests}
[2017-05-17 01:00:14,230] INFO - ndexer.EventBasedBuildsIndexer - Indexing finishing build: #66 {build id=106999, buildTypeId=AptisPlus_3RunE2eTests}
[2017-05-17 01:00:14,501] INFO - de.impl.history.DBBuildHistory - Created build history entry; build id: 106999, finish date: 2017-05-17 01:00:13.952
[2017-05-17 01:00:14,518] INFO - tbrains.buildServer.ACTIVITIES - Finished build AptisPlus :: 3. Run e2e Smoke Tests {id=AptisPlus_3RunE2eTests, internal id=bt676} #66 {build id=106999, promotion id=106999, branch=sbu/e2e, history=false, agent="BuildAgent-C" {id=9}, triggered by "Schedule Trigger" (##showAsIs='Schedule Trigger' type='schedule'). Started 2017-05-17 01:00:08.192, running}
[2017-05-17 01:28:49,288] INFO - jetbrains.buildServer.CLEANUP - Searching for obsolete log files (not used by any build) under build logs directory: F:\TeamCity\Data\system\messages
[2017-05-17 01:28:49,288] INFO - jetbrains.buildServer.CLEANUP - Cannot find obsolete build log directories in old format
[2017-05-17 01:28:49,448] INFO - jetbrains.buildServer.CLEANUP - Searching for obsolete artifact directories (not used by any build) under directories: [F:\TeamCity\Data\system\artifacts]
[2017-05-17 01:28:57,649] INFO - jetbrains.buildServer.CLEANUP - Removed 1 obsolete artifact directories (6284 processed), disk space freed: 197 B
[2017-05-17 01:28:57,794] INFO - jetbrains.buildServer.CLEANUP - Removed 1 empty artifact directories
[2017-05-17 02:00:00,127] INFO - jetbrains.buildServer.CLEANUP - Git cleanup started
[2017-05-17 02:00:00,368] INFO - jetbrains.buildServer.CLEANUP - Remove unused git repository dir F:\TeamCity\Data\system\caches\git\git-8EBCCB24.git
[2017-05-17 02:00:01,146] INFO - jetbrains.buildServer.CLEANUP - Git cleanup finished

Dont have any Errors in logs. Only Warns and infos

0

Could you please attach zip with teamcity-server.logs ?

0
Avatar
Permanently deleted user

How ? Because i have this error :

You can only upload images (jpeg, gif or png). Image uploads are limited to 2MB.

0

Filip, you can use the 'submit a request option' at the top right and send an email with the logs attached or share logs with us via dropbox, for instance.

Apologies for the inconvenience.

 

 

0

Please sign in to leave a comment.