Thank you Tom.
Sure, I will try that
EDIT: transmission does not start anymore…
I got this message after changing the unit: Warning: Unit file of transmission-daemon.service changed on disk, 'systemctl daemon-reload' recommended, so this is what I did.
And now, when I want to ‘start’ tranmission…
Job for transmission-daemon.service failed. See 'systemctl status transmission-daemon.service' and 'journalctl -xn' for details.
Hi,
Please post the contents of your transmission-daemon.service file here and the output of:
systemctl status transmission-daemon.service
and
journalctl -xn
Thanks Tom.
Jul 07 21:31:32 osmc transmission-daemon[9759]: [2017-07-07 21:31:32.806 CEST] JSON parse failed in /var/lib/transmission-daemon/.config/transmission-daemon/settings.json at pos 225: SPECIAL_EXPECTED -- remaining text "# "bind-addres"
Jul 07 21:31:32 osmc transmission-daemon[9759]: [2017-07-07 21:31:32.806 CEST] transmission-daemon Error loading config file -- exiting. (daemon.c:519)
Jul 07 21:31:32 osmc systemd[1]: transmission-daemon.service: main process exited, code=exited, status=255/n/a
Jul 07 21:31:32 osmc systemd[1]: Failed to start Transmission BitTorrent Daemon.
Jul 07 21:31:32 osmc systemd[1]: Unit transmission-daemon.service entered failed state.
and…
-- Logs begin at Wed 2017-07-05 20:41:04 CEST, end at Fri 2017-07-07 21:38:00 CEST. --
Jul 07 21:31:32 osmc systemd[1]: Unit transmission-daemon.service entered failed state.
Jul 07 21:31:32 osmc sudo[9756]: pam_unix(sudo:session): session closed for user root
Jul 07 21:37:00 osmc sudo[9774]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/systemctl status transmission-daemon.service
Jul 07 21:37:00 osmc sudo[9774]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
Jul 07 21:37:00 osmc sudo[9774]: pam_unix(sudo:session): session closed for user root
Jul 07 21:37:20 osmc sudo[9779]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/systemctl status transmission-daemon.service -l
Jul 07 21:37:20 osmc sudo[9779]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
Jul 07 21:37:20 osmc sudo[9779]: pam_unix(sudo:session): session closed for user root
Jul 07 21:38:00 osmc sudo[9783]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/journalctl -xn
Jul 07 21:38:00 osmc sudo[9783]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
EDIT: same problem with the openvpn address in ipv4 from settings.json or with “0.0.0.0”
EDIT2: removing the # "bind address ..." from settings.json, I do not get this error message anymore, when I ‘start’ transmission… but it does not start
EDIT3: here the new status
* transmission-daemon.service - Transmission BitTorrent Daemon
Loaded: loaded (/lib/systemd/system/transmission-daemon.service; enabled)
Active: active (running) since Fri 2017-07-07 21:42:00 CEST; 2min 40s ago
Main PID: 9841 (transmission-da)
Status: "Idle."
CGroup: /system.slice/transmission-daemon.service
`-9841 /usr/bin/transmission-daemon -f --log-error
Jul 07 21:42:00 osmc systemd[1]: Started Transmission BitTorrent Daemon.
Jul 07 21:42:01 osmc transmission-daemon[9841]: [2017-07-07 21:42:01.345 CEST] UDP Failed to set receive buffer: requested 4194304, got 327680 (tr-udp.c:78)
Jul 07 21:42:01 osmc transmission-daemon[9841]: [2017-07-07 21:42:01.346 CEST] UDP Failed to set send buffer: requested 1048576, got 327680 (tr-udp.c:89)
and journal
-- Logs begin at Wed 2017-07-05 20:41:04 CEST, end at Fri 2017-07-07 21:45:35 CEST. --
Jul 07 21:42:00 osmc systemd[1]: Starting Transmission BitTorrent Daemon...
-- Subject: Unit transmission-daemon.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit transmission-daemon.service has begun starting up.
Jul 07 21:42:00 osmc systemd[1]: Started Transmission BitTorrent Daemon.
-- Subject: Unit transmission-daemon.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit transmission-daemon.service has finished starting up.
--
-- The start-up result is done.
Jul 07 21:42:00 osmc sudo[9838]: pam_unix(sudo:session): session closed for user root
Jul 07 21:42:01 osmc transmission-daemon[9841]: [2017-07-07 21:42:01.345 CEST] UDP Failed to set receive buffer: requested 4194304, got 327680 (tr-udp.c:78)
Jul 07 21:42:01 osmc transmission-daemon[9841]: [2017-07-07 21:42:01.346 CEST] UDP Failed to set send buffer: requested 1048576, got 327680 (tr-udp.c:89)
Jul 07 21:44:41 osmc sudo[9853]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/systemctl status transmission-daemon.service -l
Jul 07 21:44:41 osmc sudo[9853]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
Jul 07 21:44:41 osmc sudo[9853]: pam_unix(sudo:session): session closed for user root
Jul 07 21:45:35 osmc sudo[9857]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/journalctl -xn
Jul 07 21:45:35 osmc sudo[9857]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)Hi,
When you say you ran: systemctl daemon-reload, did you issue:
sudo systemctl daemon-reload
As you need root privileges to action the command.
Thanks Tom.
Yes, i did
EDIT: what are the original lines from the transmission unit section ? I can try to replace those back to check
Hi,
Please post the output of:
cat /lib/systemd/system/transmission-daemon.service
Thanks Tom.
[Unit]
Description=Transmission BitTorrent Daemon
Requires=openvpn.service
After=openvpn.service
[Service]
User=debian-transmission
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error
ExecReload=/bin/kill -s HUP $MAINPID
[Install]
WantedBy=multi-user.target
Hi,
These are both stupid questions, but lets just rule them out.
output please of:
cat /etc/systemd/system/multi-user.target.wants/transmission-daemon.service
Also is openvpn running:
systemctl status openvpn.service
Also the original section was:
[Unit]
Description=Transmission BitTorrent Daemon
After=network.target
Thanks Tom.
It seems to be working. Could you clarify what the issue is now?
[Unit]
Description=Transmission BitTorrent Daemon
Requires=openvpn.service
After=openvpn.service
[Service]
User=debian-transmission
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error
ExecReload=/bin/kill -s HUP $MAINPID
[Install]
WantedBy=multi-user.target
* openvpn.service - OpenVPN service
Loaded: loaded (/lib/systemd/system/openvpn.service; enabled)
Active: active (exited) since Wed 2017-07-05 22:48:08 CEST; 1 day 23h ago
Main PID: 1518 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/openvpn.service
Jul 05 22:48:08 osmc systemd[1]: Started OpenVPN service.
The web GUI does not open, therefore it looks to me as it is not working…
EDIT: well, I can try to purge and re-install again…
Is it binding to the openvpn IP address?
no, doesn’t
Hi,
Not sure if it will make any difference, but the only thing that is different with my service file and yours is the sleep that dilthedog suggested. So you could try adding this to the [Service] section of transmission-daemon.service:
`ExecStartPre=/bin/sleep 5`
Thanks Tom.
I tried to purge (was OK)… But then, when I tried to re-install I got the following message
Downloading/unpacking transmission-daemon
Could not find any downloads that satisfy the requirement transmission-daemon
Cleaning up...
No distributions at all found for transmission-daemon
Storing debug log for failure in /root/.pip/pip.log
Weird…
If you have a transmission user and password set, what does
transmission-remote localhost -n user:password -l give?
transmission-remote is part of the package transmission-cli, so install if not already there with apt-get.
I rebooted, re-installed without pip…directly from apt-get install and it works now.
When I stop the openvpn, transmission stops… but when I start openvpn again, it does not start automatically
It won’t. You’ve just manually restarted openvpn, so need to do the same for transmission. Transmission requires openvpn to be running, but not vice versa.
Do you mean that it is not possible to have transmission starting and stopping as openvpn does ? I guess it should be possible under systemd too.
No, I’m simply saying that’s how it’s currently configured.
You can try to make them mutually dependent but, TBH, it doesn’t make a great deal of sense configuring it that way.