RPi 2: Transmission not starting on boot
|
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Apr 09, 2016, 09:35 PM
Looks like you could have DNS issues suggested by the NTP failure.
Those UDP errors could indicate a firewall or something.
Those torrent path errors mean the hard drive may not be mounted yet so transmission fails, can you try this for me?
Add this to the local.conf in the transmission-daemon.service.d folder at the top then daemon reload and restart, disable monit first (update-rc.d monit disable)
Code:
RequiresMountsFor=/absolute/path/of/mount
Glad monit is doing its job though.
Posts: 37
Threads: 5
Joined: Apr 2016
Reputation:
2
[Solved]
Apr 10, 2016, 07:12 AM
(This post was last modified: Apr 10, 2016, 07:13 AM by Viktor.)
Thank you Mike but it did not solve my problem :/
This is how my config file looks like:
Code:
[Unit]
RequiresMountsFor=/mnt/usbstorage
After=network.target
[Service]
User=pi
ExecStart=
ExecStart=/usr/bin/transmission-daemon -f --log-error -g /etc/transmission-daemon
The Monit log is still the same:
Code:
[EEST Apr 10 10:09:43] error : 'Transmission' failed, cannot open a connection to INET[127.0.0.1:9091] via TCP
[EEST Apr 10 10:09:43] info : 'Transmission' trying to restart
[EEST Apr 10 10:09:43] info : 'Transmission' stop: /usr/sbin/service
[EEST Apr 10 10:09:44] info : 'Transmission' start: /usr/sbin/service
[EEST Apr 10 10:10:45] info : 'Transmission' connection succeeded to INET[127.0.0.1:9091] via TCP
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Apr 10, 2016, 07:36 AM
(This post was last modified: Apr 10, 2016, 07:38 AM by Mike.)
@Viktor try this instead, remove the RequiresMountsFor line and replace it with this, Transmission will take longer to start but hopefully this will solve the problem
It may need to be in the [Service] area if this is right
Posts: 37
Threads: 5
Joined: Apr 2016
Reputation:
2
[Solved]
Apr 10, 2016, 07:55 AM
(This post was last modified: Apr 10, 2016, 08:43 AM by Viktor.)
It did not help. I really don't understand what the problem is.
Why for sudo systemctl daemon-reload is working but at boot not? what this command do?
Monit log is the same
Thats what i have in the daemon.log
Code:
Apr 10 10:04:49 raspberrypi transmission-daemon[2093]: [2016-04-10 10:04:49.180 EEST] UDP Failed to set receive buffer: requested 4194304, got 327680 (tr-udp.c:78)
Apr 10 10:04:49 raspberrypi transmission-daemon[2093]: [2016-04-10 10:04:49.180 EEST] UDP Failed to set send buffer: requested 1048576, got 327680 (tr-udp.c:89
btw
I dont have this error message in the log anymore:
Code:
Apr 9 20:24:08 raspberrypi transmission-daemon[492]: [2016-04-09 20:24:08.420 EEST] Torrent name censored No data found! Ensure your drives are connected or use "Set Location". To re-download, remove the torrent and re-add it. (torrent.c:536)
One time I tried to connect to wifi just to see how its working but later I had to change password on my rooter because the rapsberry was connecting all the time to wifi instead of Lan. I still can see this error messages in daemon.log that it try to connect to the wifi. Maybe this can mess up something?
Nope tried to connect through wifi, but the problem is same. Weak try
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Apr 10, 2016, 07:49 PM
@Viktor can you try this, remember to disable monit temporarily?
Code:
sudo update-rc.d transmission-daemon defaults 98
Posts: 37
Threads: 5
Joined: Apr 2016
Reputation:
2
[Solved]
Apr 11, 2016, 05:34 PM
(This post was last modified: Apr 11, 2016, 07:58 PM by Viktor.)
Thank you @Mike but unfortunately it's not working. I am getting frustrated with that problem. :/ After I enabled Monit and restarted the service it runs perfectly. I can not figure out why.
Edited!
I think I discovered something important. I have the same issue with MiniDLNA. After reboot Monit says that the service is running but until I don't restart it I can not see any file in the folder. Even had one time same error log as the Transmission had.
Almost identical to the Transmission's error log. I used your guide for Transmission, MiniDLNA and Mointing HDD. I think it is a HDD mounting problem or some network issue.
Code:
[EEST Apr 10 16:04:08] error : 'miniDLNA' failed, cannot open a connection to INET[127.0.0.1:8200] via TCP
[EEST Apr 10 16:04:08] info : 'miniDLNA' trying to restart
[EEST Apr 10 16:04:08] info : 'miniDLNA' stop: /usr/sbin/service
[EEST Apr 10 16:04:09] info : 'miniDLNA' start: /usr/sbin/service
[EEST Apr 10 16:05:10] info : 'miniDLNA' connection succeeded to INET[127.0.0.1:8200] via TCP
P.S What is this code? its a script right? should I remove it now that its not working?
Posts: 37
Threads: 5
Joined: Apr 2016
Reputation:
2
[Solved]
Apr 12, 2016, 06:08 PM
Any idea?
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Apr 12, 2016, 06:18 PM
@Viktor it seems the hard drive is slow to mount for some reason. Usually this is fixed by delaying the startup of the init.d or system scripts but this doesn't seem to be helping. It can also be caused by a slow WiFi connection
Is your hard drive and old model? Are you using Minibian, Raspbian or some other distro you found somewhere? Maybe you are on too old a kernel or not the latest kernel? (rpi-update will get you latest).
I can't replicate your issue so unless somebody else has the same problem and resolves it or comes up with another idea then monit is the best solution.
If you have managed to fix it I would love to know how!
Posts: 37
Threads: 5
Joined: Apr 2016
Reputation:
2
[Solved]
Apr 12, 2016, 06:34 PM
Thank you for your reply
My whole system is brand new. I have a new WD RED 1tb with Thermaltake Max 5g hdd enclosure and a Raspberry Pi 3 on Raspbian which is not older than 2 weeks. I am not using WiFi, I just tried one time how its working and that's all.
I am sad to hear that there is no solution for this at the moment. Any suggestion from whom I can get any support solving this issue? Thank you for your effort once again
Posts: 403
Threads: 26
Joined: Aug 2015
Reputation:
39
[Solved]
Apr 12, 2016, 06:38 PM
(This post was last modified: Apr 12, 2016, 06:39 PM by manne.)
I would recommend you to reinstall your system and use Mike's Media server installer. I'm guessing you are using the the official raspbian installer from raspberry website?
Use a new SD card if you don't want to mess your current setup.
|
|
Recent Posts
|
Running Plex over a Split Tunnel VPN
jonescelinaa Apr 27, 2024, 09:19 AM
|
About Swap
jonescelinaa Apr 10, 2024, 06:58 AM
|
Tracker Status: Error Connection Time Out
jonesPhedra Apr 04, 2024, 08:17 AM
|
Plex server not powerful enough, but only with s...
jonesPhedra Mar 27, 2024, 03:02 AM
|
game Geometry Dash Scratch
jonescelinaa Jan 31, 2024, 04:21 AM
|
Latest unread posts | Unanswered posts |
|