Transmission plugin 2.77_1 does not work on FreeNAS-9.1.1

[Johan]

I've installed Transmission (transmission-2.77_1-amd64) through the FreeNAS (FreeNAS-9.1.1-RELEASE-x64 (a752d35)) webgui without changing the configuration. After turning it on in the FreeNAS webgui, there is still no one responding at the transmission UI port (left at the default 9091).

Following the instructions in a previous forum thread, I tried cd-ing into /usr/pbi/transmission-amd64/etc/rc.d in the jail and ran ./transmission status which gave me the output

Will not 'status' transmission because transmission_enable is NO.

This is the contents of the rc.conf file inside the jail

transmission_enable="YES"
transmission_conf_dir="/usr/pbi/transmission-amd64/etc/transmission/home"
transmission_flags="-e /var/log/transmission "

Forcing the start says that transmission is not running. At this point I'm a bit out of my depth wrt to FreeBSD jails, so my apologies if my remaining attempts are obviously useless, but... The main (non-jailed) /var/log/messages contains this that I suspect is related

Oct 9 10:33:58 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v
Oct 9 10:35:04 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v
Oct 9 10:35:05 freenas last message repeated 3 times
Oct 9 10:45:51 freenas last message repeated 7 times
Oct 9 10:49:53 freenas last message repeated 3 times
Oct 9 11:06:15 freenas last message repeated 6 times
Oct 9 11:07:24 freenas last message repeated 3 times
Oct 9 11:22:10 freenas root: ./transmission: WARNING: run_rc_command: cannot run /usr/pbi/transmission-amd64/bin/transmission-daemon
Oct 9 11:35:35 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v

The in-jail /var/log/messages (/var/log/transmission is never created) contains no obviously fatal errors

Oct 9 11:06:17 bit_1 transmission-daemon[19613]: UDP Failed to set receive buffer: No buffer space available (tr-udp.c:58)
Oct 9 11:06:17 bit_1 transmission-daemon[19613]: UDP Failed to set receive buffer: requested 4194304, got 42080 (tr-udp.c:77)
Oct 9 11:07:10 bit_1 transmission-daemon[19815]: UDP Failed to set receive buffer: No buffer space available (tr-udp.c:58)
Oct 9 11:07:10 bit_1 transmission-daemon[19815]: UDP Failed to set receive buffer: requested 4194304, got 42080 (tr-udp.c:77)
Oct 9 11:08:01 bit_1 transmission-daemon[19815]: DHT dht.transmissionbt.com:6881: hostname nor servname provided, or not known (tr-dht.c:125)
Oct 9 11:09:27 bit_1 transmission-daemon[19815]: DHT dht.transmissionbt.com:6881: hostname nor servname provided, or not known (tr-dht.c:125)

Attempting to run the transmission daemon by hand gives me a dynamic linker error

Shared object "libevent-2.0.so.6" not found, required by "transmission-daemon

And finally, ps ax | grep transmission seems to suggest that there are indeed two transmission related processes running

16501 ?? IJ 0:01.04 /usr/pbi/transmission-amd64/bin/python /usr/pbi/transmission-amd64/control.py start 19
19815 ?? SsJ 0:00.17 /usr/local/bin/transmission-daemon -g /usr/pbi/transmission-amd64/etc/transmission/hom

Ideas?

 

[ljw1]

I am having the exact same problem. Transmission status is returning it is not running and in the process list there is transmission listed.

 

[Whattteva]

Maybe the error is because you have multiple processes running.
Try doing a kill -9 on those PID's.

 

[Johan]

Maybe the error is because you have multiple processes running.
Try doing a kill -9 on those PID's.

Still WARNING: run_rc_command: cannot run /usr/pbi/transmission-amd64/bin/transmission-daemon

 

[joeschmuck]

Out of curiosity, how many jails do you have running and what order are they in if there are more than one. Type 'jls' to get the list. And if there is a jail after the problem child, is it running properly?

 

[Johan]

No, just this one (which jls confirms):

[root@freenas] /# jls
JID IP Address Hostname Path
1 - bit_1 /mnt/space/jails_2/bit_1
[root@freenas] /#

 

[joeschmuck]

Too bad. I was hoping it was something else that I'm looking into. Sorry but I won't be able to give any help here since I don't use transmission.

But this should tell you if php fpm is running. If it's not then that is likely the problem.

Code:

jexec jailname ps axuww

Should this be the problem I would first delete the plugin and install it again. If you have the same problem I would submit a ticket for the problem ensuring you note the php fpm is not running.

 

[Johan]

After reinstalling the plugin the Transmission webgui popped up, but at another IP address. I wasn't expecting that and so didn't look for that before, so I don't know if that was the problem the whole time.

 

[ljw1]

There were a number of problems with my install. Firstly the attached storage did not have the right permission for the transmission user (not mentioned anywhere that I could find). The second issue is that any checking is done doing the root account which does have write permission which then attempts to start two instances of the transmission daemon, again not mentioned in any instructions I could find.

I am very grateful for the plugins however the complete lack of instructions is quite frustrating for users.