Package Details: aria2cd 2.0.2-1

Git Clone URL: https://aur.archlinux.org/aria2cd.git (read-only, click to copy)
Package Base: aria2cd
Description: A script and systemd serice to start aria2 automatically.
Upstream URL: https://aur.archlinux.org/packages/aria2cd
Keywords: aria2 systemd
Licenses: LicenseRef-WTFPL
Submitter: ZhangHua
Maintainer: ZhangHua
Last Packager: ZhangHua
Votes: 2
Popularity: 0.000242
First Submitted: 2021-09-02 09:14 (UTC)
Last Updated: 2026-01-15 14:00 (UTC)

Pinned Comments

ZhangHua commented on 2025-04-14 10:44 (UTC)

Please check commit message at febe70f13512 if you are updating from 1.x.x to 2.x.x and later.

Latest Comments

ZhangHua commented on 2026-01-15 13:58 (UTC)

@cyqsimon Sounds reasonable. I will set --enable-rpc in service. But I think --log should not be set in service directly, as arguments will always override setting in config file. If I set --log in service, your custom log path will never been applied. Currently aria2's output can be captured by systemd pretty well, so I would better leave it to users.

cyqsimon commented on 2026-01-14 04:20 (UTC)

It seems like v2 is failing to start without explicitly adding the --enable-rpc option in aria2.conf.

systemd[1161]: Started Aria2c Daemon.
aria2c[1202]: Specify at least one URL.
aria2c[1202]: Usage: aria2c [OPTIONS] [URI | MAGNET | TORRENT_FILE | METALINK_FILE]...
aria2c[1202]: See 'aria2c -h'.
systemd[1161]: aria2.service: Main process exited, code=exited, status=1/FAILURE
systemd[1161]: aria2.service: Failed with result 'exit-code'.

Reading the commit message you linked, I understand and agree with most of your choices. But it appears to me that the service should at least include the --enable-rpc option, and perhaps a --log=- option to to use syslog facilities.

ZhangHua commented on 2025-04-14 10:44 (UTC)

Please check commit message at febe70f13512 if you are updating from 1.x.x to 2.x.x and later.

Aut0mata commented on 2024-01-02 03:18 (UTC)

Process: 2335 ExecStartPre=/usr/bin/update-aria2-tracker (code=exited, status=217/USER) (-tracker)[2335]: aria2@user.service: Failed to determine user credentials: No such process systemd[1]: aria2@user.service: Control process exited, code=exited, status=217/USER systemd[1]: aria2@user.service: Failed with result 'exit-code'. systemd[1]: Failed to start Aria2c Daemon for user.

ZhangHua commented on 2021-09-08 10:59 (UTC)

@mmkodali According to aria2 manual(http://aria2.github.io/manual/en/html/aria2c.html#aria2-conf), the default config path is ${HOME}/.aria2/aria2.conf or ${XDG_CONFIG_HOME}/aria2/aria2.conf. So it should work without modifying unit file.

mmkodali commented on 2021-09-08 10:16 (UTC)

Thanks for the advice.

commenting the line Requires=network.target, User=%i and adding --conf-path=/home/xxxx/.aria2/aria2.conf to aria2c allowed me to run the service.

ZhangHua commented on 2021-09-07 13:42 (UTC) (edited on 2021-09-07 13:49 (UTC) by ZhangHua)

@mmkodali Don't enable service with systemctl enable aria2@.service, this service file is a template unit. You should use systemctl enable aria2@user.service instead. See note part of https://wiki.archlinux.org/title/systemd#Using_units for more details. In this unit file, specifier user means username who runs aria2. You should also copy /usr/share/aria2 to /home/user/.aria2 and modify /home/user/.aria2/aria2.conf, or the service will not start normally because you don't have needed config.

mmkodali commented on 2021-09-07 12:56 (UTC)

enabling system service giving following error :

Failed to enable unit: File multi-user.target: Identifier removed