mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
basile.pinsard@f1a7fae9f3bd9d5282fca11f62ad53b45a8eb317 2020-02-26 13:46:22 +00:00 • committed by admin
parent 456bff66f8
commit 26e7c935af
1 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_5_6d1d45fee3dd4ae82b5791335fb548b0._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="basile.pinsard@f1a7fae9f3bd9d5282fca11f62ad53b45a8eb317"
nickname="basile.pinsard"
avatar="http://cdn.libravatar.org/avatar/87e1f73acf277ad0337b90fc0253c62e"
subject="comment 5"
date="2020-02-26T13:46:22Z"
content="""
Yes the local IP is already listed in the security parameters, the error message was quite informative.
There are no proxy configured on any of the machines.
tcpdump should show me any data going out to the server.
I looked at the AWS.S3 package, and it seems some bucket resolve function might rely on the DNS, correct me if I am wrong.
The requeststyle is set to path as this is what minio can provide, so the
Could it be that the local DNS do not support some functions that S3 rely on?
However, I already created remotes and pushed data from these servers in the past and I don't think the DNS server has changed since.
As the hotspot test shows, this is an interaction of the local network configuration with git-annex+dependencies code, but I can't figure out how to debug that.
Thanks.
"""]]