Comments in the moderation queue:
Recent comments posted to this site:
That seemed to work, thanks:
$ git fsck --no-reflogs |wc
Checking object directories: 100% (256/256), done.
error: refs/gcrypt/gitception+ does not point to a valid object!
error: refs/remotes/Beta/git-annex does not point to a valid object!
error: refs/remotes/Beta/master does not point to a valid object!
Checking connectivity: 128728, done.
369082 1165340 20898546
Thanks for your help!
I decommissioned a machine and installed git annex on another machine, with the same IP as the initial one. To avoid errors, I declared the first repository as dead and created a new one (with a new remote). However, I also had to remove the git remote to the dead machine as "git annex sync" kept telling me synchronizing to this dead machine failed (the ssh succeeded, using the name automatically generated by git annex, but the repository was not at the same path on the new machine, so it could not find it).
Should a dead repository not tried to be synchronized at all during git annex sync?
greg has confirmed that he can connect to the webapp, but it never replies to http requests. So, this could be the port being bound, but the accept failing.
I don't know why it would retry the accept once per second, but this could be something in warp or the network library.
A workaround for this is using an external app that pings the media scanner to rescan. It's an extra step to remember, but I haven't found it too much of a burden.
I use this one: https://play.google.com/store/apps/details?id=com.addz.mediascanner, but there are at least a dozen to choose from.
Agreed, the dbus and accept messages are probably unrelated. I just commented here because it's the same bug I'm encountering.
The dbus message only appears once in the log (shortly after startup). The accept messages appears every second.