Transmission unMenu package


Recommended Posts

thanks Joe

killall transmission-daemon

stopped transmission and fixed the "button" it can now stop and start

 

when checking the .json file in the new location the parameters do not seem to change

this was a fresh install. Editing the .json file in a texteditor didn't seem to change it either.

 

I will try uninstalling next

Link to comment
  • Replies 703
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

It appears that installing over an existing install is what is causing the problems.

 

Unfortunately I can't test that situation... well I could but it would be on my production machine, which I have not updated as of yet, been to busy...

 

If I get some free time this weekend I will see what I can do as far as pulling some stuff over from my production machine onto my test machine and then installing over the top of it from there.

 

 

EDIT: I have updated the first post with instructions to use or you can try the button I just put together.  I have not tested the button as I am not near my server right now.

Link to comment

It appears that installing over an existing install is what is causing the problems.

I did a fresh install and had the problems described above.

 

Tried installing the button

it appears with the text

sh:-c: line 1: syntax error: unexpected end of file

 

 

manually deleted all transmission files. updated unmenu and reinstalled.

 

now it seems transmission wont start

 

 

 

/boot/custom/transmission/transctl start
+++ /boot/custom/transmission/transctl start
/boot/unmenu/42-unmenu_user_script_start_transmission: line 7: /boot/custom/transmission/transctl: No such file or directory

ok after a reboot transmission started up, seems to act the same as before, will test some more

 

after some playing around i managed to get things working.

strange there where 2 folders in custom on the flash

\custom\transmission\transmission.conf    and

\custom\transmission\transmission_conf

 

the transmission.conf  folder was having a wrong .json file and also the folders "blocklist" "resume" and "torrents" like in the actual install directory on the cache drive.

 

I don't know if its normal or could be useful to find out what is going wrong, it just seemed odd to me.

 

copied the right .json file over the other .json files both on the cache drive and flash drive.

 

 

 

Link to comment

i had all similar problems. yesterday....with the new package what i find worked is if you want to change the values or settings it will only change if you change the setting to install transmission in a new folder...otherwise the new variables won't work. So everytime i want to change the port I have to change the install location to something new for it to work.

Link to comment

did a clean install on my 2nd usbdrive just copied over some .cfg files so the server didn't need to be set-up again.

installed unmenu and then the transmission package.

exactly the same behavior as before

the install directory \cache\.torrents\transmission has non of the settings it was installed with

{
   "alt-speed-down": 50, 
   "alt-speed-enabled": false, 
   "alt-speed-time-begin": 540, 
   "alt-speed-time-day": 127, 
   "alt-speed-time-enabled": false, 
   "alt-speed-time-end": 1020, 
   "alt-speed-up": 50, 
   "bind-address-ipv4": "0.0.0.0", 
   "bind-address-ipv6": "::", 
   "blocklist-enabled": false, 
   "dht-enabled": true, 
   "download-dir": "/root/Downloads", 
   "encryption": 1, 
   "incomplete-dir": "/root/Downloads", 
   "incomplete-dir-enabled": false, 
   "lazy-bitfield-enabled": true, 
   "lpd-enabled": false, 
   "message-level": 2, 
   "open-file-limit": 32, 
   "peer-limit-global": 240, 
   "peer-limit-per-torrent": 60, 
   "peer-port": 51413, 
   "peer-port-random-high": 65535, 
   "peer-port-random-low": 49152, 
   "peer-port-random-on-start": false, 
   "peer-socket-tos": 0, 
   "pex-enabled": true, 
   "port-forwarding-enabled": true, 
   "preallocation": 1, 
   "proxy": "", 
   "proxy-auth-enabled": false, 
   "proxy-auth-password": "", 
   "proxy-auth-username": "", 
   "proxy-enabled": false, 
   "proxy-port": 80, 
   "proxy-type": 0, 
   "ratio-limit": 2.0000, 
   "ratio-limit-enabled": false, 
   "rename-partial-files": true, 
   "rpc-authentication-required": false, 
   "rpc-bind-address": "0.0.0.0", 
   "rpc-enabled": true, 
   "rpc-password": "{e2994d2f66718ae16c7e0f35ff4509656d8db9aezaAet3N0", 
   "rpc-port": 9091, 
   "rpc-username": "", 
   "rpc-whitelist": "127.0.0.1", 
   "rpc-whitelist-enabled": true, 
   "script-torrent-done-enabled": false, 
   "script-torrent-done-filename": "", 
   "speed-limit-down": 100, 
   "speed-limit-down-enabled": false, 
   "speed-limit-up": 100, 
   "speed-limit-up-enabled": false, 
   "start-added-torrents": true, 
   "trash-original-torrent-files": false, 
   "umask": 18, 
   "upload-slots-per-torrent": 14
}

 

here is the one from \flash\custom\transmission\transmission_conf wich is correct

 

{
"alt-speed-down": 50,
"alt-speed-enabled": false,
"alt-speed-time-begin": 540,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": false,
"alt-speed-time-end": 1020,
"alt-speed-up": 50,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": false,
"dht-enabled": true,
"download-dir": "/mnt/cache/.torrents/download",
"encryption": 1,
"incomplete-dir": "/mnt/cache/.torrents/download",
"incomplete-dir-enabled": false,
"watch-dir": "/mnt/cache/.torrents/watch",
"watch-dir-enabled": false,
"lazy-bitfield-enabled": true,
"lpd-enabled": true,
"message-level": 2,
"open-file-limit": 32,
"peer-limit-global": 1000,
"peer-limit-per-torrent": 50,
"peer-port": 51413,
"peer-port-random-high": 65535,
"peer-port-random-low": 49152,
"peer-port-random-on-start": false,
"peer-socket-tos": 0,
"pex-enabled": true,
"port-forwarding-enabled": true,
"preallocation": 1,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"ratio-limit": 2.000,
"ration-limit-enabled": false,
"rename-partial-files": true,
"rpc-authentication-required": false,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "",
"rpc-port": 9091,
"rpc-username": "",
"rpc-whitelist": "192.168.1.*",
"rpc-whitelist-enabled": true,
"script-torrent-done-enabled": false,
"script-torrent-done-filename": "",
"speed-limit-down": 100,
"speed-limit-down-enabled": false,
"speed-limit-up": 100,
"speed-limit-up-enabled": false,
"start-added-torrents": true,
"trash-original-torrent-files": false,
"umask": 18,
"upload-slots-per-torrent": 15
}

 

somehow the settings are not transferred

the settings were already made before downloading and installing transmission

 

the settings in \flash\custom\transmission\transmission.conf

are wrong like the ones on the cache drive

Link to comment

copied and renamed settings.local over all existing .json and json.default files and settings were used on restart.

for now this is the only way I can  get the settings to work.

 

 

one more thing maybe someone has some insight on this

Im trying to use transmission remote gui

getting "refused connection"

 

is there any specific setting to make it work? web interface does work

 

in connection settings tried using //ip/  and //server_name/

 

with and without password and username

 

here are the setting fron the .json file

{
   "alt-speed-down": 50, 
   "alt-speed-enabled": false, 
   "alt-speed-time-begin": 540, 
   "alt-speed-time-day": 127, 
   "alt-speed-time-enabled": false, 
   "alt-speed-time-end": 1020, 
   "alt-speed-up": 50, 
   "bind-address-ipv4": "0.0.0.0", 
   "bind-address-ipv6": "::", 
   "blocklist-enabled": false, 
   "dht-enabled": true, 
   "download-dir": "/mnt/cache/.torrents/download", 
   "encryption": 1, 
   "incomplete-dir": "/mnt/cache/.torrents/download", 
   "incomplete-dir-enabled": false, 
   "lazy-bitfield-enabled": true, 
   "lpd-enabled": true, 
   "message-level": 2, 
   "open-file-limit": 32, 
   "peer-limit-global": 1000, 
   "peer-limit-per-torrent": 50, 
   "peer-port": 51413, 
   "peer-port-random-high": 65535, 
   "peer-port-random-low": 49152, 
   "peer-port-random-on-start": false, 
   "peer-socket-tos": 0, 
   "pex-enabled": true, 
   "port-forwarding-enabled": true, 
   "preallocation": 1, 
   "proxy": "", 
   "proxy-auth-enabled": false, 
   "proxy-auth-password": "", 
   "proxy-auth-username": "", 
   "proxy-enabled": false, 
   "proxy-port": 80, 
   "proxy-type": 0, 
   "ratio-limit": 2.0000, 
   "ratio-limit-enabled": false, 
   "ration-limit-enabled": false, 
   "rename-partial-files": true, 
   "rpc-authentication-required": true, 
   "rpc-bind-address": "0.0.0.0", 
   "rpc-enabled": true, 
   "rpc-password": "{0dd20962462bd9291aae8e633774ddc2c994eejM82VqVIR", 
   "rpc-port": 9091, 
   "rpc-username": "admin", 
   "rpc-whitelist": "192.168.1.*", 
   "rpc-whitelist-enabled": true, 
   "script-torrent-done-enabled": false, 
   "script-torrent-done-filename": "", 
   "speed-limit-down": 100, 
   "speed-limit-down-enabled": false, 
   "speed-limit-up": 100, 
   "speed-limit-up-enabled": false, 
   "start-added-torrents": true, 
   "trash-original-torrent-files": false, 
   "umask": 18, 
   "upload-slots-per-torrent": 15, 
   "watch-dir": "/mnt/cache/.torrents/watch", 
   "watch-dir-enabled": false
}

maybe i'm missing some setting or use a wrong path  ???

 

thanks for the hard work on this project really apreciated!

 

 

Link to comment

no wories m8 take the time you need

graduation is a lot more important :D

 

I found what i was doing wrong with transmission -remote gui

I just needed to fill in the server (or ip)  name  without "/"

 

 

 

 

UPDATE

working with Transmission remote is really nice. Have set it to default program for opening torents  and it works nearly like a local torrent client.

highly recommended!

Link to comment

Has anyone else noticed that when you change the path for the data files for finished downloads in Transmission Remote GUI, Transmission crashes and usually needs a complete server reboot to bring back up? It doesn't seem to happen with smaller files, just multi-GB ones...

Link to comment

Has anyone else noticed that when you change the path for the data files for finished downloads in Transmission Remote GUI, Transmission crashes and usually needs a complete server reboot to bring back up? It doesn't seem to happen with smaller files, just multi-GB ones...

 

I have never noticed this, but then I don't move my files after download.  I keep the originals were they are and how they are and then copy the things I need to there proper location.

 

 

AND UPDATE FOR ANYONE FOLLOWING:

I managed to find a little time to look at the issue people are having and may have found a few things.  I HAVE NOT had time to test anything but should be able to Friday night and Saturday once I make the changes I think need to be made.  I will probably put up the new .conf file saturday night for people to test and then for JoeL to include in unMenu.

Link to comment

Hi,

 

I not sure if this has been mentioned, the ratio-limit-enabled is spelled incorrectly in the transmission auto_install, settings.json and settings.local.

 

It is named:

 

"ration-limit-enabled": true,

 

is should be

 

"ratio-limit-enabled": true

Link to comment

Hi,

 

I not sure if this has been mentioned, the ratio-limit-enabled is spelled incorrectly in the transmission auto_install, settings.json and settings.local.

 

It is named:

 

"ration-limit-enabled": true,

 

is should be

 

"ratio-limit-enabled": true

 

Thanks for pointing that out.  I have changed it in my version and should have something up later today... I got "side tracked" last night so did not get a chance to make my last reviews of the updated package.

Link to comment

OK, so for anyone following there is an updated package attached to the first post.

 

I have tested this, though not on my production machine as of yet.  Just not enough time on my hands... hence me posting this at almost 1:00am EST... fun fun

 

Anyway, my suggestion when updating to this version is that if you have a current install that is working and you want to save your current torrents listings and resume states is to make copies of those folders before updating.  You can find those folders in /boot/custom/transmission/transmission.conf/ or in the install location you specified from the previous package.

 

After you have backups of those folders I suggest deleting the folder that the resume and torrents folders were in and starting fresh.  I found a couple of miss typed things in the previous package that caused the bugs people were seeing.  Leaving what is in place now, could cause odd things to happen and I can't code for everyones case... so start from a clean slate if at all possible... PLEASE.

 

If you all find anything else let me know.

 

Oh, and I am also looking into updating the version of Transmission that is used in the package.  I just have not had the time to try as of yet and probably wont for a little while, but figured I would let everyone know.

Link to comment

Thanks for the work prostuff.

 

The updates do work for changing the rcp port. The variables and the link on the package page changes as well where it didn't before.

 

I'm still having trouble logging on to the webpage. (http://tower:9091/transmission/web)

Still getting

Unable to connect

Firefox can't establish a connection to the server at ......

 

I've tried closing the firewall. An Internet Explorer page with windows 7 diagnosis the problem as transmission not responding.

 

Thanks Josh

Link to comment

Is the name of the server you are trying to connect to still called tower?  If not then the hostname is not being found correctly.

 

My suggest would be to try and connect to

http://IP_ADDRESS_HERE:PORT_NUMBER

 

if you can also do a:

ps -ef

from the command line to see if it is running that would be great.

Link to comment

Thanks for the work prostuff.

 

The updates do work for changing the rcp port. The variables and the link on the package page changes as well where it didn't before.

 

I'm still having trouble logging on to the webpage. (http://tower:9091/transmission/web)

Still getting

Unable to connect

Firefox can't establish a connection to the server at ......

 

I've tried closing the firewall. An Internet Explorer page with windows 7 diagnosis the problem as transmission not responding.

 

Thanks Josh

i had such trouble in the beginning because the right settings were not imported and saved in the right location.

have you tried the updates?

Link to comment

Thanks for the great work guys!

 

ps -ef showed that it wasn't running.

 

I made the mistake of putting one of the ratios as .1 instead of 0.1 so it wouldn't start up.

 

Thanks Josh

 

Glad to here that you got it working!! and thanks for letting me know what the problem was.  I might be able to handle a case like what you did... but that would turn into a lot of extra stuff that I am not sure I want to add to the package.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.