transmission 2.84_1

[TIQA]

after updating transmission fom 2.82 to 2.84_1 it wont start anymore. anyone have encountered the same problems?

 

[kloon]

I encountered the same problem and I decide not to troubleshoot it since I don't have the knowledge. I choose to reinstall and everything work again, it just that my magnet link no longer work now and I am finding the reason.

 

[hervon]

Also had the same problem after upgrade to 9.3. The link bellow helped be a bit but I also had to redo the Transmission plugin settings too and some more things I can't remember.

https://forums.freenas.org/index.ph...-maraschino-htpc-mylar-ll-gamez.16200/page-46

 

[Basil Hendroff]

So I’m not the only one experiencing problems with the latest Transmission update. I’ve narrowed it down to a permissions issue, but don’t have sufficient Linux knowledge to provide a solution.

First, noting I am on the latest FreeNAS version with all pending package updates applied:

FreeNAS-9.3-STABLE-201412240734

I install Transmission 2.84_1 and note the following when I click on the plugin:

The default download directory is /usr/pbi/transmission-amd64/etc/transmission/home/Downloads.

When I check the ownership along the path, I note that ownership changes around transmission/home. I also note that the Downloads directory does not exist.

drwxr-xr-x 3 root wheel 3 Dec 22 09:09 transmission

drwxr-x--- 6 transmission transmission 7 Dec 26 23:52 home

Note the user and group transmission in the previous line. Checking the UID and GID I get UID/GID as 921. However, when I check accounts, there isn’t a user or group defined for user transmission. Curious.

After starting the transmission service and starting a download, I note that the Downloads directory gets created and the owner is user transmission.

drwxr-xr-x 3 transmission transmission 3 Dec 27 00:16 Downloads

I note that the download successfully progresses.


The issue at this point is that the download is in the jail, whereas I want it outside the jail. These are my next steps:

1. I stop the Transmission service.
2. I set up a storage mount point mapping /media/downloads in the jail to an external point.
3. I check the ownership of the /media/downloads directory:
   

drwxr-xr-x 2 root wheel 2 Dec 27 00:48 downloads

Note the owner is root and not transmission.

1. I click on the Transmission plugin and set the download directory to /media/downloads
2. I start the Transmission service and attempt a download. The download fails with ‘Permission denied’.

So it appears there’s an ownership and permission issue. As long as the directory owner is the phantom transmission user, the download is likely to be successful. Anything else and the download will fail.


I’ve tried creating a user transmission with UID 921 and adding it to the wheel group, but with no success. The download still fails.


Over to the greater community to suggest a way forward.

 

[Joshua Parker Ruehlig]

the transmission user not existing is not a bug, users/groups in the jail are not shared with the host. You can create them on the host if you like but since the service runs in the jail it only knows about the group mappings in the jail.

Either change the owner of the dataset you mounted, loosen the permission levels
or (more advanced options, need CLI) change the user transmission runs as, add the transmission user to the group for that dataset in the jail

 

[Basil Hendroff]

Joshua - you’ve hit the nail on the head!

Last pieces of the puzzle for other noobs like me.

In my case, the missing piece was to add user transmission in the jail to the wheel group using the following command:

pw usermod transmission -G wheel

I then stopped and restarted the plugin and jail and, voila. the Transmission plugin burst into life.

Thanks Joshua!

 

[Joshua Parker Ruehlig]

no problem. glad it's working for you.

 

[kloon]

Not sure what it happen. If I upload the torrent file, then it will start download. However, when I use magnet or paste the torrent link, it just won't work. And all torrent files gone if I restart the plugin.

 

[Joshua Parker Ruehlig]

Not sure what it happen. If I upload the torrent file, then it will start download. However, when I use magnet or paste the torrent link, it just won't work. And all torrent files gone if I restart the plugin.

transmission forum might know more about the difference between those two, and how to get relevant logs from transmission.
id make sure transmission has read/write on any directories it uses as well, but it sounds like you already went through that.

 

[TIQA]

...this is.......interesting...i changed download path, shutdown nas and few days later started it again and now transmission works even if webgui shows as off....wtf?

 

[Scharbag]

2.82 --> 2.84 update failed for me as well. I deleted the plugin and reinstalled and it seems to be working again. I like that 2.84 has the ability to set the permissions to 777 as that has caused me some hell in the past.

Cheers,

 

[kloon]

...this is.......interesting...i changed download path, shutdown nas and few days later started it again and now transmission works even if webgui shows as off....wtf?

Wait...You said you shutdown the NAS instead of the plugin?

 

[mccann73]

Again, 2.82 --> 2.84 update failed for me as well, had to delete and reinstall the plugin. I like that the "Incomplete Download" option has been added, however i used the "Configuration Directory" option and would still like to use it, what do i need to edit to set the configuration folder to a different location, i would have hoped it stayed! :)

Cheers

 

[Joshua Parker Ruehlig]

Again, 2.82 --> 2.84 update failed for me as well, had to delete and reinstall the plugin. I like that the "Incomplete Download" option has been added, however i used the "Configuration Directory" option and would still like to use it, what do i need to edit to set the configuration folder to a different location, i would have hoped it stayed! :)

Cheers

check /usr/local/etc/rc.d/transmission
there is a variable you can set in /etc/rc.conf to set the config directory.
but the plugin expects a certain place to find the setrings.json so you may have to make a symlink.

why did you want to move your config directory?
if this is a really wanted feature I can add it back next release, it just makes the plugin a bit more complex and I thought not many people used this cause none of the other plugins have the option.

EDIT
I do hate how the directory defaults to under the PBI directory which causes all sorts of issues with upgrades...

 

[mccann73]

Hi Joshua

Thanks with that info, will have a play around with rc.conf, I like to keep the settings separate from the jail in case there are any issues, just delete jail and start again, I keep the config folder in the same location as my torrents, easier to maintain as I use some of the extra settings not available in the transmission config screen. It would be nice to have the setting back, but if no one uses it then it not really worth it, don’t mind manually changing setting for my setup.

Cheers

 

[Joshua Parker Ruehlig]

Hi Joshua

Thanks with that info, will have a play around with rc.conf, I like to keep the settings separate from the jail in case there are any issues, just delete jail and start again, I keep the config folder in the same location as my torrents, easier to maintain as I use some of the extra settings not available in the transmission config screen. It would be nice to have the setting back, but if no one uses it then it not really worth it, don’t mind manually changing setting for my setup.

Cheers

That's what I figured, and just having the config folder not under /usr/pbi/ would have saved alot of people headaches with this last update.

Maybe you can try the below which will set a different config directory, and link your config. Replace the instances of /PATH with the mountpoint you want

Code:

service transmission onestop
sysrc 'transmission_conf_dir=/PATH'
mv /usr/pbi/transmission-amd64/etc/transmission/home /PATH
mkdir /usr/pbi/transmission-amd64/etc/transmission/home
ln -s /PATH/settings.json /usr/pbi/transmission-amd64/etc/transmission/home
service transmission start

 

[kloon]

For some weird reason, the magnet link work again after I restart the plugin few times.

And I do change the watch-dir to another directory, and it also reflect in the setting.json. However, when I ssh into the jails, the torrent still save in the default watch-dir, which is /usr/pbi/transmission-amd64/etc/transmission/home/torrents/

This is my setting

{
"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,
"blocklist-url": "",
"cache-size-mb": 4,
"dht-enabled": true,
"download-dir": "/media",
"download-queue-enabled": true,
"download-queue-size": 5,
"encryption": 0,
"idle-seeding-limit": 30,
"idle-seeding-limit-enabled": false,
"incomplete-dir": "/media/Incomplete",
"incomplete-dir-enabled": true,
"lpd-enabled": false,
"message-level": 2,
"peer-congestion-algorithm": "",
"peer-id-ttl-hours": 6,
"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": "default",
"pex-enabled": true,
"pidfile": "/var/run/transmission/daemon.pid",
"port-forwarding-enabled": true,
"preallocation": 1,
"prefetch-enabled": 1,
"queue-stalled-enabled": true,
"queue-stalled-minutes": 30,
"ratio-limit": 5,
"ratio-limit-enabled": false,
"rename-partial-files": true,
"rpc-authentication-required": true,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "",
"rpc-port": 9091,
"rpc-url": "/transmission/",
"rpc-username": "",
"rpc-whitelist": "",
"rpc-whitelist-enabled": false,
"scrape-paused-torrents-enabled": true,
"script-torrent-done-enabled": false,
"script-torrent-done-filename": "",
"seed-queue-enabled": false,
"seed-queue-size": 10,
"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": 2,
"upload-slots-per-torrent": 14,
"utp-enabled": false,
"watch-dir": "/media/torrents",
"watch-dir-enabled": true
}

 

[Yatti420]

I just reconfigured my main computer.. I did have issues upgrading transmission from 2.82 to 2.84.. I just reinstalled it cleanly and reconfigured it.. Works fine now as far as I can tell..

 

[Joshua Parker Ruehlig]

For some weird reason, the magnet link work again after I restart the plugin few times.

And I do change the watch-dir to another directory, and it also reflect in the setting.json. However, when I ssh into the jails, the torrent still save in the default watch-dir, which is /usr/pbi/transmission-amd64/etc/transmission/home/torrents/

This is my setting

.torrent files are supposed to be in the transmission/home/torrents folder.

your not fully understanding the watch directory and the torrent directory. the watch directory is a folder you drop .torrent files for transmission to add. the transmission/home/torrent directory holds all active torrents be saving a copy of the .torrent file in there, whether it was added using a .torrent file or magnet-link.

 

[kloon]

.torrent files are supposed to be in the transmission/home/torrents folder.

your not fully understanding the watch directory and the torrent directory. the watch directory is a folder you drop .torrent files for transmission to add. the transmission/home/torrent directory holds all active torrents be saving a copy of the .torrent file in there, whether it was added using a .torrent file or magnet-link.

Thank you Joshua. I get the idea now. Will try to monitor it since the transmission not working earlier. When I look into the transmission/home/torrents folder, all torrents become torrent.added instead of .torrent.

But everything is working fine again now.