Can you please be a bit less cryptic? How to make the updates? Using wget? To which urls? The additional code should be added at the end of the profile file?
Can you please be a bit less cryptic? => not understood. How to make the updates? Using wget? To which urls? => make for libevent ( libevent-2.0.15-stable ) => debian package for intltool (dpkg -i intltool-debian_0.35.0+20060710.1_all.deb, and replace binary extracted from /usr/local/share to /usr/bin) The additional code should be added at the end of the profile file? => yes
1/ And don't forget before start : Make a backup of transmission folder (/addons-config), libevent binary (/usr/lib) and intltool (/usr/bin).
2/ Here a copy of my folders needed to build transmission : http://dl.free.fr/e1DRUWV3C (all binary are already available due the "make" and "configure" from these folders) from 4.1.8 firmware, sparc platforms and transmission package 2.33, intltool = (dpkg -i intltool-debian_0.35.0+20060710.1_all.deb, and replace binary extracted from /usr/local/share to /usr/bin) libevent = (execute in command line just a "make install" from libevent) transmission = (execute in command line just a "make install")
Everytime I've tried to install many of the latest versions of Transmission, I always get the popup error :
"The Transmission add-on encountered an error during installation."
A few seconds later come the three popup menus telling me to adjust my settings.json and it's installed. However, I have had problems getting any of them to actually start (they appear started in the frontview GUI, but via SSH everything seems dead and won't start).
I realise there is little support around this addon, so have been trying for a couple of months on and off to fix it myself. Does anyone know WHERE the error encountered during installation would be logged ? Or anyway of disassembling the "bin" add-on file to look at the scripts (maybe I'm using a share directory name than conflicts with the install, etc.) ?
There's two minor issues with the x86 2.42 release;
Firstly it takes over 30 seconds to "start" when enabled in frontview, and once it starts frontview incorrectly displays a message that it failed to start (even though it does start successfully). So there's an issue between the frontview portion of the add-on and the transmission service itself.
Secondly, the service DOES fail to start once the NAS is restarted, and a manual restart has to be performed. This leads to the same behaviour described above, but it does start and can be used.
Currently not experiencing any other stability issues (i.e: crashing or high CPU usage) but this is more likely due to the fact i'm only seeding one item and not downloading anything else.
[EDIT]: Just checked the transtart.sh, transtop.sh and blocklist.sh files as suggested by super-poussin in this thread (although he's referring to the SPARC version);
Anyway, the password for the admin user, as specified in these files is still saying "password1" even though I've changed the password for the admin user. So I manually changed the password for those three files to what I set via the web interface. Transmission still takes a bit longer to start up, but now says "Transmission Service Started" instead of "Failed To Start". Not tried a reboot or blocklist check as of yet, as the NAS is busy doing other stuff.
Maybe super-poussin hasn't had time to post the link yet.
With my knowledge of the ReadyNAS SDK (http://www.readynas.com/sdk) and considering super-poussin's earlier posts the update is available for those who already have the latest version linked to on the site installed.
If you download the latest version in the thread and open it in a text editor you will find the available add-on XML link. When the add-on is installed, on RAIDiator 4.2.16 or later if you go to Add-ons > Installed, Frontview will check the XML file to see if it refers to a newer version and if so will provide a button suggesting you upgrade.
2.42 has been running nicely on my Duo for a couple of months now. The previous versions kept crashing. So, first of all, thanks to SP for compiling this version for us!
What always bugged me with the new version was the very slow start of the torrents. Somehow they just didn't get the announce correctly from the tracker and kept idling around. After a while, they mostly began downloading though.
For a couple of days I noticed issues with announces for all kinds of trackers and also at seeding torrents. They only show "Announce is queued" in the Tracker-tab of the inspector.
I searched the Transmission-bug-tracker for this, but it seems that this issue should have been resolved for a couple of versions.
Transmission hogs 98% of my Duos CPU, although nothing seems to happen there. There are a couple of hundred torrents in there, but it never choked before. I tried restart/reboot. DHT is disabled, LPD enabled.
Does anybody notice this, too, or has a hint on how to resolve it?
