Transmission just..... stops working.....
Posted: Fri Jul 01, 2016 2:41 pm
Ok, so I've noticed this issue. Transmission just...well... stops working. I'll get nothing from the url, and any apps I have that talk to it start getting errors saying it's not there. It's still RUNNING, just nothing can talk to it anymore. Everything else works on the box, just transmission stops. It's like it's stopped listening to it's port.
How long it takes varies. But it's at least once a day. All I have to do is ssh in (it's a headless server) and throw a quick "systemctl restart transmission-daemon" at it. Then it's fine for the next little bit. Seems to happen most often when it's idle, haven't noticed it when it's got stuff to do. I currently have written a cron to go and throw a 'systemctl restart' at it every 6 hours, I'll see how that does, but something just doesn't seem right.
Log is clean, seems it stops outputting stuff to the log also once this happens. It's like it gets cut off from the outside world. Nothing in, nothing out...just sits there running. (it does use CPU during this time).
Pi2
Raspbian 8 "Jessie"
Latest transmission from the jessie repository
Any ideas?
How long it takes varies. But it's at least once a day. All I have to do is ssh in (it's a headless server) and throw a quick "systemctl restart transmission-daemon" at it. Then it's fine for the next little bit. Seems to happen most often when it's idle, haven't noticed it when it's got stuff to do. I currently have written a cron to go and throw a 'systemctl restart' at it every 6 hours, I'll see how that does, but something just doesn't seem right.
Log is clean, seems it stops outputting stuff to the log also once this happens. It's like it gets cut off from the outside world. Nothing in, nothing out...just sits there running. (it does use CPU during this time).
Pi2
Raspbian 8 "Jessie"
Latest transmission from the jessie repository
Any ideas?