RPi 2: Transmission not starting on boot
|
Posts: 32
Threads: 4
Joined: Feb 2016
Reputation:
0
[Solved]
Feb 17, 2016, 07:04 PM
I am using a Raspberry Pi 2 with Raspbian Jessie.
Transmission is not starting on boot.
I had it starting on boot, but it broke somehow during the process of resolving an issue with getting my external USB drive to mount properly and NZBGet to start properly.
I currently have edited /etc/rc.local by adding the following lines before the exit:
Quote:service transmission-daemon stop
sleep 5
service transmission-daemon start
I've tooled around with it, changing the value form 5, 10, 15. Nothing works.
I also tried using Mike's suggestion (replacing suggestion (replacing the instructions above in the exact same place) posted in the comments:
Quote:sleep 60
service transmission-daemon restart
This also did not work.
Posts: 403
Threads: 26
Joined: Aug 2015
Reputation:
39
[Solved]
Feb 17, 2016, 07:29 PM
I know that you have used Mikes auto installer and I'm not saying that it's bad but you lose control when you get in trouble. Have you tried to remove transmission and install it manually?
http://www.htpcguides.com/install-transm...untu-15-x/
Posts: 32
Threads: 4
Joined: Feb 2016
Reputation:
0
[Solved]
Feb 17, 2016, 07:37 PM
(Feb 17, 2016, 07:29 PM)manne Wrote: I know that you have used Mikes auto installer and I'm not saying that it's bad but you lose control when you get in trouble. Have you tried to remove transmission and install it manually?
http://www.htpcguides.com/install-transm...untu-15-x/
The ease of installation with the auto-installer is wonderful. That said, it does make things difficult to trouble shoot going into the future.
When I run something like:
Code:
sudo apt-get purge transmission
I am met with the following:
Quote:Package 'transmission' is not installed, so not removed
So, to uninstall and reinstall is a bit trickier than normal. If I go that route, I need help to figure out how sufficiently uninstall the package and its configuration files.
Posts: 403
Threads: 26
Joined: Aug 2015
Reputation:
39
[Solved]
Feb 17, 2016, 07:48 PM
Quote:sudo nano /lib/systemd/system/transmission-daemon.service
what do you get?
ExecStart=??
Posts: 32
Threads: 4
Joined: Feb 2016
Reputation:
0
[Solved]
Feb 17, 2016, 07:57 PM
(Feb 17, 2016, 07:48 PM)manne Wrote: Quote:sudo nano /lib/systemd/system/transmission-daemon.service
what do you get?
ExecStart=??
I get the following:
Quote:[Unit]
Description=Transmission BitTorrent Daemon
After=network.target
[Service]
User=debian-transmission
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error -g /etc/transmission-daem$
ExecReload=/bin/kill -s HUP $MAINPID
[Install]
WantedBy=multi-user.target
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Feb 17, 2016, 07:57 PM
The transmission package is transmission-daemon. The installer uses transmission-daemon from the repository and makes the modifications to the settings.json file. As you both point out this can make troubleshooting harder but they are just automated versions of the manual installation guides (unless I made a mistake somewhere).
I am going to recommend using monit ( guide) to make sure it's always running after you get debug the service.
What does sudo service transmission-daemon start say?
Posts: 32
Threads: 4
Joined: Feb 2016
Reputation:
0
[Solved]
Feb 17, 2016, 08:07 PM
(This post was last modified: Feb 17, 2016, 08:55 PM by killa909.
Edit Reason: fixed formatting
)
(Feb 17, 2016, 07:57 PM)Mike Wrote: The transmission package is transmission-daemon. The installer uses transmission-daemon from the repository and makes the modifications to the settings.json file. As you both point out this can make troubleshooting harder but they are just automated versions of the manual installation guides (unless I made a mistake somewhere).
I am going to recommend using monit (guide) to make sure it's always running after you get debug the service.
What does sudo service transmission-daemon start say?
I have been considering installing monit. I will give that a whirl.
Entering sudo service transmission-daemon start, results in nothing from the console and does not start Transmission. If I use webmin and reload the service, it loads.
Installing monit did not go well. Producing the SSL key may have worked, but the instructions for editing monitrc were difficult to follow and I don't think I did it correctly. Starting monit.service was unsuccessful.
I'd really like to see if I can get this existing Transmission installation working or delete it and start new. After I get that sorted, then I can possibly move on to monit.
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Feb 17, 2016, 08:54 PM
Hmm then somehow Webmin is starting the service differently, can you run these commands
Code:
sudo find / -iname transmission-daemon.service
sudo find / -iname transmision-daemon
As for monit, you actually don't edit the existing monitrc file (that is why it is renamed) but rather create a fresh one. I did my best to make it work out of the box but I'm interested in improving it further which we can do in another thread.
Posts: 32
Threads: 4
Joined: Feb 2016
Reputation:
0
[Solved]
Feb 17, 2016, 09:14 PM
(Feb 17, 2016, 08:54 PM)Mike Wrote: Hmm then somehow Webmin is starting the service differently, can you run these commands
Code:
sudo find / -iname transmission-daemon.service
sudo find / -iname transmision-daemon
As for monit, you actually don't edit the existing monitrc file (that is why it is renamed) but rather create a fresh one. I did my best to make it work out of the box but I'm interested in improving it further which we can do in another thread.
transmission-daemon.service:
Quote:/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/transmission-daemon.service
/lib/systemd/system/transmission-daemon.service
/sys/fs/cgroup/systemd/system.slice/transmission-daemon.service
transmission-daemon returns nothing.
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Feb 17, 2016, 09:30 PM
hmm as @manne pointed out show us the contents of /lib/systemd/system/transmission-daemon.service
You can try disabling the service and re-enabling it, then try sudo service transmission-daemon start
Code:
sudo systemctl disable transmission-daemon.service
sudo systemctl disable transmission-daemon.service
|
|
Recent Posts
|
Split Tunnel Docker Containers
jonesPhedra Mar 27, 2024, 03:10 AM
|
Plex server not powerful enough, but only with s...
jonesPhedra Mar 27, 2024, 03:02 AM
|
About Swap
jonescelinaa Mar 18, 2024, 02:11 AM
|
game Geometry Dash Scratch
jonescelinaa Jan 31, 2024, 04:21 AM
|
Find My IP Address - Kodi - Updated
jonesPhedra Jan 29, 2024, 02:56 AM
|
Latest unread posts | Unanswered posts |
|