So, I was trying to run deluged on my new home server, but it's bug-city!
The server is running Debian Bookworm (12.4); I've done a regular install from the repo ('# apt install deluged') -
which currently results in:
* deluged 2.0.3
* libtorrent: 2.0.8.0
* Python: 3.11.2
Then disabled the systemd service that is for some reason auto-enabled ('# systemctl disable deluged.service');
Started deluged ('$ deluged'); killed it ('$ pkill deluged'); edited core.conf and auth to enable remote access.
Downloaded ltConfig.egg to /plugins.
Started deluged again; connected via thin client to deluged.
It got my IP correctly and started connecting to DHT nodes.
Changed a few settings:
* download -> set folders for download and move on completion
* bandwidth -> raised the values+disabled rate limiting overhead
* queue -> raised the values+ignore slow torrents
* network -> enabled encryption
* plugins -> enabled blocklist+ltConfig
* ltConfig -> enabled announce to all tiers+announce to all trackers
Then tried a test-torrent:
Dropped torrent file in thin client -> torrent immediately paused.
Note: the "add paused" option was not enabled!
"Resume" not working.
Went back to server; restarted deluged; reconnected.
It's still able to find my IP and DHT nodes, but the torrent stays paused.
Tried starting deluged with logfile + loglevel "info":
A bunch of warnings and exceptions thrown in my face; apparently the broken log.py is >still< a thing on Debian.
By now it's the 3rd or 4th machine where I have to fix this...
Updated Twisted via pip3 ('# pip3 install --upgrade Twisted --break-system-packages').
Went to /usr/lib/python3/dist-packages/deluge; edited log.py ('# nano log.py').
Changed "findCaller(self, stack_info=False)" to "findCaller(self, *args, **kwargs)"; saved & exited.
Finally able to run deluged with logfile+loglevel without all the log.py rubbish.
Loglevel 'info' -> everything OK; no errors or warnings; still torrent won't start.
Loglevel 'debug' -> LOTS of info; I 'THINK' the important part 'MIGHT' be this bit:
Code: Select all
16:31:15 [DEBUG ][deluge.core.rpcserver :1622] intevents: {}
16:31:15 [DEBUG ][deluge.core.torrent :1622] State from lt was: downloading | Session is paused: True
Torrent state set from "None" to "Paused" (9231ee2aee44cd8ab903cc10889bd444b28b3ca5)
16:31:15 [DEBUG ][deluge.core.torrent :1622] Torrent object created.
16:31:15 [DEBUG ][deluge.core.rpcserver :1622] intevents: {}
16:31:15 [DEBUG ][deluge.core.torrentmanager :1622] Torrent added: 9231ee2aee44cd8ab903cc10889bd444b28b3ca5
16:31:15 [INFO ][deluge.core.torrentmanager :1622] Torrent 2023-12-11-raspios-bookworm-armhf-lite.img.xz from user "User123" loaded
16:31:15 [INFO ][deluge.core.torrentmanager :1622] Finished loading 1 torrents in 0:00:00.286234
16:31:15 [DEBUG ][deluge.core.rpcserver :1622] intevents: {}
16:31:15 [DEBUG ][deluge.core.torrent :1622] State from lt was: downloading | Session is paused: True
Torrent state set from "Paused" to "Paused" (9231ee2aee44cd8ab903cc10889bd444b28b3ca5)
16:31:15 [DEBUG ][deluge.core.torrent :1622] State from lt was: downloading | Session is paused: True
Torrent state set from "Paused" to "Paused" (9231ee2aee44cd8ab903cc10889bd444b28b3ca5)
16:31:15 [INFO ][deluge.core.torrentmanager :1622] on_alert_external_ip: 12.34.56.789
16:31:15 [DEBUG ][deluge.core.rpcserver :1622] intevents: {}
If this is not it, then ...dunno...
I've already tried a full purge and reinstall of deluged: same game.
I've also tried connecting to deluged via deluge-console, but the cli crashed almost immediately (Seriously, how come Deluge is so totally broken on Debian?! ).
And now... I really, REALLY dont know what else to do or check anymore.... :/
Help?