Arch Linux

MrSweetie

Member

Registered: 2021-12-07

Posts: 3

Transmission config file not created [SOLVED]

Hello,

I am trying to make transmission-cli work properly and I carefully follow the Transmission Arch Wiki.

1. install transmission-cli (Ok).

2. Enable systemctl transmission.service to Run Transmission as the Transmission user (Ok).

3. Accessing the config file located at /var/lib/transmission/.config/transmission-daemon/settings.json (KO).

The /var/lib/transmission/ directory is well created but is empty.
Note that if I try to run Transmission as my logged user using

$ transmission-daemon

then the config file is well created in the .config/transmission directory as specified by the documentation.

I tried to start&stop the service to make sure the config file is not created once it stop, but still nothing.

Any idea?

Last edited by MrSweetie (2021-12-08 21:40:17)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,312

Re: Transmission config file not created [SOLVED]

transmission-daemon running under normal user and transmission.service as transmission user are 2 separate processes that have nothing in common except the executable.

use systemctl start transmission.service to start , systemctl start transmission.service to stop the service (probably needs root rights)

If you already did try that, post journal output .
See https://wiki.archlinux.org/title/Systemd/Journal for more info and options how to filter the output, https://wiki.archlinux.org/title/List_o … n_services for options to post long texts.

Welcome to Archlinux forums .

Last edited by Lone_Wolf (2021-12-07 10:52:58)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

MrSweetie

Member

Registered: 2021-12-07

Posts: 3

Re: Transmission config file not created [SOLVED]

Thank you for your answer and for pointing out to look at the systemd journal, I didn't know where to start. That was fun .

Indeed, the transmission-daemon and the systemd service are two different processes, I included this in case it would help.

I may overexplain but it might be useful for other people who may have the same issue.

1. Running the systemd service: sudo systemctl start --now transmission.service

2. Checking at the journal output for this boot and this specific service: journalctl -b -u transmission.service.

The resulting output is not quite long:

-- Journal begins at Wed 2021-12-08 12:43:35 CET, ends at Wed 2021-12-08 13:14:03 CET. --
Dec 08 13:14:00 pcdevice systemd[1]: Starting Transmission BitTorrent Daemon...
Dec 08 13:14:00 pcdevice systemd[1]: Started Transmission BitTorrent Daemon.
Dec 08 13:14:01 pcdevice transmission-daemon[2480]: [2021-12-08 13:14:01.435] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:97)
Dec 08 13:14:01 pcdevice transmission-daemon[2480]: [2021-12-08 13:14:01.435] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:105)
Dec 08 13:14:01 pcdevice transmission-daemon[2480]: [2021-12-08 13:14:01.435] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:97)
Dec 08 13:14:01 pcdevice transmission-daemon[2480]: [2021-12-08 13:14:01.435] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:105)

Searched for this error on the web and tried this solution (using sudo):

1. Stop the systemd service: sudo systemctl stop --now transmission.service

2. Create a dedicated conf file:

   touch /etc/sysctl.d/<anyname>.conf

3. Add those two lines in the file (we're setting 16 MiB for the receive buffer and 4 MiB for send buffer) :

   net.core.rmem_max = 16777216 
   net.core.wmem_max = 4194304

4. Apply the new parameters:

   sysctl --system

5. Start the systemd service: sudo systemctl start --now transmission.service

The config file is well created and there is no more error.

I know this is off-topic, but may I ask you what are the main differences between running the transmission-daemon and the transmission.service
?

I will mark the post as solved.

Last edited by MrSweetie (2021-12-09 00:24:11)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,312

Re: Transmission config file not created [SOLVED]

functionally there's not much difference, I only use transmission-daemon as user from cli, but that's personal preference.

My biassed answer :

I prefer to have only essential functionality automatically started and seem to have a different view on what's essential then most users.

Transmission is useful for me maybe 5% of the time my pc is on, starting it automatically is unnecessary for and unwanted by me.

I also prefer not to be tied to one PID1 init system and use methods that will work regardless of which init system is used to boot .

The transmission-daemon command does what I need and works on every system where transmission-cli or equivalent is present.
Transmission.service content comes from upstream, but archlinux devs  changed it's name (upstream calls it transmission-daemon.service) .

Last edited by Lone_Wolf (2021-12-08 13:33:29)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

MrSweetie

Member

Registered: 2021-12-07

Posts: 3

Re: Transmission config file not created [SOLVED]

Alright, thanks, it makes sense to me.
I will finish my setup and reconsider the way I use it as my transmission usage is quite similar to yours.