Transmission plugin - getting Middleware Error on installation

[Happybug]

Dear All

I am very new to FreeNAS and Home Servers (just started playing around 1 week ago). I have installed version 9.2.0 on a laptop qith 3GB of RAM and using UFS (as the guidance notes say I don't have enough RAM for ZFS). I keep getting an error message when I try to install the Transmission plug in. I have attached the error report from the Console Log. I would be very grateful if anyone could point me in the right direction.

Feb 18 20:33:48 HomeNAS warden: Building new Jail... Please wait...
Feb 18 20:33:48 HomeNAS warden: Installing world...
Feb 18 20:35:38 HomeNAS warden: Done
Feb 18 20:35:39 HomeNAS warden: Success!
Feb 18 20:35:39 HomeNAS warden: Jail created at /mnt/NASHDD1/jails/transmission_1
Feb 18 20:35:40 HomeNAS kernel: bridge0: Ethernet address: 02:e0:fb:8e:f8:00
Feb 18 20:35:40 HomeNAS kernel: re0: promiscuous mode enabled
Feb 18 20:35:40 HomeNAS kernel: bridge0: link state changed to UP
Feb 18 20:35:40 HomeNAS kernel: epair0a: Ethernet address: 02:80:04:00:0c:0a
Feb 18 20:35:40 HomeNAS kernel: epair0b: Ethernet address: 02:80:04:00:0d:0b
Feb 18 20:35:40 HomeNAS kernel: epair0a: link state changed to UP
Feb 18 20:35:40 HomeNAS kernel: epair0b: link state changed to UP
Feb 18 20:35:40 HomeNAS kernel: re0: link state changed to DOWN
Feb 18 20:35:40 HomeNAS kernel: epair0a: promiscuous mode enabled
Feb 18 20:35:41 HomeNAS ntpd[4763]: bind() fd 27, family AF_INET6, port 123, scope 12, addr fe80::80:4ff:fe00:c0a, mcast=0 flags=0x11 fails: Can't assign requested address
Feb 18 20:35:41 HomeNAS ntpd[4763]: unable to create socket on epair0a (6) for fe80::80:4ff:fe00:c0a#123
Feb 18 20:35:41 HomeNAS manage.py: [middleware.exceptions:38] [MiddlewareError: The command /usr/sbin/jexec 1 /usr/local/sbin/pbi_add -f --no-checksig /.plugins/transmission-2.77_1-i386.pbi failed: ""]
Feb 18 20:35:42 HomeNAS kernel: re0: link state changed to UP
Feb 18 20:35:42 HomeNAS dhclient: New IP Address (re0): 192.168.2.3
Feb 18 20:35:42 HomeNAS dhclient: New Subnet Mask (re0): 255.255.255.0
Feb 18 20:35:42 HomeNAS dhclient: New Broadcast Address (re0): 192.168.2.255
Feb 18 20:35:42 HomeNAS dhclient: New Routers (re0): 192.168.2.1

 

[dlavigne]

Sounds like the Realtek NIC is being flaky. Do you have another NIC (e.g. an Intel) that you can install?

 

[Happybug]

Only have the NIC that comes with the laptop. As an alternative, I download the pbi file and then tried to upload it into the jail which had been created by the failed plug-in process. I got the same error message.

 

[dwoodard3950]

Not sure where to post this as the list of plugin issues are numerous, but I too can't get plugins to install. I've jumped around reading about warden and other related items, but with no success. I have several plugins installed and I recently upgraded to 9.2.1.2 keen to improve the plugin experience. However, I can't now install plugins. I get the following error as seen in warden.log;

Code:

Building new Jail... Please wait...
zfs clone tank/mnt/tank/jail/.warden-template-pluginjail@clean tank/jail/owncloud_1
ERROR: Failed creating clean ZFS base clone

Note that the prefix is duplicate the root of the path to the jail dataset; why is this?

Some relevant configuration items;

Code:

[root@rome /mnt/tank/jail]# zpool get altroot tank
NAME  PROPERTY  VALUE    SOURCE
tank  altroot   /mnt     local
 
[root@rome /mnt/tank/jail]# zfs list -rt snap tank/jail/.warden-template-pluginjail
NAME                                          USED  AVAIL  REFER  MOUNTPOINT
tank/jail/.warden-template-pluginjail@clean   128K      -  1.26G  -
 
[root@rome /mnt/tank/jail]# warden template list
Jail Templates:
------------------------------
9.1-RELEASE-amd64 - FreeBSD 9.1 (amd64)
9.1-RELEASE-amd64-pluginjail - FreeBSD 9.1 (amd64)
pluginjail - FreeBSD 9.2 (amd64)

And direction would be much appreciated.

 

[dlavigne]

There was a similar bug (same error message) which was supposed to be fixed for 9.2.1.1: https://bugs.freenas.org/issues/4168. It sounds like upgrading still has a bug. It would be worthwhile creating a new bug, referencing the old bug number, and posting the new bug number here.