Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
Here's my feedback on the addon.
In short words: No can do..
For instance:
in start.sh: transmission-daemon is send to the foreground by the '-f ' option. But when the start-stop-daemon is called to throw the transmission-daemon to the background, the command breaks on the first fact. The correct option would be the '-g' and than the location of the 'settings.json'file. But if you set the TRANSMISSION_HOME variable correctly, you don't need that option. Second. The environment variable "TRANSMISSION_HOME" is set incorrectly. This must be set tot the same directory as where the 'settings.json' file is. Third: binaries does not belong into the '/etc' directory. Binaries belong (in this case) in /usr/local/bin
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
I find that if I don't use the '-f' (foreground) option the settings don't get saved when the addon is stopped. Probably should remove the --background option in start.sh as it is redundant in this case.
Not sure why you think TRANSMISSION_HOME is set incorrectly. It is set to '/c/addons-config/Transmission' which is where the settings.json is found.
For the binaries, I prefer to put all the files in one directory so they are easy for me to find. For me (and others I'm guessing) it doesn't really matter as we don't remote into the NAS to run the transmission commands directly. But feel free to move them to /usr/local/bin
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
i'm unable to transfer or delete files coming from the Bitorrent folder... it says access denied.. i can copy files without issue.. any help will be greatly appreciated
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
Many thanks for this update.
Has the email alert function been removed?
I've configured my NV+ to use an external email server, installed the 'email_alert' script and changed the relevant setting to 'true' in the settings file - but it still doesn't work for me.
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
raider125jeigh wrote:
i'm unable to transfer or delete files coming from the Bitorrent folder... it says access denied.. i can copy files without issue.. any help will be greatly appreciated
Edit the settings.json file and set the umask to 0.
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
kels wrote:
Many thanks for this update.
Has the email alert function been removed?
I've configured my NV+ to use an external email server, installed the 'email_alert' script and changed the relevant setting to 'true' in the settings file - but it still doesn't work for me.
Am I missing something here?
Thanks kels
@Kels I'm still using the email alerting facility from the SuperPoussin version. I remember having issues initially when I wanted to get emails. I had it all configured but it would just never send an email. Turns out it was permissions on the script file weren't set to 'x' (execute) so it could never be called. After that it was fine. Not long ago I combined my email alert script with an unrar/unzip script to extract torrents after completion which makes my life a bit easier.
if [ -f /etc/frontview/alert.conf ]; then EmailTo=`/bin/grep "email" /etc/frontview/alert.conf | /usr/bin/awk -F '!!' '{ print $2 }' | /usr/bin/awk -F ',' '{ print $1 " " $2 " " $3 }'` else EmailTo=`/bin/grep "email" /frontview/conf/alert.conf | /usr/bin/awk -F '!!' '{ print $2 }' | /usr/bin/awk -F ',' '{ print $1 " " $2 " " $3 }'` fi if [[ "$(readlink `which sendmail`)" = "/usr/bin/msmtp" ]]; then EmailFrom=`/bin/grep '^from' /etc/msmtprc | /usr/bin/cut -f2 -d' '` else EmailFrom=`/bin/echo $EmailTo | awk '{ print $1 }'` fi echo "From:$EmailFrom To:$EmailTo" # Create the email message EmailFile=/tmp/tmp_email.txt if [ -f "$EmailFile" ]; then rm -f $EmailFile fi touch $EmailFile # Create the message headers echo "Date: `date -R`" >> $EmailFile echo "From: $EmailFrom" >> $EmailFile echo "To: $EmailTo" >> $EmailFile echo "Subject:Torrent Done!" >> $EmailFile echo "MIME-Version: 1.0" >> $EmailFile echo "Content-Type: text/plain; charset=ISO-8859-1" >> $EmailFile echo "" >> $EmailFile # Create the message body /bin/echo " Hostname: $HOSTNAME" >> $EmailFile /bin/echo "Transmission finished downloading \"$TR_TORRENT_NAME\" on $TR_TIME_LOCALTIME" >> $EmailFile /bin/echo "" >> $EmailFile /bin/echo "----------------------------------------------------------------------" >> $EmailFile /bin/echo "Your add-ons developer Super-Poussin" >> $EmailFile /bin/cat $EmailFile |/usr/sbin/sendmail -f $EmailFrom $EmailTo #$NAIL -v -S from="$EmailFrom" -S smtp -s "$SUBJECT" -S smtp=$SMTP_SERVER "$EmailTo" < $EmailFile rm -f $EmailFile ################################################################################################################# # you can use nail instead of readynas exim in this case : # # uncomment the $NAIL line # # comment the message header section # # put a correct SMTP_SERVER value # #################################################################################################################
################################################################################################################# # this script will work with exim if you use custom parateters in frontview aka you specify : # # username # # smtp server ans so on # #################################################################################################################
Test exim emails get through - but nothing from Transmission!
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
Kels, you appear to have the stock email script. Compared to my own, in the second line of the script the stock SMTP_SERVER=smtp.orange.fr I changed to whatever smtp resource I am using in Frontview alert (ie: smtp.gmail.com). Not sure if this has an impact. If you can receive test emails from within the Frontview alert testing function then my experience is that Tranmission should work also.
For your reference my relevant settings are below. I think your file permissions would be fine since all users have execute. Make sure you set the script variables correctly. My script is different as mentioned previously because I chucked in an extraction command.
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
Oh most importantly, if you intend on making any changes to settings.json you have to stop Transmission first. Any changes that made to settings.json whilst Transmission is running are lost when Transmission stops. Stop the service, save your changes, then start Transmission again.
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
I uninstalled super-poussin's and WhoCare's Transmission versions. Deleted the folders and rebooted. Installed tarobun's version stopped it and edited the settings file (with inspiration from super-poussin's). Started it. But nothing seems to happen. And no error message alert.
One sign of that something is wrong is that my password was not encrypted and my modifed port setting was dismissed.
Can anyone detect what's wrong with my settings (or if thats the error):
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
fastfwd wrote:
eton wrote:
Can anyone detect what's wrong with my settings
No closing brace. (Or did you just copy it incompletely?)
No comma after "utp-enabled": true . Maybe missing punctuation elsewhere, too; those are just the first errors I saw. There are online JSON validators... You might want to run your file through one to make sure it's error-free.
Thanks fastfwd Yep I didn't copy the closing brace. I added a comma after "utp-enabled": true. And edited the post above. And ran a validator, with no errors. Still the same problem. Transmission starts but nothing happens, and the indicator icon in the upper right corner of the Transmisson modul panel stays grey. How can I debug this? I've never had problems with Transmission or any other addons before.
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
tarobun wrote:
How are you with unix command line? If you are familiar then you can try the following:
tarobun wrote:
To run from command line enter:
cd /etc/frontview/addons/bin/TRANSMISSION ./transmission-daemon --logfile /var/tmp/transmission.log
To view log file:
cat /var/tmp/transmission.log
If not, then there are a few things in the config you could try and remove the following settings as they don't exists anymore (see https://trac.transmissionbt.com/wiki/EditConfigFiles😞 "open-file-limit": 32, "peer-port-random-enabled": 0,
Also check the line endings in the text file, I think they should be unix style line ending (\x0a)
But the problems remain. At first there was nog log file, but after starting Transmission from command line I got this:
# cat /var/tmp/transmission.log [15:59:41.480] Transmission 2.82 (14160) started (session.c:738) [15:59:41.481] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:828) [15:59:41.481] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:1035) [15:59:41.481] RPC Server Whitelist enabled (rpc-server.c:1039) [15:59:41.482] UDP Failed to set receive buffer: requested 4194304, got 1048576 (tr-udp.c:78) [15:59:41.482] UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:83) [15:59:41.482] UDP Failed to set send buffer: requested 1048576, got 524288 (tr-udp.c:89) [15:59:41.482] UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr-udp.c:94) [15:59:41.482] DHT Generating new id (tr-dht.c:310) [15:59:41.482] Using settings from "/root/.config/transmission-daemon" (daemon.c:526) [15:59:41.482] Saved "/root/.config/transmission-daemon/settings.json" (variant.c:1217) [15:59:41.482] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:73) [15:59:41.482] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:73) [15:59:47.540] Port Forwarding Starting (port-forwarding.c:95) [15:59:48.550] Port Forwarding (NAT-PMP) readnatpmpresponseorretry succeeded (0) (natpmp.c:73) [15:59:48.550] Port Forwarding (NAT-PMP) Found public address "95.347.429.326" (natpmp.c:142) [15:59:48.550] Port Forwarding (NAT-PMP) sendnewportmappingrequest succeeded (12) (natpmp.c:73) [15:59:48.550] Port Forwarding (NAT-PMP) readnatpmpresponseorretry succeeded (0) (natpmp.c:73) [15:59:48.550] Port Forwarding (NAT-PMP) Port 51413 forwarded successfully (natpmp.c:222) [15:59:48.550] Port Forwarding Forwarded (port-forwarding.c:95) [16:00:16.830] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:248) [16:05:02.520] Transmission 2.82 (14160) started (session.c:738) [16:05:02.521] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:828) [16:05:02.521] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:1035) [16:05:02.522] RPC Server Whitelist enabled (rpc-server.c:1039) [16:05:02.522] Couldn't bind port 51413 on 0.0.0.0: Address already in use (Is another copy of Transmission already running?) (net.c:371) [16:05:02.522] UDP Couldn't bind IPv4 socket (tr-udp.c:263) [16:05:02.522] DHT Generating new id (tr-dht.c:310) [16:05:02.522] Using settings from "/root/.config/transmission-daemon" (daemon.c:526) [16:05:02.522] Saved "/root/.config/transmission-daemon/settings.json" (variant.c:1217) [16:05:02.522] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:73) [16:05:02.522] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:73) [16:05:08.580] Port Forwarding Starting (port-forwarding.c:95) [16:05:09.590] Port Forwarding (NAT-PMP) readnatpmpresponseorretry succeeded (0) (natpmp.c:73) [16:05:09.590] Port Forwarding (NAT-PMP) Found public address "95.347.429.326" (natpmp.c:142) [16:05:09.590] Port Forwarding (NAT-PMP) sendnewportmappingrequest succeeded (12) (natpmp.c:73) [16:05:09.590] Port Forwarding (NAT-PMP) readnatpmpresponseorretry succeeded (0) (natpmp.c:73) [16:05:09.590] Port Forwarding (NAT-PMP) Port 51413 forwarded successfully (natpmp.c:222) [16:05:09.590] Port Forwarding Forwarded (port-forwarding.c:95) [16:06:17.240] Saved "/root/.config/transmission-daemon/settings.json" (variant.c:1217) [16:06:17.240] DHT Not saving nodes, DHT not ready (tr-dht.c:358) [16:06:17.241] Port Forwarding Stopped (port-forwarding.c:183) [16:06:17.241] Port Forwarding (NAT-PMP) sendnewportmappingrequest succeeded (12) (natpmp.c:73) [16:06:17.241] Port Forwarding Stopping (port-forwarding.c:95) [16:06:17.280] Saved "/root/.config/transmission-daemon/settings.json" (variant.c:1217) [16:06:17.280] DHT Not saving nodes, DHT not ready (tr-dht.c:358) [16:06:17.281] Port Forwarding Stopped (port-forwarding.c:183) [16:06:17.281] Port Forwarding (NAT-PMP) sendnewportmappingrequest succeeded (12) (natpmp.c:73) [16:06:17.281] Port Forwarding Stopping (port-forwarding.c:95)
The logfile tells about: /root/.config/transmission-daemon/settings.json
cd /etc/frontview/addons/bin/TRANSMISSION ./transmission-daemon -f --logfile /var/tmp/transmission.log
give it a few seconds then ctrl-c to stop the daemon then view the log file for errors.
Thanks
Now it looks like this:
# cat /var/tmp/transmission.log [14:00:43.286] Transmission 2.82 (14160) started (session.c:738) [14:00:43.287] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:828) [14:00:43.287] RPC Server Adding address to whitelist: 10.0.0.* (rpc-server.c:828) [14:00:43.288] RPC Server Adding address to whitelist: 192.168.*.* (rpc-server.c:828) [14:00:43.288] RPC Server Serving RPC and Web requests on port 127.0.0.1:8181/transmission/ (rpc-server.c:1035) [14:00:43.288] RPC Server Whitelist enabled (rpc-server.c:1039) [14:00:43.288] RPC Server Password required (rpc-server.c:1042) [14:00:43.288] UDP Failed to set receive buffer: requested 4194304, got 1048576 (tr-udp.c:78) [14:00:43.288] UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:83) [14:00:43.288] UDP Failed to set send buffer: requested 1048576, got 524288 (tr-udp.c:89) [14:00:43.288] UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr-udp.c:94) [14:00:43.288] DHT Reusing old id (tr-dht.c:306) [14:00:43.288] DHT Bootstrapping from 114 IPv4 nodes (tr-dht.c:154) [14:00:43.288] Using settings from "/c/addons-config/Transmission" (daemon.c:526) [14:00:43.288] Saved "/c/addons-config/Transmission/settings.json" (variant.c:1217) [14:00:43.288] transmission-daemon requiring authentication (daemon.c:546) [14:00:43.289] Watching "/c/media/BitTorrent/sources/" for new .torrent files (daemon.c:564) [14:00:43.289] Using readdir to watch directory "/c/media/BitTorrent/sources/" (watch.c:163) [14:00:43.289] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:73) [14:00:43.289] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:73) [14:00:48.314] Port Forwarding Starting (port-forwarding.c:95) [14:00:48.535] Saved "/c/addons-config/Transmission/settings.json" (variant.c:1217) [14:00:48.535] DHT Not saving nodes, DHT not ready (tr-dht.c:358) [14:00:48.535] Port Forwarding Stopped (port-forwarding.c:183)
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
tarobun wrote:
Looks fine.... so what's the problem you're seeing?
Hmm, strange.
The problem is that Transmission doesn't start. And I can't access the web gui. But after I executed your commands Transmission read the settings and encrypted my password. So something has changed. But it still don't work.
It might be better to start all over. How do I get rid of Transmission completely? Will it be enough to remove the add-on from Frontview and then the rest that is left of these:
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
Looks like there are some old transmission files:
-rwxr-xr-x 1 root root 7593660 Oct 31 2011 /usr/local/bin/transmission-cli -rwxr-xr-x 1 root root 7808113 Oct 31 2011 /usr/local/bin/transmission-create
Best way to start again is to install the same add-on and then uninstall it. It should remove all related add-on files.
The /root/.config/transmission-daemon is the default location of the config files if you do not specify the TRANSMISSION_HOME env variable. You can safely delete this directory.
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
tarobun wrote:
Looks like there are some old transmission files:
-rwxr-xr-x 1 root root 7593660 Oct 31 2011 /usr/local/bin/transmission-cli -rwxr-xr-x 1 root root 7808113 Oct 31 2011 /usr/local/bin/transmission-create
Best way to start again is to install the same add-on and then uninstall it. It should remove all related add-on files.
The /root/.config/transmission-daemon is the default location of the config files if you do not specify the TRANSMISSION_HOME env variable. You can safely delete this directory.
I actually did install and uninstall super-poussin' and WhoCares' Transmission versions before installing your version. But now I went through that procedure again. Uninstalled yours, installed WhoCares' version and uninstalled it, installed super-poussin' and uninstalled. But these files remains:
Re: New Transmission 2.82 add-on for ReadyNAS Duo/NV+ (sparc
Update. I deleted the files listed above (also /c/addons-config/Transmission) and after that the installation of tarobun's Transmission went just fine!
