NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New Transmission add-on thread
The previous thread was very long time to open a new one and prepare the 2.0 :)
Just noticed something. I didn't have this issue to start with, then one of my drives failed, and i started seeing this behavior. I blamed it on the NAS, seeing as it was one drive short, and no longer redundant. An automatic security measure, disable stuff that isn't really needed, so to speak. Anyway, what it started doing was no longer start Transmission after the NAS is restarted. Got a new drive, stuck it in, got redundancy back, and the issue persisted. Didn't think so much about it since i was upgrading to the beta anyway. How that went, we know. I'm now back to 2.42 and can report that it still does this. I've removed the old transmission version every-time i switched to a different version.
In the addons-config directory, the settings.json is protected writing and reading is not allowed even when the NAS say Transmission isn't running, on boot. After ticking the box in settings, and removing the tick again i can save the setting, and it gets read/write-able. When i tell the NAS to start the Transmission service, i get a "Transmission service failed to start" message, the dot turns green, and it works. If i untick, and tick it again, and tell it to save settings, i get the same message, and guess what, every tracker thinks i'm seeding everything twize.
No check is made to see if Transmission is already running, perhaps this is unintentional?
The main issue tho. Trying to shut down transmission isn't working. It says it stopped the service, and you can access the settings.json, but transmission is still up and running, doing transfers, and letting you manage it through the web interface, or a remote client. Seams the only way to shut down transmission is to reboot the NAS. And if the first thing you do when you start the NAS is to turn of, and save the transmission thingy, even tho it's said to be of already, it makes you able to read/write the settings.json, and trackers seam to actually think your offline. (as do they when you first start the NAS)
However, even now, after starting it, just once, you get the "Transmission service failed to start" message, and a green dot indicating it's running. It also will not shut off from this point on. Something that is slightly painfull when you try to tweak settings.
Needless to say, i gave up. It's running, i hit 3MB/s up, it's going to have to do for now.
Not sure if these bugs are a part of the packaging for ReadyNAS, or if it's a part of the Transmission thingy it self. But short of whiping the NAS, and restarting from scratch, i don't know quite how to get it to behave as intended again.
B!
In the addons-config directory, the settings.json is protected writing and reading is not allowed even when the NAS say Transmission isn't running, on boot. After ticking the box in settings, and removing the tick again i can save the setting, and it gets read/write-able. When i tell the NAS to start the Transmission service, i get a "Transmission service failed to start" message, the dot turns green, and it works. If i untick, and tick it again, and tell it to save settings, i get the same message, and guess what, every tracker thinks i'm seeding everything twize.
No check is made to see if Transmission is already running, perhaps this is unintentional?
The main issue tho. Trying to shut down transmission isn't working. It says it stopped the service, and you can access the settings.json, but transmission is still up and running, doing transfers, and letting you manage it through the web interface, or a remote client. Seams the only way to shut down transmission is to reboot the NAS. And if the first thing you do when you start the NAS is to turn of, and save the transmission thingy, even tho it's said to be of already, it makes you able to read/write the settings.json, and trackers seam to actually think your offline. (as do they when you first start the NAS)
However, even now, after starting it, just once, you get the "Transmission service failed to start" message, and a green dot indicating it's running. It also will not shut off from this point on. Something that is slightly painfull when you try to tweak settings.
Needless to say, i gave up. It's running, i hit 3MB/s up, it's going to have to do for now.
Not sure if these bugs are a part of the packaging for ReadyNAS, or if it's a part of the Transmission thingy it self. But short of whiping the NAS, and restarting from scratch, i don't know quite how to get it to behave as intended again.
B!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
