Jinja_dude
Jinja_dude

Reputation: 529

Transfer Issue with tsop-agent v3.0.5219: Update to v3.0.5235

We recently encountered a problem with our file transfer configuration using the tsop-agent for Google Cloud Storage. Here is a summary of the situation:

Problem Description

  1. Launch an STS job to synchronize a POSIX filesystem on-prem to a GCP bucket.
  2. The synchronization consistently fails since 06/20.

Environment

Diagnosis

Solution

After various tests and verifications, we discovered the problem stemmed from the version of the tsop-agent. An automatic update occurred, upgrading the agent from version v3.0.5219 to version v3.0.5235, which resolved the issue.

Question

Has anyone else experienced this problem with tsop-agent version v3.0.5219? Do you know what was fixed in version v3.0.5235 to resolve this issue? I searched the documentation but couldn't find the release notes to compare the two versions.

Thanks in advance for your help!

Additional Details for Context:

  1. DNS Configuration: DNS resolution for Google URLs is intentionally disabled by our security policies.
  2. Proxy Configuration: Verified and correct, with an initial warning about Boto configuration resolved.
  3. File Size: Specific issue with files around 35 MB or larger.
  4. Logs: Consistent error message on DNS resolution.

Thank you for your attention, and I hope someone can provide insights on the differences between these two versions of the tsop-agent.

Upvotes: 0

Views: 238

Answers (1)

Pranay Kumar Kyasala
Pranay Kumar Kyasala

Reputation: 382

As per the official GCP document on Troubleshoot file system transfers :

The agent version is no longer compatible with Storage Transfer Service.

This is a temporary error, related to a bad agent update. If it occurs, do the following:

  1. Stop all of your agents.

  2. Incase if you are using a docker, Pull the latest docker image by running: sudo docker pull gcr.io/cloud-ingest/tsop-agent

  3. Issue the Docker run command to start all of your agent containers.

If the issue persists, reach out to the GCP support team by creating a new Issue Tracker thread describing your issue.

Upvotes: -1

Related Questions