Deluge 2.0 Beta 1

Suggestions and discussion of future versions
mhertz
Seeder
Seeder
Posts: 108
Joined: Wed Jan 22, 2014 5:05 am
OS or Distro: Arch Linux

Re: Deluge 2.0 Beta 1

Postby mhertz » Thu Jun 14, 2018 8:28 am

Sorry jeps, cannot help, but just wanted to add that lately i'm having the same issue with stable v1.3.15, which i've never had before, and the only change i've done, is to run deluged from it's systemd service file which runs deluge as deluge user instead me running deluged locally. It happens on/off, e.g. every tenth time maybe, but when it happens, it always after having stopped deluged with it's systemd service file(the journalctl doesn't list errors there), through my script. X freezes and I cannot change tabs in chromium or fire up terminals, nothing, so I ctrl+altgr+delete and startx to "fix". Also, I haden't used deluge for 3 months maybe, when I started again, so probably an libtorrent update issue or updated system component/kernel/xorg colliding. The strange thing is that rtorrent did the same, but that was fixed with pkill -2 rtorrent in my script instead of pkill's default signal 15. Probably unrelated, since another version, and happens on exit, but it just caught my eye when you said it took your entire desktop down, like with me too.

Could I please ask you a favor? Whenever you have the time, not in a hurry, then if you could please run deluged and then deluge-console and press return to connect and esc to exit the help screen and then press p - which should open preferences. If nothing happens, then it's arrow-left and then p - do you see preferences coming through, or an error up-top about a deferred error like me? Thanks alot in advance - wanna see if it's a general problem or related to my setup solely(arch-linux) - i've looked through debug-logs and checked the shown files at the reported lines, but isn't good enough at python to understand the whole-complicated deluge-"framework" and nothing "evident" shines through.

Spadge
Seeder
Seeder
Posts: 103
Joined: Sat Dec 13, 2008 4:17 pm

Re: Deluge 2.0 Beta 1

Postby Spadge » Thu Jun 14, 2018 8:49 pm

For me, it's the Incoming Address setting in Preferences/Network that keeps emptying itself. I've not noticed if it's every reboot, or just some reboots, or only reboots after an update, or what. I don't reboot the Pi much. I am aware that I have had to write it in a couple of times. I'll keep a look out for it and write up a bug request when I've worked it out.

The incoming port hasn't deleted itself yet.

mhertz
Seeder
Seeder
Posts: 108
Joined: Wed Jan 22, 2014 5:05 am
OS or Distro: Arch Linux

Re: Deluge 2.0 Beta 1

Postby mhertz » Thu Jun 14, 2018 9:14 pm

Regarding incoming ports, libtorrent will choose another port by default if it can't bind to defined port e.g. if busy, but there's a setting you can disable for this behavior, although if the port is busy, then I don't know what will happen with that setting disabled, since no port to use then. I would try changing the port as it sounds like it could be "busy", and then the libtorrent setting to disable from ltconfig plugin is: 'listen_system_port_fallback = false'(true by default).

About my previous described issue of deluge hanging, and hanging X too, for stable version, then I just noticed that 'sudo systemctl stop deluged.service' sometimes can hang for a minute or so before stops(I use it from a script normally so haden't noticed), When checking 'journalctl -xe', then I can see that deluged doesn't respond to sigterm(signal 15) and hence after timeouts runs signal 9 sigkill and then it stops. I remember that my freezing X issue with rtorrent, where because of running signal 9(or 15) for killing rtorrent from my script, and changing to signal 2 worked, so it seems to be the same issue(kernel/Xorg?). I'm no systemd wizz, but maybe I can change the service file to change this behavior - i'd guess that's a possibility :)

Edit: Yeah, systemd supports 'KillSignal=' option, so I could e.g.:

Code: Select all

sudo mkdir /etc/systemd/system/deluged.service.d
echo "[Service]\nKillSignal=2" | sudo tee /etc/systemd/system/deluged.service.d/deluged.conf
sudo systemctl daemon-reload
pgrep deluged && sudo systemctl restart deluged

Edit2: Crap, signal-2 don't fix it, as just had a freeze! It worked for rtorrent for exact same issue, but this time I run the client under other user-name and kills through sudo, though don't see what that has to do with anything really. I've tried now changing my script to instead killing deluge with 'deluge-console halt' which also might as well should be used anyway, and hoping it will not happen again, but i'm not too convinced honestly.


Return to “Development”

Who is online

Users browsing this forum: No registered users and 4 guests