Installing plugin on 11.2 fails to obtain DHCP address and fails to create jail

[Tony Self]

I have just upgraded my 9.10.2-U6 installation to the release copy of 11.2
Everything upgraded ok, so I am now starting the process of migrating my plugins from the legacy warden system to iocage.
I started with Sonarr.
I have stopped the old warden jail.
I have copied the Sonarr data directory tree to a separate apps data folder
I then tried to create a new iocage Sonarr plugin using DHCP

Unfortunately the create process failed because it was unable to get a DHCP address

The following is a copy of the StdOut : -

undefinedDec 7 15:38:27 fnplex epair17a: Ethernet address: 02:f1:d0:00:1b:0a
Dec 7 15:38:27 fnplex epair17b: Ethernet address: 02:f1:d0:00:1c:0b
Dec 7 15:38:27 fnplex kernel: epair17a: link state changed to UP
Dec 7 15:38:27 fnplex kernel: epair17a: link state changed to UP
Dec 7 15:38:27 fnplex kernel: epair17b: link state changed to UP
Dec 7 15:38:27 fnplex kernel: epair17b: link state changed to UP
Dec 7 15:38:27 fnplex kernel: epair17a: changing name to 'vnet0:19'
Dec 7 15:38:27 fnplex kernel: epair17b: changing name to 'epair0b'
Dec 7 15:38:27 fnplex kernel: vnet0:19: promiscuous mode enabled

Can anyone please help explain what is going on here and how I can resolve the problem.

Many thanks

 

[Tony Self]

Just a bit of an update on my progress with this problem.

I have a test machine that runs on an older HP N40L where I have been trying out the various versions of 11.2 and which yesterday I upgraded to the release version of 11.2. This was originally an 11.1 install, so unlike my production box, had not b been upgraded from 9.10.2

On the test machine I have been able to install plugins without a problem. I have just installed another plugin just to make sure it is not an issue with the release version of 11.2

On my main machine I have also created an empty jail without a problem obtaining a DHCP address

In comparing the network setups on both boxes, I have only noticed two differences: -
1. There is an IPMI section on the main box. I presume because HP's iLO4 service is built in.
2. No network interface was defined. I have therefore added the bge0 interface. Creating the Sonarr plugin still fails, although I am getting additional output to StdOut - see below.

Code:

undefinedDec  7 16:19:02 fnplex epair20a: Ethernet address: 02:f1:d0:00:21:0a
Dec  7 16:19:02 fnplex epair20b: Ethernet address: 02:f1:d0:00:22:0b
Dec  7 16:19:02 fnplex kernel: epair20a: link state changed to UP
Dec  7 16:19:02 fnplex kernel: epair20a: link state changed to UP
Dec  7 16:19:02 fnplex kernel: epair20b: link state changed to UP
Dec  7 16:19:02 fnplex kernel: epair20b: link state changed to UP
Dec  7 16:19:02 fnplex kernel: epair20a: changing name to 'vnet0:22'
Dec  7 16:19:02 fnplex kernel: epair20b: changing name to 'epair0b'
Dec  7 16:19:02 fnplex kernel: vnet0:22: promiscuous mode enabled
Dec  7 16:19:06 fnplex dhclient: New IP Address (bge0): 192.168.173.50
Dec  7 16:19:06 fnplex dhclient: New Subnet Mask (bge0): 255.255.255.0
Dec  7 16:19:06 fnplex dhclient: New Broadcast Address (bge0): 192.168.173.255
Dec  7 16:19:06 fnplex dhclient: New Routers (bge0): 192.168.173.1
Dec  7 16:19:40 fnplex kernel: bge0: link state changed to DOWN
Dec  7 16:19:40 fnplex kernel: bge0: link state changed to DOWN
Dec  7 16:19:42 fnplex dhclient: New IP Address (bge0): 192.168.173.50
Dec  7 16:19:42 fnplex dhclient: New Subnet Mask (bge0): 255.255.255.0
Dec  7 16:19:42 fnplex dhclient: New Broadcast Address (bge0): 192.168.173.255
Dec  7 16:19:42 fnplex dhclient: New Routers (bge0): 192.168.173.1
Dec  7 16:19:43 fnplex kernel: bge0: link state changed to UP
Dec  7 16:19:43 fnplex kernel: bge0: link state changed to UP

 

[Michael Hanna]

I been dealing with the same issue. Creating plugin I get the DHCP issue... however if I just create a jail DHCP works just fine.

 

[Tony Self]

Well i am glad it's not just me. Let's hope someone has a solution

 

[gt2416]

Please post this bug on https://redmine.ixsystems.com/projects/freenas/roadmap
You have a lot of details, hopefully the devs will be able to fix it.
Could you post the bug tracker number here once your done so we can track it ?

 

[Tony Self]

Reported as bug. Issue #62739 created.

 

[pschatz100]

Might be a problem with the update scripts. iocage, in particular, saw quite a bit of updating in the newer versions of FreeNAS. You might try updating from 9.10 to 11.1-U6, confirm things are working, then update from 11.1-U6 to 11.2.

 

[Tony Self]

I appear to have solved my problem.
What I failed to do after adding the Network Interface entry was reboot the system.
Having now rebooted, I can now create the Sonarr plugin.

 

[pschatz100]

Glad it's resolved.

 

[Big Data Guy]

Hi Tony Self,

I am experiencing the same problem. I can't create any plugins whatsoever.

The weird thing is that I have previously installed (as a test) on the same machine Freenas 11.U2 and all working fine.
The perfectionist in me decided to restart from scratch and using the newer Freenas 11.U2.1, and then I got this problem.

I decided to reinstall using the older version and see how it goes.

My spec:
Gigabyte Z97N-Wifi
i5-4690
16GB DDR3 non-ECC
3xWD RED 4TB and 3x Seagate Ironwolf 4TB.

 

[Big Data Guy]

Hi Tony Self,

I am experiencing the same problem. I can't create any plugins whatsoever.

The weird thing is that I have previously installed (as a test) on the same machine Freenas 11.U2 and all working fine.
The perfectionist in me decided to restart from scratch and using the newer Freenas 11.U2.1, and then I got this problem.

I decided to reinstall using the older version and see how it goes.

My spec:
Gigabyte Z97N-Wifi
i5-4690
16GB DDR3 non-ECC
3xWD RED 4TB and 3x Seagate Ironwolf 4TB.

I can confirm that after reinstalling with the 11.3-U2 instead of U2.1, I can successfully install the plugins without any problem.

 

[sretalla]

I can confirm that after reinstalling with the 11.3-U2 instead of U2.1, I can successfully install the plugins without any problem.

Well, that's good, but don't export any pools unless you want to lose them.

 

[Yorick]

Gigabyte Z97N-Wifi

Mama mia, che due palle!

LAN Chipset - Intel i217V - not terrible, but also not officially supported by FreeBSD. -LM would be.
Second LAN Chipset - Atheros 8161B - I can't even

I wonder whether people having trouble with DHCP can always be traced back to "your network" or "your NIC"

 

[Big Data Guy]

Mama mia, che due palle!

LAN Chipset - Intel i217V - not terrible, but also not officially supported by FreeBSD. -LM would be.
Second LAN Chipset - Atheros 8161B - I can't even

I wonder whether people having trouble with DHCP can always be traced back to "your network" or "your NIC"

Yeah, I am repurposing my old Windows PC for this.

Do you have a recommendation for cheap Mobo/processor to upgrade in the future? It is only for home server of 4 users.

 

[Big Data Guy]

Well, that's good, but don't export any pools unless you want to lose them.

Why is that may I ask? Because I did just that and have had no problem so far.

Thanks

 

[Redcoat]

Why is that may I ask? Because I did just that and have had no problem so far.

That comment was specifically in the context of exporting pools from 11.3-U2. That version contained a problem that could lead to pool loss - fixed in 11.3-U2.1 - see the first paragraph at https://www.ixsystems.com/blog/library/freenas-11-3-u2-1/