Perforce Checkpoint Causing Timeout Exception

We have an scheduled task that checkpoints the Perforce database nightly at 2:00 AM every night.  This process takes less than 4 minutes to execute but can occasionally cause problems when invocation of p4 commands occur during the time that Perforce is checkpointing.  We are seeing errors like this: VcsRootVcsException: Timeout exception: the process did not produce output longer than 60 seconds; Process: p4.  What can we do to mitigate this problem?

3 comments
Comment actions Permalink

Hi Ken,

What TeamCity version do you use? Here is the related request: https://youtrack.jetbrains.com/issue/TW-36603, that was fixed in TeamCity 8.1.3. If you use older version please upgrade to the latest one (9.1 as of now).

0
Comment actions Permalink

We are running version 8.1.5. According to this, we shouldn't be experiencing this problem. We are planning on upgrading to 9.1 as soon as possible. Aside from this issue, we are also having lots of problems using Perforce with ticket-based authentication.  Later this week we will be setting our Perforce server's security level to 3 - all interactions with Perforce server must be ticket-based.  We've asked our user base to go ahead and start using passwords for the Perforce logins and to be sure to configure TeamCity VCS roots with their username AND password AND select the use ticket-based authentication option.  As soon as a user resets and tests their VCS root to use a password with ticket-based authentication, all other VCS roots start to fail. The only thing we have found to resolve this issue is to stop and start the TeamCity Server service.

0
Comment actions Permalink

Please upgrade to TeamCity 9.1. If the issues are reproduced on the latest version, then please attach teamcity-vcs.log and teamcity-server.log files.

0

Please sign in to leave a comment.