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
And finally, ps ax | grep transmission seems to suggest that there are indeed two transmission related processes running
Ideas?
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
This is the contents of the rc.conf file inside the jailWill not 'status' transmission because transmission_enable is NO.
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 relatedtransmission_enable="YES"
transmission_conf_dir="/usr/pbi/transmission-amd64/etc/transmission/home"
transmission_flags="-e /var/log/transmission "
The in-jail /var/log/messages (/var/log/transmission is never created) contains no obviously fatal errorsOct 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
Attempting to run the transmission daemon by hand gives me a dynamic linker errorOct 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)
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?