Teamcity complains about Perforce VCS root timezone
Hi, we've been randomly getting this error when trying to connect to VCS roots. All roots in all projects will suddenly be giving this error, yesterday I rebooted the TC server and it seemed to solve it, but it occurred again over night. Please let me know what I can do, thanks.
Failed to build patch for build #8.0.30.0 {build id=2836241, buildTypeId=KnowledgeBases_KnowledgeBases80_KnowledgeBases_Cath_CathBuild}, VCS root: "Informatics_Develop (1)" {instance id=9064, parent internal id=3578, parent id=KnowledgeBases_KnowledgeBases80_KnowledgeBases_Cath_InformaticsDevelop1, description: "perforce: p4.inside.clinical-knowledge.com:1666: perforce client mapping with 17 rules"}, due to error: Cannot find server timezone info in `p4 info` output: [Error running p4 -u TeamCity -p p4.inside.clinical-knowledge.com:1666 info: Timeout exception: the process did not produce output longer than 10 seconds; Process: p4 -u TeamCity -p p4.inside.clinical-knowledge.com:1666 info]
Please sign in to leave a comment.
Have there been any environmental changes to your platform recently? You may be running into this issue: https://youtrack.jetbrains.com/issue/TW-67482. There is a workaround in the comments suggesting an increase to the timeout by adding teamcity.perforce.info.timeout=<new timeout in ms> to your server Internal Properties. The default is 10000 (10 seconds), so you could try increasing it to something like 20000. In the case the error is occurring on the build agent, add this setting to the buildAgent.properties file on your build agent to see if it would make any difference.
Nothing has changed in our environment, I'm going to increase the timeout and see if that fixes it. Seems more like a bandaid though since it just seemingly started happening out of nowhere.
If increasing the timeout eliminates the issue, that means there may be something causing a slow response from your perforce server. However, this would be outside of the control of TeamCity since this would indicate that TeamCity has not received a response from your perforce server for 10 seconds.