Closed Palpatineli closed 7 months ago
As a sanity check, I was able to clone
+ get
the sub-nwu01
subject on my personal machine, so I don't think this is a universal issue?
<Code>InvalidToken</Code><Message>The provided token is malformed or otherwise invalid.</Message>
This seems like the important bit from the error message? (Thank you for providing the full log! :hearts:)
From other reports of this same error, it may be that git-annex is picking up on some pre-existing AWS credentials, either in ~/.aws
or in various AWS-specific environment variables.
As a quick check, could you see if you have .aws
in your home folder, and also check if you have any of the following environment variables set using echo
?
# Check if either empty (not set) or non-empty (secrets -- don't share!)
echo $AWS_SESSION_TOKEN
echo $AWS_ACCESS_KEY
echo $AWS_ACCESS_KEY_ID
echo $AWS_SECRET_ACCESS_KEY
Also, as a quick note, regarding the "Maybe add some of these remotes" message, see https://github.com/spine-generic/data-multi-subject/issues/132#issuecomment-1279115797:
No, these remotes are an internal server, and someone's laptop, neither of which is accessible from the internet, so they wouldn't work. It's an unfortunate side-effect of how git-annex works that these details are visible to you.
While we wait for more details, I've marked this extra remote as inaccessible, so it should stop showing up as a suggestion once people run git annex sync
:
b4e0530d-c6b2-440c-8080-b7fb53d79990 -- sebeda@joplin.neuro.polymtl.ca:~/datasets/data-multi-subject_v2
Thanks for the help! Turns out I have an AWS_SESSION_TOKEN hidden in a startup file from long time ago. It works when I unset it.
Excellent! Thanks for letting us know that this is resolved. And if anyone else has the same problem in the future, we'll know how to solve it.
Can you advise on how to further debug, or is there a problem with the server config?
And when I add the other remote
> git remote add b4e0530d-c6b2-440c-8080-b7fb53d79990 -- sebeda@joplin.neuro.polymtl.ca:~/datasets/data-multi-subject_v2
I gotthen the same amazon error message.