Replies: 2 comments
|
I'm not sure what was happening before. but after 5 days, and not like LazyLibrarian or Bookshelf, I came back and did a clean install of this. (I had other problems besides this with readarr imports and it going and downloading everything that i had untracked in readarr since I didn't realize it was turned on to just download everything), files were moved just fine. |
|
Late close out on this one. Glad the clean install sorted you, but the underlying bug was real and it is fixed now, so here is what was happening in case it saves someone else the same afternoon. qBittorrent reports a torrent as complete slightly before the files are actually where it says they are. Bindery took that at face value, went looking for the save path, found nothing there, and logged Fixed in #1976, released in v1.31.0 on 13 August. Completion now checks the negative signals first, and an attempt where the source is simply not there yet no longer counts against the retry budget. One thing from your log that is not a bug: the empty parentheses in |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The folder
dst: /books/Jim Butcher/Out Law ()/was created, but the file never moved. It would appear that qBit was still downloading but Bindery thought the file was completed downloading when it may not have been. Is this some sort of potential bug?I run a "seed box" with TrueNAS on one machine that has the downloads and Bindery.
And another TrueNAS media machine where my books are stored.
I didn't actually have Bindery Bridge setup yet, but I don't think that should be related since merely moving the file should be disconnected from that.
All reactions