Closed escape0707 closed 2 years ago
I wonder if your total download task number is over max-concurrent-downloads
, which default is 5
.
If so there should be only 5 active
tasks, and others are in waiting
queue. When a active
task is finished, the first task in waiting
queue will be sent to active
queue thus starts aother download
This can be changed in Options
→ ⚙
after JSON-RPC URI
→ Max Concurrent Downloads
Thanks for your speedy reply.
I'm not running too much downloading tasks simultaneously.
This is the configuration my aria2 RPC server is using:
auto-file-renaming=false
continue=true
enable-rpc=true
file-allocation=falloc
log-level=warn
max-concurrent-downloads=3
max-connection-per-server=4
min-split-size=1M
split=99999
And I only downloaded one .torrent
file. When the downloading of the file finished, Aria2 started the BT download of the torrent, which is not what I wanted. I mainly use qBittorrent for that.
And I only downloaded one
.torrent
file. When the downloading of the file finished, Aria2 started the BT download of the torrent, which is not what I wanted. I mainly use qBittorrent for that.
If you use aria2 to download for example https://test.com/test.torrent
. When the HTTP
download is complete, aria2 will start a Bit Torrent
download based on test.torrent
. It is aria2's default behavior
Sorry, but can you elaborate more on what's text.torrent
? Is that something about MIME? :thinking:
Sorry, that's a typo. I meant aria2 would download .torrent
file from http server, then read the .torrent
file and start a bit-torrent download automatically.
Doesn't that option completely skip the downloading of normal HTTP tasks?
Edit: Just tried it out:
$ aria2c --dry-run https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
09/10 11:51:38 [NOTICE] Downloading 1 item(s)
09/10 11:51:38 [NOTICE] Download complete: /home/jay/Downloads/google-chrome-stable_current_amd64.deb
Download Results:
gid |stat|avg speed |path/URI
======+====+===========+=======================================================
c63330|OK | 0B/s|/home/jay/Downloads/google-chrome-stable_current_amd64.deb
Oops, my fault, it should be
--follow-torrent=true|false|mem
Reference
If true or mem is specified, when a file whose suffix is .torrent or content type is application/x-bittorrent is downloaded, aria2 parses it as a torrent file and downloads files mentioned in it. If mem is specified, a torrent file is not written to the disk, but is just kept in memory. If false is specified, the .torrent file is downloaded to the disk, but is not parsed as a torrent and its contents are not downloaded. Default: true
Oh, thanks! I didn't realize that the default to that option is true
...
Guess I should update my configs.
I use aria2 as my default download manager so I haven't changed many options. I'm happy if your problem is solved 👍
I don't remember this behavior existed earlier. What changed or, what should I change to prevent this?