Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Harbor synchronous mirror occasional write connection timeout #20434

Closed
smallemployees opened this issue May 15, 2024 · 4 comments
Closed

Harbor synchronous mirror occasional write connection timeout #20434

smallemployees opened this issue May 15, 2024 · 4 comments

Comments

@smallemployees
Copy link

If you are reporting a problem, please make sure the following information are provided:

Expected behavior and actual behavior:
A clear and concise description of what you expected to happen and what's the actual behavior. If applicable, add screenshots to help explain your problem.
How will I change the timeout time
Steps to reproduce the problem:
Please provide the steps to reproduce this problem.
failed to pushing the blob write: connection timed out
Versions:
Please specify the versions of following systems.
v2.2.1

  • harbor version: [x.x.x]
  • docker engine version: [y.y.y]
  • docker-compose version: [z.z.z]

Additional context:

  • Harbor config files: You can get them by packaging harbor.yml and files in the same directory, including subdirectory.
  • Log files: You can get them by package the /var/log/harbor/ .
@wy65701436
Copy link
Contributor

Please upgrade your harbor instance since v2.2 is out of support, then rerun the scenario. If you still have the same problem, please provide the core and registry log.

@smallemployees
Copy link
Author

image
image

@smallemployees
Copy link
Author

Is there a way to address this issue without upgrading the version? What is the main root cause? Due to architecture reasons, I am unable to upgrade in the short term. Is there any way to alleviate this problem

@wy65701436
Copy link
Contributor

since we apply the n-2 support strategy, the code case has changed a lot since 2.2. The problems that most likely already resolved in the latest release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants