Strangeness On 2.1.1 lt 1.2.15, new migration from 1.3

Specific support for Deluge on Microsoft Windows OS
User avatar
ambipro
Moderator
Moderator
Posts: 418
Joined: Thu May 19, 2022 3:33 am
Contact:

Re: Strangeness On 2.1.1 lt 1.2.15, new migration from 1.3

Post by ambipro »

nimer wrote: Mon Aug 08, 2022 8:05 am heres my issue and its kinda hard to describe

if i filter any of my torrents using any of the sidebar criteria, the results populate correctly for about 15 seconds and then all the main torrents come flooding into the browser making the desired results scroll away,.

same thing happens if i use the search feature. the correct results appear pretty instantly however are only viewable for 15seconds

i thought i would check here first, before mucking around with Libtorrent 2.0.6

maybe i’m having a moron moment but i’m still unclear as to notably what the difference is between 1.2.15 and 2.0.6…..

i’m aware i’ll need to go seek out the correct ltconfig if i make this swap….

any suggestions?

the new version is so remarkably fast that i’ve already satisfied to myself i’ll work around this oddity if its just how things are for now.

thanks in advance

happy to try to make a movie showing the bug,
So I was seeing this issue previously, I believe it was replicable when I would reapply the libtorrent defaults or maybe minimum memory usage profiles in ltconfig, have apply at startup checked, apply, hit ok, and restart deluge. When it would restart my entire GUI experience would be almost impossible to navigate successfully, including going to active, paused, seeding and seeing relevant torrents. I would have to apply pre-ltconfig or high performance seed and apply, hit ok, and restart to get my GUI to act properly once more. Not sure what the deal was. This occured on 1.2.x and 2.0.x as far as I remember.

Maybe mhertz has some insight? I'm not sure if this is universal, though. I was on 2.1.1, and last time this occured was this morning when I was trying to fix some memory "leak/usage" issues I've been experiencing once again that myself and mhertz have pretty much determined is libtorrent.
tasoss
New User
New User
Posts: 8
Joined: Sun Jan 09, 2022 2:29 am

Re: Strangeness On 2.1.1 lt 1.2.15, new migration from 1.3

Post by tasoss »

Hello and thanks for replying.
I have created a new user on my machine.
I installed deluge there and everything works just fine.
I'm running 2 different instances of the app from two different users.
I only download from the new one and let the previous one seed.
To be honest i was playing with ltconfig settings a lot that period...
User avatar
ambipro
Moderator
Moderator
Posts: 418
Joined: Thu May 19, 2022 3:33 am
Contact:

Re: Strangeness On 2.1.1 lt 1.2.15, new migration from 1.3

Post by ambipro »

tasoss wrote: Sat Dec 17, 2022 4:08 pm Hello and thanks for replying.
I have created a new user on my machine.
I installed deluge there and everything works just fine.
I'm running 2 different instances of the app from two different users.
I only download from the new one and let the previous one seed.
To be honest i was playing with ltconfig settings a lot that period...
I went back and read about your issue, I'm not sure - as you didn't mention - but do you use ltconfig as well? I use windows 10, so this may differ on ubuntu, but I noticed with minimum usage profile in ltconfig exiting was god awful with around 875 torrents seeding, I usually killed the process, and then changed settings to get this fixed, but that doesn't sound at all like normal behavior.

If you do use ltconfig, a few things I've noticed similar, although it may not be the same, behavior with is the validate_https_tracker setting preventing me from getting successful tracker announces done. I had a private tracker I literally couldn't get announces done, and say 0/0 until I disabled this in ltconfig and then everything worked.

What do you see in the "Trackers" tab when you first add the torrent after announce sent (Should say "Announce OK" if a response is received and then your seeds/peers will update if they exist) Is this the same on all trackers or just one? Does it show announcing successfully?

What strikes me as odd is that you say that it does inevitably start after a few hours, which perhaps might be a DHT thing if your trackers aren't able to update? Just a guess...are these public trackers and do you have DHT enabled in deluge?

I know there's a lot to digest, but there are many possibilities...I'd start with checking the trackers tab and seeing exactly what your tracker's announce responses are on new torrents you're having problems with, and from there maybe disable validate_https_tracker in ltconfig if you are receiving errors like "unspecified system error" in the tracker status blank.

I'll check back for a response, hopefully we can help you get this narrowed down just a bit.
tasoss
New User
New User
Posts: 8
Joined: Sun Jan 09, 2022 2:29 am

Re: Strangeness On 2.1.1 lt 1.2.15, new migration from 1.3

Post by tasoss »

To be honest i was playing with ltconfig settings a lot that period...
I use private trackers and i don't get a "Announce OK" only "Announce sent".
I am not using the "validate_https_tracker" option.
I am not using DHT at all.
Moreover i am using this patch https://github.com/ratanakvlun/deluge-ltconfig/pull/24
but i don't think that this is a problem because my second instance uses the same configuration
and works as expected.Also, it used to work for a long time with this patch...
User avatar
ambipro
Moderator
Moderator
Posts: 418
Joined: Thu May 19, 2022 3:33 am
Contact:

Re: Strangeness On 2.1.1 lt 1.2.15, new migration from 1.3

Post by ambipro »

tasoss wrote: Wed Dec 21, 2022 6:45 pm
To be honest i was playing with ltconfig settings a lot that period...
I use private trackers and i don't get a "Announce OK" only "Announce sent".
I am not using the "validate_https_tracker" option.
I am not using DHT at all.
Moreover i am using this patch https://github.com/ratanakvlun/deluge-ltconfig/pull/24
but i don't think that this is a problem because my second instance uses the same configuration
and works as expected.Also, it used to work for a long time with this patch...
This generally means, from my understanding, that your not receiving any acknowledgment of your announcement from the tracker...which would prevent you from seeding anything effectively or receiving peers/seed data. I'm not particularly sure what would cause this, as my initial guess was the validate_https_tracker which I had experienced, but since you said you weren't using that...

I'm not sure if you mentioned it, but this happens on all trackers? https udp or standard http, yes? That then leads me to believe it's possibly a libtorrent issue, but I'm not sure of the inner workings of deluge or where the announce is falling apart...

Have you tried a completely vanilla/new profile for deluge (you don't have to delete your old one, you can use command-line to launch from a empty directory, I think its -c /path/here) and see if that work? Then it would most likely be your config somewhere, if not, you may try using apt-get to remove and purge libtorrent and deluge and reinstalling, of course backing up your profile first.
tasoss
New User
New User
Posts: 8
Joined: Sun Jan 09, 2022 2:29 am

Re: Strangeness On 2.1.1 lt 1.2.15, new migration from 1.3

Post by tasoss »

Yes it happens on all trackers.
As i have already mentioned , i have created a new user on the linux machine.
I'm running another instance of deluged and it's running without any problems(same libtorrent,same ltconfig settings).
I was trying to print some messages in order to debug it but with no luck.
And to be honest i don't like python :P
Anyway , it seems that the problem is affecting only a few users so...
If you have any ideas on how to continue investigating it , let me know.
Thanks again!
User avatar
ambipro
Moderator
Moderator
Posts: 418
Joined: Thu May 19, 2022 3:33 am
Contact:

Re: Strangeness On 2.1.1 lt 1.2.15, new migration from 1.3

Post by ambipro »

mhertz may be able to help a bit with how to test this method effectively, but could you run deluge FROM the user you have success with tracker announces, but with the profile (-c \path\to\profile) of the one you do not? Essentially testing an exact replica setup in every manner?

I know you said your setup is identical, but there must be something different, and if it works from your working user with the other profile, then I would be leaning toward there are some permissions or user-specific settings (firewall/iptables/etc) that are preventing you from successfully announcing rather than looking at the torrent client. I assume your libtorrent and deluge files are system-wide and aren't separate, that would also be necessary to determine the validity of this test.

You may also need to chown your profile to the working user (temporarily) to give permission to r/w before executing deluge...

I'm not familiar with the exact commands or anything besides -c for profile selection, so hopefully you can figure that out or mhertz can chime in as he tends to do whenever needed <3
mhertz
Moderator
Moderator
Posts: 2195
Joined: Wed Jan 22, 2014 5:05 am
Location: Denmark

Re: Strangeness On 2.1.1 lt 1.2.15, new migration from 1.3

Post by mhertz »

Awesome idea ambipro, but honestly I have no constructive feedback additionally, and seeing you're more than on-top-of-things clearly and much more helpful than me, but anyways just wanted say much love to you and rest good people all around this board, and happy holidays you all, if celebrating such in your parts of the woods :)

Ohh, like ambipro stated, then just to make absolutely sure you have tried 'validate_https_trackers' false right? I wasn't sure about how you answered that(could mean both ways, unless I'm dense). If not, and since all trackers, then sounds like using libtorrent from pypi and hence for Linux need use an extra command to enable https tracker announces, or validate_https_trackers command, though would not differ between user accounts.

That ltconfig patch I would guess not related. I've thought about building it merged and posting here when first saw it, but didn't because honestly didn't really get the appeal, especially since outdated hard-coded default preset, but regardless.

Last, did you check debug-logging e.g deluge -L debug -l deluge.log.

Cheers
User avatar
ambipro
Moderator
Moderator
Posts: 418
Joined: Thu May 19, 2022 3:33 am
Contact:

Re: Strangeness On 2.1.1 lt 1.2.15, new migration from 1.3

Post by ambipro »

tasoss wrote: Wed Dec 21, 2022 6:45 pm I am not using the "validate_https_tracker" option.
mhertz is correct, while you may not use the option it could still technically be enabled. Just because it is greyed out doesn't mean it's not being utilized. If I'm not mistaken it is a default option in all profiles.

I would suggest you ensure that "Apply settings on startup" is checked (I assume you do have that) and go down, check the box for validate_https_tracker and disable it, hit apply, restart deluge and see if that changes things. I know this is probably not the issue at this point, but just for sanity's sake, especially before going through the hassle of testing the profile on the other user thing I suggested.

Note: If you can't seem to select the checkbox to disable/enable the option, click the checkbox you want to enable/disable (it won't signal that you have) and use the spacebar to toggle after...this is a known bug in ltconfig.
nimer
Member
Member
Posts: 16
Joined: Mon Aug 08, 2022 7:50 am

Re: Strangeness On 2.1.1 lt 1.2.15, new migration from 1.3

Post by nimer »

ambipro wrote: Sat Dec 17, 2022 3:59 pm When it would restart my entire GUI experience would be almost impossible to navigate successfully, including going to active, paused, seeding and seeing relevant torrents.
Do you mean like it renders the gui normally and then you click on a torrent and try to change the download location for example and in those 20 seconds the entire gui almost appears to have a memory overflow which causes the entire list of torrents to refresh, causing that selected item/items to be unselected? - my solution to this issue is simply time, no idea whats happening behind the scenes, my system has ooooodles of spare resources.... as below if the gui is stopping you from enjoying a afternoon of plex. Add the torrents via auto-add active, and reboot server



As silly as it sounds... my solution, untill some white knight saves the day with what i'm almost certain of is a simple setting change

if i want the file NOW, i add the torrent as usual through autoadd where it would otherwise take 2 Hours 15min before starting, and then restart the server...

I have things set to auto launch deluge behind a login screen, kinda like a server but running client windows 10 pro....

What i have found is that 30min or so where the entire thing is spinning up, it queues those undownloaded items in front of the other 9,000 torrents set to seed automatically.

its a solution, not a very excellent one. but it works for me...

While there are some teething issues... especially when considering my seed size... moving to 2.1.1 has been stupendous
Post Reply