diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-09-18 15:44:26 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-09-18 15:44:26 -0400 |
| commit | 0a4fbdf1713b32174b87ca212101d7928170dee3 (patch) | |
| tree | 9eca53bcfc7b78ec87a613f7accd995845c3cd47 | |
| parent | f0446fb2f83983bfcbe9e513ddb92520b6fad7af (diff) | |
| parent | d6a46a6047de7e2c07706950d89460be268d39eb (diff) | |
Merge branch 'master' of ssh://git-annex.branchable.com
| -rw-r--r-- | doc/bugs/box.com/comment_1_d904a08519424cb9f599b2154d1ef953._comment | 10 | ||||
| -rw-r--r-- | doc/forum/SSH_remote_transfers_queued_but_no_movement/comment_1_fea4e2317f850d6166480cddba088ae5._comment | 10 |
2 files changed, 20 insertions, 0 deletions
diff --git a/doc/bugs/box.com/comment_1_d904a08519424cb9f599b2154d1ef953._comment b/doc/bugs/box.com/comment_1_d904a08519424cb9f599b2154d1ef953._comment new file mode 100644 index 000000000..d230e52aa --- /dev/null +++ b/doc/bugs/box.com/comment_1_d904a08519424cb9f599b2154d1ef953._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 1" + date="2014-09-18T19:28:56Z" + content=""" +Ok, I managed to reproduce this. In my case, there was no \"Bad creds\" message because the broken creds data it used happened to contain a newline, but same problem; the creds stored by the webapp are not used properly when re-enabling the box.com remote elsewhere. Same problem would affect other special remotes using embedded creds and shared encryption. + +Seems to be a bug introduced in [[!commit fbdeeeed5fa276d94be587c8916d725eddcaf546]]. Despite what the commit says, the embedded creds did get encrypted with the shared gpg key. I have reverted that commit to fix this problem. +"""]] diff --git a/doc/forum/SSH_remote_transfers_queued_but_no_movement/comment_1_fea4e2317f850d6166480cddba088ae5._comment b/doc/forum/SSH_remote_transfers_queued_but_no_movement/comment_1_fea4e2317f850d6166480cddba088ae5._comment new file mode 100644 index 000000000..d9bf5a97f --- /dev/null +++ b/doc/forum/SSH_remote_transfers_queued_but_no_movement/comment_1_fea4e2317f850d6166480cddba088ae5._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 1" + date="2014-09-18T19:41:39Z" + content=""" +First, take a look at the output of `ps fax` .. you should see a `git-annex assistant` process and near it there ought to be a `git annex transferkeys` process. See if that process has any children under it, like perhaps a rsync. If so, it might just be stalled talking to the host for some reason. + +The best way to debug it further is probably to run `git annex copy --to $remote` at the command line, passing the name of your remote repository. See if it also stalls there. If so, add a --debug and you can see the actual rsync commands it's using, and perhaps work out the problem from there. +"""]] |