Recent comments posted to this site:

OK. I ended up having to delete all the files from git, then re-add them zipped up.

I re-read the post you mentioned, this helped me resolve my issue: assistant crashes in TransferScanner (from johannes)

Johannes dropped the file, then re-added, that fixed his issue. So I tried that first.

I did the following:

  • git-annex dropped all problem files. this didn't fix issue
  • deleted all problem files (using OS-X Finder), committed the deletion with git (git add -A), issue then fixed
    • re-added deleted files, issue came back
    • re-added deleted files in different folder, issue came back
    • re-added deleted files all with different filenames in different path, issue came back
    • zipped up folder of problem files, then added to git-annex, no issues
Comment by andrew Mon Jan 23 02:28:23 2017

I found the problem: I was cd'ing into the local repository via a symbolic link, instead of using the "canonical" path. You can mark the bug as solved or delete it. Sorry for the noise.

Comment by jesrui Sat Jan 21 15:08:20 2017

Any thoughts Joey? Reminder I have a v6 repo, that spits out errors git-annex: fd:24: hFlush: resource vanished (Broken pipe) when using sync --content.

I am not sure why git annex sync --content cloud should spew errors, and git annex copy --auto --to cloud runs without issue. Anything I should do on my end to investigate this issue further?

Thanks,

Andrew

Comment by andrew Sat Jan 21 14:56:26 2017
Ok! Got it working, and I can ssh between the two machines and access git-annex-shell on both sides, got all the $PATH stuff right. I set up one repo on the desktop and one on the server, made them remotes of each other, and I have managed to transfer files back and forth using "git annex sync." But how do I get the assistant to do this automatically without command line intervention? Just dropping the file in one folder, it doesn't show up in another, unlike the other git-annex repos I have between my two local computers.
Comment by jaylangseth Wed Jan 18 21:11:15 2017

Log from other side:

[2017-01-18 15:46:22 MSK] main: starting assistant version 5.20140412ubuntu1
[2017-01-18 15:46:22 MSK] Cronner: You should enable consistency checking to protect your data. 
(Recording state in git...)
(scanning...) [2017-01-18 15:46:22 MSK] Watcher: Performing startup scan
(started...) Generating public/private rsa key pair.
Your identification has been saved in /tmp/git-annex-keygen.0/key.
Your public key has been saved in /tmp/git-annex-keygen.0/key.pub.
The key fingerprint is:
aa:c0:c3:b8:ca:4d:5c:85:58:02:b6:a0:4a:64:18:dd echormonov@sml-pc-091
The key's randomart image is:
+--[ RSA 2048]----+
|+B.o .           |
|B o E .          |
|.o . . .         |
|o     .          |
|.    .  S        |
| +. .  .         |
|. =o  .          |
|..oo .           |
|+. ..            |
+-----------------+
[2017-01-18 15:48:26 MSK] main: Pairing in progress
[2017-01-18 15:48:44 MSK] PairListener: abutirsky@sml-pc-066:~/Desktop/gitrepo_test is sending a pair request.
Generating public/private rsa key pair.
Your identification has been saved in /tmp/git-annex-keygen.0/key.
Your public key has been saved in /tmp/git-annex-keygen.0/key.pub.
The key fingerprint is:
28:e0:f4:a2:2c:a2:bc:7a:22:6e:4c:6d:8f:38:ac:b4 echormonov@sml-pc-091
The key's randomart image is:
+--[ RSA 2048]----+
|                 |
|                 |
|  o              |
| o o   .         |
|  + o . S        |
|.o + .           |
|Boo o            |
|O*o. .           |
|XEo              |
+-----------------+
[2017-01-18 15:50:40 MSK] main: Pairing with abutirsky@sml-pc-066:~/Desktop/gitrepo_test in progress

By the way, any comment here is accessible for deletion by anyone. Seems like security hole

Comment by butirsky Wed Jan 18 16:52:21 2017
Version of annex on the other side is 5.20140412ubuntu1, if it matters
Comment by butirsky Wed Jan 18 13:21:45 2017

Having the same issue, the error only on one side, syncing doesn't start:

[2017-01-18 15:25:30.603909] main: starting assistant version 5.20151208-1build1
[2017-01-18 15:25:30.615017] Cronner: You should enable consistency checking to protect your data. 

  No known volume monitor available through dbus; falling back to mtab polling
(scanning...) [2017-01-18 15:25:31.040087] Watcher: Performing startup scan
(started...) 
(scanning...) [2017-01-18 15:27:19.254315] Watcher: Performing startup scan
(started...) git-annex: Daemon is already running.
warning: no common commits
From /home/abutirsky/Desktop/annex
 * [new branch]      annex/direct/master -> annex/annex/direct/master
 * [new branch]      git-annex  -> annex/git-annex
 * [new branch]      master     -> annex/master

(merging annex/git-annex into git-annex...)
(recording state in git...)

Already up-to-date!
Merge made by the 'recursive' strategy.
[2017-01-18 15:29:18.003333] main: Syncing with annex 
[2017-01-18 15:29:18.003518] Pusher: Syncing with annex 
To /home/abutirsky/Desktop/annex
 * [new branch]      git-annex -> synced/git-annex
 * [new branch]      master -> synced/master
Everything up-to-date

(nautilus:19391): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed

(nautilus:19391): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed

(nautilus:19391): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(nautilus:19391): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(nautilus:19391): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
git-annex: Daemon is already running.
(scanning...) [2017-01-18 15:34:47.539423] Watcher: Performing startup scan
(started...) git-annex: Daemon is already running.
git-annex: Daemon is already running.
git-annex: Daemon is already running.


  illegal control characters in pairing message; ignoring

  illegal control characters in pairing message; ignoring

  illegal control characters in pairing message; ignoring

  illegal control characters in pairing message; ignoring

  illegal control characters in pairing message; ignoring

  illegal control characters in pairing message; ignoring

  illegal control characters in pairing message; ignoring

  illegal control characters in pairing message; ignoring

  illegal control characters in pairing message; ignoring
Generating public/private rsa key pair.
Your identification has been saved in /tmp/git-annex-keygen.0/key.
Your public key has been saved in /tmp/git-annex-keygen.0/key.pub.
The key fingerprint is:
SHA256:dJ9VU8CQ+hHL2fsta1E5PkxTvkqDThbyOainUXZvaY4 abutirsky@sml-pc-066
The key's randomart image is:
+---[RSA 2048]----+
|            .+.o+|
|            o ..o|
|        . .o =..o|
|       . o.o=o.=o|
|        So+o*.+o+|
|        o..Boo+= |
|       .. + o=ooo|
|       ... .=.o o|
|       .o  E o.o |
+----[SHA256]-----+
[2017-01-18 15:48:44.423064] main: Pairing in progress

  illegal control characters in pairing message; ignoring

  illegal control characters in pairing message; ignoring

  illegal control characters in pairing message; ignoring
Comment by butirsky Wed Jan 18 13:19:43 2017

i actually answered this in Full workflow guide before realizing this post was a duplicate.

i am not sure where that should be put - it's not a "full workflow guide", it's actually a "specific workflow guide", namely "i have 3 computers and need to sync files from A to B to C"...

i wonder if this should be marked as resolved or if we want to add a specific workflow for this or what?

this reminds me of my broader build a user guide task... -- anarcat

Comment by anarcat Tue Jan 17 16:56:39 2017

looking at the page title here, i'm tempted to simply point you to Workflow guide and therefore the new workflow page, but that may not answer your question directly. so let's see...

the the examples below, i'll assume you are familiar with the commandline and show examples using git and git-annex commands, since you mentioned that. but a lot of those things can be done with the web assistant, if not everything. but i am not very familiar with it, so you'll excuse my geekiness...

  1. I want to start keeping track of some files I have in a directory

     cd directory
     git init
     git annex init
     git annex add "some" "files"
     git commit -m"start keeping track of some files"
    

    Note that you could track all files with git annex add . or git annex add *... regular glob patterns apply.

  2. I want to copy them to a second computer.

    This is the harder part. Here I'll assume that you have an SSH server on the first computer, which i'll name firstcomputer. If that's not your case, you can use the new tor to pair arbitrary machines with the peer to peer network with tor instructions instead of this.

    On the second computer:

     git clone firstcomputer:directory
     cd directory
     git annex get
    
  3. From a third place, I want to get them from the second computer.

    Same comments as above apply.

    On the third computer:

     git clone secondcomputer:directory
     cd directory
     git annex get
    
  4. I change the files on one computer, and I want to make sure the changes get synced to the others.

    This can be done manually with git-annex-sync (with the --content flag to copy actual content), or automated with the git-annex-assistant or git-annex-watch.

Comment by anarcat Tue Jan 17 16:54:22 2017
Ok thanks! I'll give that a try.
Comment by jaylangseth Tue Jan 17 16:37:39 2017