adding a new .torrent from tracker B to seed tracker A's data works some of the time. other times it does not.
I am curious why the daemon is refusing certain torrents. the .torrents have identical hashes embedded, distinct filenames (for the .torrents), and the data being seeding is 100% intact.
this is the error log when I add the unaccepted torrent:
Code: Select all
15:27:56 [ERROR ][deluge.core.rpcserver :1512] type <class 'deluge.error.AddTorrentError'> not handled
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/deluge/core/rpcserver.py", line 160, in sendData
self.transfer_message(data)
File "/usr/lib/python3.10/site-packages/deluge/transfer.py", line 56, in transfer_message
body = zlib.compress(rencode.dumps(data))
File "rencode/rencode.pyx", line 336, in rencode._rencode.dumps
File "rencode/rencode.pyx", line 316, in rencode._rencode.encode
File "rencode/rencode.pyx", line 249, in rencode._rencode.encode_list
File "rencode/rencode.pyx", line 316, in rencode._rencode.encode
File "rencode/rencode.pyx", line 249, in rencode._rencode.encode_list
File "rencode/rencode.pyx", line 322, in rencode._rencode.encode
Exception: type <class 'deluge.error.AddTorrentError'> not handled
deluge 2.0.5
libtorrent 2.0.6.0
python 3.10.4