There are SSH keys in ~/.ssh to a remote server that I added as a git annex remote. On my Debian box, I am able to git annex copy and git annex move to and from the remote to a local repo at ~/archive with no problems. I also have no problems with external USB drives formatted ext4.
I have an external usb drive formatted NTFS that I connect to a Debian box. I added the remote server like the others and when I try to copy or move to and from it, this error code shows up.
pull archive
Control socket connect(.git/annex/ssh/f7be67fcc0a6f016ba90edcdd8e02e1f): Connection refused
Failed to connect to new control master
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
failed
push archive
Control socket connect(.git/annex/ssh/f7be67fcc0a6f016ba90edcdd8e02e1f): Connection refused
Failed to connect to new control master
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Pushing to archive failed.
I think it is because of NTFS and the ssh key stored in ~/.ssh, but I don't know what is going on.
Thanks!
I think I have tracked down part of the issue. It due to the options that are called by
git-annexwhen trying torsyncbetween the NTFS local hard drive and the SSH remote.I got
rsyncto work by usingrsync -vrc source destas options (outside of git-annex). Found here.Is there any way to change the rsync options put out by git-annex when copying/moving to and from local ntfs drives on linux?
This control socket message sounds like the actual problem is that unix sockets cannot be used on this filesystem. git-annex puts the socket there to make ssh connection caching work.
So, I think you need to disable ssh connection caching:
git config annex.sshcaching falseI was able to reproduce a similar failure on nfts on linux.