Closed nothing2obvi closed 7 months ago
Trace logs are required. The provided logs have nothing to debug and show absolutely no issues nor anything you described
Thanks for taking a look. Please correct me if these are not trace logs:
https://gist.github.com/nothing2obvi/464f06ea62546045701017d5a8d698e9
Just looking at my "public" share limit torrents, I don't see anything about min_seeding_time
for each torrent even though min_seeding_time
is set up in my config.
public:
priority: 9
exclude_any_tags:
- something
- another-thing
- again-another-thing
max_ratio: 1
min_seeding_time: 60
max_seeding_time: 70
resume_torrent_after_change: True
cleanup: False
you've told qbit_manage to seed for at least 60 seconds and a ratio of 1 OR seed for at least 70 seconds -no bug appears to exist
trace logs indicate this seems to be being applied just fine.
also room to improve the logging an add min seed time, https://github.com/StuffAnThings/qbit_manage/blob/46518577f956fcbf2b18d36c4e9c6d3908b01a95/modules/core/share_limits.py#L196-L219
Wow that's set for 60 seconds and not 60 minutes? I greatly misunderstood, thank you so much.
Yes, adding min_seeding_time
to logs would be great.
Thanks again!
Reopening for the logging cc @bobokun
Wow that's set for 60 seconds and not 60 minutes?
No, this should be in minutes, not seconds. I think what @bakerboy448 meant was
you've told qbit_manage to seed for at least 60 minutes and a ratio of 1 OR seed for at least 70 minutes
@bakerboy448
So if it's minutes, then min_seeding_time
really isn't working for me.
No it's working accurately. The values are in second. Thus 60 is 60 seconds 3600 is 1 hour / 60 minutes
Trace logging resolved https://github.com/StuffAnThings/qbit_manage/commit/d5aaa31e4057747524c2c9708fd99d78cc7c1cf4
Okay, if it's seconds then I think I should be good.
So I changed my config to account for seconds, not minutes, and my public
share-limit torrents still aren't seeding. Even the newly added ones since the change.
public:
priority: 9
exclude_any_tags:
- bunch-of-tags-here
max_ratio: 1
min_seeding_time: 3600
max_seeding_time: 4200
resume_torrent_after_change: True
cleanup: False
https://gist.github.com/nothing2obvi/9ec3106c3b464fad98c7f0b559dd23e9
I've noticed that my torrents from private trackers are all seeding, but those from public trackers aren't. Does that have anything to do with it?
Any chance you could try develop which has slightly improved logging on the comparisons
Sorry, I would definitely do it but I'm not sure how to. I'm running a local install. When I go to the develop branch and select Clone
it tells me the URL is https://github.com/StuffAnThings/qbit_manage.git
which I don't think points to the develop branch. Unless I'm wrong about that.
You simple pull and checkout the develop branch.
Used the develop branch and copied my config over.
https://gist.github.com/nothing2obvi/050fca1a5b5f540abc07806001f6e9a4
public:
priority: 9
exclude_any_tags:
- bunch-of-tags-here
max_ratio: 1
min_seeding_time: 3600
max_seeding_time: 4200
resume_torrent_after_change: True
cleanup: False
It's hard to tell because in the screenshot you're hiding the torrent name. But I do see min seed time is working, taking this example:
| Torrent: [Bitsearch.to] Prometheus.2012.2160p.UHD.BDRemux.DTS-HD.MA.7.1.HDR.DoVi.Hybrid.P8.by.DVT.mkv [Hash: 344d031905ac72f54d0bcd35d8ae2f532e5caf16] |
| Torrent Category: 4k-movies-radarr |
| Torrent Tags: other |
| Grouping: public |
| Config Max Ratio vs Torrent Max Ratio:1.0 vs 1 |
| check_max_ratio: False |
| Config Max Seeding Time vs Torrent Max Seeding Time: 4200 vs 60 |
| Config Max Seeding Time vs Torrent Current Seeding Time: (4200 vs 0.23333333333333334) 2 days, 22:00:00 vs 0:00:14 |
| Config Min Seeding Time vs Torrent Current Seeding Time: (3600 vs 0.23333333333333334) 2 days, 12:00:00 vs 0:00:14 |
| Config Min Num Seeds vs Torrent Num Seeds: 0 vs 3 |
| check_max_seeding_time: True |
| Config Limit Upload Speed vs Torrent Limit Upload Speed: -1 vs 488 |
| check_limit_upload_speed: True |
| hash_not_prev_checked: True |
| share_limits_not_yet_tagged: True |
| Torrent Name: [Bitsearch.to] Prometheus.2012.2160p.UHD.BDRemux.DTS-HD.MA.7.1.HDR.DoVi.Hybrid.P8.by.DVT.mkv |
| Tracker: udp://tracker2.dler.com:80 |
| Min seed time not met: 0:00:14 <= 2 days, 12:00:00. Removing Share Limits so qBittorrent can continue seeding. |
| Adding Tag: nmst |
| Torrent Name: [Bitsearch.to] Prometheus.2012.2160p.UHD.BDRemux.DTS-HD.MA.7.1.HDR.DoVi.Hybrid.P8.by.DVT.mkv |
| Tracker: udp://tracker2.dler.com:80 |
| Added Tag: sl_9.public |
| Share Limit: Max Ratio = 1.0, Max Seed Time = 4200 min |
It shows that Min seed time not met: 0:00:14 <= 2 days, 12:00:00. Removing Share Limits so qBittorrent can continue seeding.
Is that torrent seeding? If not can you right click the torrent in the webUI and go to Limit Share Ratio
and screenshot that? Can you also try highlighting these "completed" torrents and choose resume to see if they start seeding?
Can you also check your qbitorrent settings go to the BitTorrent tab? Screenshot the Seeding Limits section
Thanks for following up.
Oh sorry I didn't mean to hide the torrent names I just thought the tags would suffice. Unfortunately, that torrent was already removed by Radarr (I think).
I was able to highlight those completed torrents and resume them, and they seeded, but then they all went back to completed within less than 5 minutes. Also, if min_seeding_time
is working, shouldn't it auto-resume the torrent? "If the torrent has not yet reached this minimum seeding time, it will change the share limits back to no limits and resume the torrent to continue seeding."
Can you right click one of the torrents that are completed and check what the share limits qbittorrent has set on them? Does it match with what's in your qbm config?
I'm not quite sure how to do that -- I right clicked on a torrent, clicked on Limit share ratio
and it gave me this:
These are all the choices presented when I right click on a torrent:
Does it matter that I have automatic torrent management turned on? Or does it matter that I was using qBittorrent 4.3.9? I've now upgraded to 4.5.5 to see if that would make a difference.
Also, as an aside, the numbers in the config really are in minutes then. I was told twice that it was seconds, if you scroll above.
Upgraded to qBittorrent 4.5.5 and it made no difference. See the screenshot below this trace log.
| Torrent: Will.Trent.S02E07.1080p.WEB.h264-ELEANOR[TGx] [Hash: 59742ef3eed0d594141a96a9ee0adae68c8a6015] |
| Torrent Category: tv-sonarr |
| Torrent Tags: nmst, other, sl_9.public |
| Grouping: public |
| Config Max Ratio vs Torrent Max Ratio:1.0 vs -1 |
| check_max_ratio: True |
| Config Max Seeding Time vs Torrent Max Seeding Time: 70 vs -1 |
| Config Max Seeding Time vs Torrent Current Seeding Time: (70 vs 3.066666666666667) 1:10:00 vs 0:03:04 |
| Config Min Seeding Time vs Torrent Current Seeding Time: (60 vs 3.066666666666667) 1:00:00 vs 0:03:04 |
| Config Min Num Seeds vs Torrent Num Seeds: 0 vs 0 |
| check_max_seeding_time: True |
| Config Limit Upload Speed vs Torrent Limit Upload Speed: -1 vs -1 |
| check_limit_upload_speed: False |
| hash_not_prev_checked: True |
| share_limits_not_yet_tagged: False
| Config Max Seeding Time vs Torrent Current Seeding Time: (70 vs 3.066666666666667) 1:10:00 vs 0:03:04 | | Config Min Seeding Time vs Torrent Current Seeding Time: (60 vs 3.066666666666667) 1:00:00 vs 0:03:04 |
Seeding for 3 minutes and not a goal of 70 minutes Seeding for 3 minutes and not a minimum time of 60 minutes
what's the issue?
also yeah as bobo mentioned, minutes not sconds sorry
I think this is most likely a config issue since if min_seeding_time wasn't working it would be a widespread issue affecting a lot more users. I'm closing this issue, if you need additional support please hop onto the discord as it's easier to debug with you there instead of through Github.
Thanks to both of you and for your help, @bobokun, on Discord. I finally solved it and thought I'd share. I noticed that the share limits were working for my downloads from private trackers, but not public trackers. I found a Reddit thread and someone asked if Ultra.cc (my seedbox) supports public trackers. Apparently they do not, and they have scripts that will stop seeding from public trackers once they are done downloading. That's why I could never meet the min_seeding_time
for public trackers.
Thanks again!
Glad you got it figured out and thanks for sharing!
Describe the Bug
min_seeding_time
doesn't seem to work on any of my torrents. For most, but not all torrents, once they're completed they don't seed. If they complete in 4 minutes but mymin_seeding_time
is set to 60 minutes, it has no effect. It won't seed. You can look specifically at mypublic
share-limit.I don't think the logs help.
Am I misunderstanding something?
Config
Logs
https://gist.github.com/nothing2obvi/4108d89a4f64ea2f41bdfec2e5bc2569
Screenshots
No response
Installation
Local
Version Number
4.1.1
What branch are you on?
master