11.2 Release - Can't install plugins

[Phot3k]

Hi all, I'm 99% certain this is something I configured incorrectly on my end and could use help with knowing what I did wrong.

I haven't really tinkered with my FreeNAS system and it's running great as a NAS with all my drives. Not keeping anything mission critical as this was mostly a learning exercise and putting some old hardware to use (namely 7+ platter drives). Most or nearly all of the settings are left on default with the exception of activating 'powerd'.

Running FreeNAS-11.2-RELEASE (upgraded from my initial install which was 11.1U6).

1. (Plugins\Available) So I navigate over in the GUI to the plugins page, and try and install QBitorrent or even Transmission.
2. (Plugins\Add) Leave the next page with DHCP checked
3. Hit save
4. I see the window at 50% with it quering - net-p2p/qbittorrent
5. I see the install window at 75% with net-p2p/qbittorrent, stays here for maybe a minute or two
6. And this is where it quits with '[EFAULT] Exception: URLError: occured, destroyed qbittorrent.
7. It does the same thing with Transmission

I suspect it's my network configuration or connection so I few stupid questions/assumptions on my end.

• I left the network configuration when I installed FreeNAS with getting an IP and everything else through DHCP, but used my Google Wifi to manually assign it a static IP via MAC address. When I try to install the plugins I notice it tries to get a new IP through DHCP, could this be tripping over the fact that Google Wifi is trying to assign it the same IP as my FreeNAS originally received?
• I've tried to manually assign an IP via eth0 or bridge0, using 24 for ipv4 netmask, but then I get a different error:
  • [EFAULT] Exception: CallError:[EFAULT] pkg.cdn.trueos.org could not be reached via DNS, check your network occured, destroyed qbittorrent.
  • This leads me to suspect it might be how I'm configuring the IP of my FreeNAS (via DHCP but router is assigning a static IP to it via MAC)
• I never setup a Network interface under Network\Interfaces, should I? I've read the manual but couldn't really grasp why/if I needed one?
• The console shows the following, nothing I can really tell but the destination address delete failed might be my only clue.
• Do I need to have setup a Jail first? I have an IOCage already in my storage pools, that seemed to have been created as I had a jails pool originally when I was on 11.1U6, which in turn was created after I looked at the plugins page but never installed anything.

Code:

Dec 18 17:41:08 FreeNAS epair0b: Ethernet address: 02:de:d0:00:05:0b
Dec 18 17:41:08 FreeNAS kernel: epair0a: link state changed to UP
Dec 18 17:41:08 FreeNAS kernel: epair0a: link state changed to UP
Dec 18 17:41:08 FreeNAS kernel: epair0b: link state changed to UP
Dec 18 17:41:08 FreeNAS kernel: epair0b: link state changed to UP
Dec 18 17:41:08 FreeNAS kernel: epair0a: changing name to 'vnet0:4'
Dec 18 17:41:08 FreeNAS kernel: vnet0:4: promiscuous mode enabled
Dec 18 17:41:08 FreeNAS kernel: re0: link state changed to DOWN
Dec 18 17:41:08 FreeNAS kernel: re0: link state changed to DOWN
Dec 18 17:41:12 FreeNAS kernel: re0: link state changed to UP
Dec 18 17:41:12 FreeNAS kernel: re0: link state changed to UP
Dec 18 17:41:18 FreeNAS dhclient: New IP Address (re0): 192.168.86.36
Dec 18 17:41:18 FreeNAS dhclient: New Subnet Mask (re0): 255.255.255.0
Dec 18 17:41:18 FreeNAS dhclient: New Broadcast Address (re0): 192.168.86.255
Dec 18 17:41:18 FreeNAS dhclient: New Routers (re0): 192.168.86.1
Dec 18 17:42:24 FreeNAS kernel: vnet0:4: link state changed to DOWN
Dec 18 17:42:24 FreeNAS kernel: vnet0:4: link state changed to DOWN
Dec 18 17:42:24 FreeNAS kernel: epair0b: link state changed to DOWN
Dec 18 17:42:24 FreeNAS kernel: epair0b: link state changed to DOWN
Dec 18 17:42:24 FreeNAS kernel: re0: link state changed to DOWN
Dec 18 17:42:24 FreeNAS kernel: re0: link state changed to DOWN
Dec 18 17:42:24 FreeNAS kernel: bridge0: link state changed to DOWN
Dec 18 17:42:24 FreeNAS kernel: bridge0: link state changed to DOWN
Dec 18 17:42:28 FreeNAS dhclient: New IP Address (re0): 192.168.86.36
Dec 18 17:42:28 FreeNAS dhclient: New Subnet Mask (re0): 255.255.255.0
Dec 18 17:42:28 FreeNAS dhclient: New Broadcast Address (re0): 192.168.86.255
Dec 18 17:42:28 FreeNAS dhclient: New Routers (re0): 192.168.86.1
Dec 18 17:42:28 FreeNAS kernel: re0: link state changed to UP
Dec 18 17:42:28 FreeNAS kernel: re0: link state changed to UP
Dec 18 17:42:28 FreeNAS kernel: bridge0: link state changed to UP
Dec 18 17:42:28 FreeNAS kernel: bridge0: link state changed to UP
Dec 18 17:43:00 FreeNAS kernel: in6_purgeaddr: err=65, destination address delete failed

The log in /var/logs gives similar/identical output.

Some more details, it's a consumer Asus P8Z77 board, 16GB of RAM, an Intel i5-3570k. Booting off an SSD, and running two Z1 vdevs in one pool.

Code:

% zpool status
  pool: Volume1
 state: ONLINE
  scan: scrub repaired 0 in 0 days 03:58:55 with 0 errors on Mon Dec 17 14:17:37 2018
config:

        NAME                                                STATE     READ WRITE CKSUM
        Volume1                                             ONLINE       0     0     0
          raidz1-0                                          ONLINE       0     0     0
            gptid/8df32afc-f8b6-11e8-8edc-c860009b68d0.eli  ONLINE       0     0     0
            gptid/8f10a952-f8b6-11e8-8edc-c860009b68d0.eli  ONLINE       0     0     0
            gptid/8fd98a1e-f8b6-11e8-8edc-c860009b68d0.eli  ONLINE       0     0     0
            gptid/90842652-f8b6-11e8-8edc-c860009b68d0.eli  ONLINE       0     0     0
          raidz1-1                                          ONLINE       0     0     0
            gptid/f82e0fd3-fdd0-11e8-b820-c860009b68d0.eli  ONLINE       0     0     0
            gptid/e01c673f-f8b6-11e8-8edc-c860009b68d0.eli  ONLINE       0     0     0
            gptid/e16039ea-f8b6-11e8-8edc-c860009b68d0.eli  ONLINE       0     0     0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:05 with 0 errors on Tue Dec 18 03:45:05 2018
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          ada3p2    ONLINE       0     0     0

errors: No known data errors
%

 

[dlavigne]

Ouch, a Realtek NIC (re0). Does replacing that with one of the recommended Intel NICs resolve the issue?

 

[Phot3k]

I'll give that a try, I think I have a box of spare NIC's, maybe a better/recommended one. I heavily assumed it was my lazy way of assigning a static IP to the FreeNAS device.

 

[Phot3k]

Marking as solved! Totally bonehead move on my part as part my learning FreeNAS, probably because I was initially setting it up before I understood it more, I had an IP in WebGUI ipv4 address, when I cleared it out as 0.0.0.0 and saved, the plugin installed properly.

On the other hand, I have a new Intel NIC card now! Went and picked up an Intel 82574L Gigabit Ethernet Controller.

 

[Monkey Bizness]

I had an IP in WebGUI ipv4 address, when I cleared it out as 0.0.0.0 and saved, the plugin installed properly.

Hi,
Which field did you clear out inthe GUI precisely? I'm having some similiar issues with plugins myself and also assume bad configuration, but i can't pinpoint it out :)

 

[Phot3k]

Hi,
Which field did you clear out inthe GUI precisely? I'm having some similiar issues with plugins myself and also assume bad configuration, but i can't pinpoint it out :)

That would be the System > General > WebGUI Ipv4 address field. Not sure why I even filled it out, probably when I was looking at all the settings late one night, so I'm not sure how helpful this will be unless some random person also did what I did.

 

[Monkey Bizness]

Well I could be that random person :)
I have been changing configuration around so that might have been the source of my issue.
Actually, this field is one i did not tampered with. So not the source of my issue.

Thanks for answering anyway.