This time I hadn't done such a backup since I did my last big dig and I almost feel like I'm being punished for having any faith at all that qB would be stable for more than a few days. At that time I ended up getting my queue back and just had to remove several dozen items that I knew had finished (plus found several more over the course of the year that have been duplicates).
#Qbittorrent v3.3.7 software#
At that time I was able to recover because I had backed up the BT_backup (your software is BAD at fastresuming).
Just for reference, the last time this happened to me was only a few months ago (March or April). I have just left it on for a day and a half since I booted into the ~560 queue (work) and am only now trying recovery. local/share/data/qBittorrent directory has a BT_backup with 1312 items and my 'torrents' directory has about 1200 more files than my 'torrents-completed' directory yet qB is screwed. I am currently trying to figure out why my. Sledgehammer999, I have always been grateful to you for the work you have done/do, but this software has serious flaws and has for all of the most of a decade that I've been using it.
#Qbittorrent v3.3.7 torrent#
The worst part is that I considered the several days of digging that produced that queue to be work and now I have to do even more work to redo it because I have to manually compare everything to the files that have already been archived (I already manually check each torrent that completes against the rest of the queue to remove the other 'same files'). It did it after I upped my queue to 2k files. When I started using qB again I told myself that it was unstable, prone to screwing me as a user, and that when it did I would have only myself to blame. When I switched before I went to Deluge and found that it is more stable yet qB pulls in faster. Items that had been in the queue since December 2015 are missing! When qB was opened post reboot I had a queue of ~560 items and everything was in a different order (very important when you queue multiple torrents to get the same file as you can't be sure which will actually have a seed and come in). I am here now because most recently I told my computer (Debian Jessie, Gnome) to reboot and had a queue of ~2170 items, mostly added via magnets (including over 1k torrents from ONE long research dig on ONE topic). Ok, I have experienced this (or something like it) multiple times over the years and it has driven me away from qB before (the integrated search engine brought me back as it really suits my work style, but with btdigg gone it produces next to no results now). 20:17:16 - qBittorrent is trying to listen on any interface port: TCP/6881 20:17:16 - HTTP user agent is qBittorrent v3.1.12 20:17:16 - Local Peer Discovery support 20:17:16 - Options were saved successfully. 20:17:16 - The Web UI is listening on port 8080
20:17:17 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/4433 20:17:17 - qBittorrent is successfully listening on interface :: port: TCP/4434 20:17:17 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/6881 20:17:17 - qBittorrent is successfully listening on interface :: port: TCP/6881 20:17:18 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP.
0 kommentar(er)
