Transmission won't start

[greenSeeker]

I'm trying to get the transmission plugin set up. I've configured the jail and am now trying to start the service, but after a few minutes it says there was an error.

Is there any logging where I can get more detail?

 

[dlavigne]

more /var/log/messages from within the jail. Also, service start transmission should give an error if it is failing. (though it may be called something else, check /usr/local/etc/rc.d to see if there is anything appended to transmission)

 

[greenSeeker]

# jexec 1 tcsh
# service transmission start
Cannot 'start' transmission. Set transmission_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'.

# vi /etc/rc.conf
Added 'transmission_enable="YES"'.
Saved and quit.

# service transmission start
usage: chown [-fhvx] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhvx] [-R [-H | -L | -P]] :group file ...
Starting transmission.

# service transmission stop
Stopping transmission.


Checked /var/log/messages:
Jan 10 18:13:24 transmission_1 transmission-daemon[91699]: UDP Failed to set receive buffer: No buffer space available (tr-udp.c:59)
Jan 10 18:13:24 transmission_1 transmission-daemon[91699]: UDP Failed to set receive buffer: requested 4194304, got 42080 (tr-udp.c:78)
Jan 10 18:15:41 transmission_1 transmission-daemon[91872]: UDP Failed to set receive buffer: No buffer space available (tr-udp.c:59)
Jan 10 18:15:41 transmission_1 transmission-daemon[91872]: UDP Failed to set receive buffer: requested 4194304, got 42080 (tr-udp.c:78)


Found this thread about these errors:
https://forums.freenas.org/index.ph...iled-to-set-receive-buffer-please-help.15203/


But these values are already set as advised:
# sysctl kern.ipc.maxsockbuf
kern.ipc.maxsockbuf: 5242880

# sysctl net.inet.udp.recvspace
net.inet.udp.recvspace: 4194304


Starting the service from the web gui still says "some error ocurred" but there are no updates to /var/log/messages inside the jail or out.

 

[SweetAndLow]

Cannot 'start' transmission. Set transmission_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'.

Did you do this?

 

[greenSeeker]

Did you do this?

Yup

# jexec 1 tcsh
# service transmission start
Cannot 'start' transmission. Set transmission_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'.

# vi /etc/rc.conf
Added 'transmission_enable="YES"'.
Saved and quit.

 

[Joshua Parker Ruehlig]

the transmission service works fine inside the jail. Your FreeNAS WebUI can't connect to the plugin's middleware layer that start+enables / stops/disables the plugin.
From the jail can you ping your computer?

 

[flashpoint]

This guy was having the same issue, couple of posts down:

https://forums.freenas.org/index.ph...no-longer-able-to-access-web-interface.40399/

How he fixed it:

https://forums.freenas.org/index.ph...le-to-access-web-interface.40399/#post-255062

 

[greenSeeker]

the transmission service works fine inside the jail. Your FreeNAS WebUI can't connect to the plugin's middleware layer that start+enables / stops/disables the plugin.
From the jail can you ping your computer?

No, I cannot:

# jexec 1 tcsh
# ping 192.168.1.10
ping: sendto: Host is down
ping: sendto: Host is down​

Routing and NIC look ok:

# netstat -r
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
localhost link#1 UH 0 84 lo0
192.168.1.0 link#2 U 0 373 epair0
transmission_1 link#2 UHS 0 0 lo0​

# ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:61:d2:00:08:0b
inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active​

Actually, I can't even ping the NAS from within the jail:

# ping 192.168.1.50
PING 192.168.1.50 (192.168.1.50): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down​

I'm assuming there's some configuration missing to allow the jail to communicate with the outside

 

[SweetAndLow]

Do you have a default gateway set for the jail configuration? I suspect that might fix the issue. This isn't required, only when something in your router/dhcp server is messed up.

 

[greenSeeker]

I had a static config earlier with the gateway configured, but I had switched to DHCP.
It looked correct, but I switched it back to static anyway. This didn't make a difference.
I decided to reboot the whole system at this point, and everything is working fine. I even went back to DHCP and it keeps working, so I'm not sure what the reboot cleared up.

After this, I was able to locate and edit settings.json to allow remote connections to transmission.
This seems like a lot of manual work for such a simple function.

 

[Joshua Parker Ruehlig]

I had a static config earlier with the gateway configured, but I had switched to DHCP.
It looked correct, but I switched it back to static anyway. This didn't make a difference.
I decided to reboot the whole system at this point, and everything is working fine. I even went back to DHCP and it keeps working, so I'm not sure what the reboot cleared up.

After this, I was able to locate and edit settings.json to allow remote connections to transmission.
This seems like a lot of manual work for such a simple function.

what did you need to edit in settings.json?
Most common settings are available in transmission's webui or the transmission settings menu in the left panel of the freenas webui

 

[greenSeeker]

what did you need to edit in settings.json?
Most common settings are available in transmission's webui or the transmission settings menu in the left panel of the freenas webui

I disabled rpc-whitelist-enabled so I could connect to the transmission web interface. Otherwise it only allows connects from localhost.
Looks like I could have edited the whitelist itself from the FreeNAS GUI.

 

[Joshua Parker Ruehlig]

I disabled rpc-whitelist-enabled so I could connect to the transmission web interface. Otherwise it only allows connects from localhost.
Looks like I could have edited the whitelist itself from the FreeNAS GUI.

If you place anything in the whitelist field in freenas it enabled the whitelist. Editing the settings.json directly isn't the best because that setting will be overwritten if you don't fix it in the FreeNAS interface.

 

[greenSeeker]

If you place anything in the whitelist field in freenas it enabled the whitelist. Editing the settings.json directly isn't the best because that setting will be overwritten if you don't fix it in the FreeNAS interface.

Out of the box the whitelist was empty but enabled so all access to the web gui was blocked.

I don't think Plugins > Transmission was available from the sidebar until I logged out and back in, or maybe I just overlooked it. I had been clicking Plugins on the topbar and trying to configure from there, as well as from the Jails menu.

Online search led me to Transmission documentation, and I ended up editing settings.json myself as a result.

I've configured properly from Plugins > Transmission now, so I should be good to go.

 

[Joshua Parker Ruehlig]

Out of the box the whitelist was empty but enabled so all access to the web gui was blocked.

I don't think Plugins > Transmission was available from the sidebar until I logged out and back in, or maybe I just overlooked it. I had been clicking Plugins on the topbar and trying to configure from there, as well as from the Jails menu.

Online search led me to Transmission documentation, and I ended up editing settings.json myself as a result.

I've configured properly from Plugins > Transmission now, so I should be good to go.

Yeah that menu is fininky. Glad you got it working