What does CATCHUPLIST request failed: 400 mean in my cache agent log?
In the remote Cache Agent debug log, you could see entries such as the following:
This means that the remote Cache Agent successfully contacted the upstream Cache Agent and attempted to begin a catch-up operation, but the upstream Cache Agent rejected the request. The most common reason for this is that remote Cache Agent was configured to use a specific upstream Cache Agent, but that upstream Cache Agent is not caching contents for the required StarTeam server GUID.
For example, suppose you configure the remote Cache Agent as follows:
Instead of auto-locating the root Cache Agent, this remote Cache Agent is configured to use the specific upstream Cache Agent amer.test.test.net for GUID a7d26ccd-d95r-46c4-43th-0k209bfb5108c. If, however, the upstream Cache Agent is not caching content for that GUID, the mismatch will be detected in the catch-up cycle, causing the remote Cache Agent’s catch-up request to be rejected with the 400 code (bad request).