SOLVED No IP from DHCP on jails - Moved to new ticket

[melloa]

Guys,

I've noticed that after my upgrade from 9.3 to 10, my jails are not getting IP from the DHCP.

Just deleted my jails and jail dataset, and recreated a new jail for test: No IP.

root@test:/ # ifconfig
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:ff:70:00:06:0b
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

------------------------

Build FreeNAS-9.10-STABLE-201605021851 (35c85f7)
Platform Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz

------------------------

Any ideas?

Thanks,
Al

 

[melloa]

Same issues with plugins. Just reinstall owncloud and had to assign an IP to the jail to start it.

 

[dlavigne]

Does it get a lease if you type dhclient epair0b inside the jail (or whichever the epair device name is)? Note that you may have to killall dhclient first. If it doesn't get a lease, paste the output from the dhclient command.

 

[melloa]

It does. See outputs:

root@test:/ # ifconfig
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:ff:70:00:06:0b
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
root@test:/ # dhclient epair0b
DHCPDISCOVER on epair0b to 255.255.255.255 port 67 interval 3
DHCPOFFER from 10.10.10.1
DHCPREQUEST on epair0b to 255.255.255.255 port 67
DHCPACK from 10.10.10.1
bound to 10.10.10.138 -- renewal in 3600 seconds.
root@test:/ # ifconfig
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:ff:70:00:06:0b
inet 10.10.10.138 netmask 0xffffff00 broadcast 10.10.10.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active


But the GUI doesn't show any IP, just DHCP under IP Address (although if config on the shell does show the same ip above)

 

[dlavigne]

To clarify, where exactly are you not seeing the IP?

 

[melloa]

The GUI

 

[dlavigne]

That is correct. It will only show an IP if you manually set a static IP, otherwise it says DHCP.

 

[melloa]

Not sure. I always saw the IP besides the word DHCP. See my other FN that I didn't delete the jails:

 

[melloa]

That one is running:


Build FreeNAS-9.10-STABLE-201605021851 (35c85f7)
Platform Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz

and mine:

Build FreeNAS-9.10-STABLE-201605021851 (35c85f7)
Platform Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz

So same build.

 

[dlavigne]

I think that is only the case for plugins....

 

[melloa]

It came up after awhile. See screen. Also installed a plugin to test and no IP on GUI or shell.

 

[melloa]

Still looking for ideas. About to build a test FN to test and see if a fresh install will do the same ... Already moved all my servers from FN plugins to Vbox to keep them running, so any help will be appreciated.

 

[melloa]

By the way ... rolled back to an earlier boot - Build FreeNAS-9.10-STABLE-201603252134 (412fb1c) - and now my jails are getting IP from DHCP.

Any directions on how to move forward? If the 9.3 to 9.10 upgrade is the cause, should I do a clean install and restore my configs/backups. At this point I'm not trusting my system.

 

[dlavigne]

It would be interesting to see if a clean install by a restored config exhibits the same behavior. If it does, it's probably worth creating a bug report.

 

[melloa]

As requested:

Fresh install

- Regular jail created and obtained IP from DHCP
- Owncloud plugin installed and no IP

- Manually assigned IP
- Changed back to DHCP
- Jail kept same IP previously assigned​

- Installed Transmission to capture screens

- No IP after installation

- Manually assigned

- Opened config for it and GUI has changed to DHC

- Saved and restarted -> No IP

- Some errors

May 25 19:39:35 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/raid/jails/transmission_1'
May 25 19:39:35 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/raid/jails/test'
May 25 19:39:35 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/raid/jails/owncloud_1'
May 25 19:40:00 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs list -H -o name '/mnt/raid/jails/.warden-template-pluginjail'
May 25 19:40:00 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/raid/jails/transmission_1'
May 25 19:40:00 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/raid/jails/test'
May 25 19:40:01 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/raid/jails/owncloud_1'
May 25 19:40:01 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs list -H -o name '/mnt/raid/jails/.warden-template-pluginjail'
May 25 19:40:01 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/raid/jails/transmission_1'
May 25 19:40:01 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/raid/jails/test'
May 25 19:40:01 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/raid/jails/owncloud_1'
May 25 19:40:18 freenas manage.py: [freeadmin.navtree:630] An error occurred while unserializing from http://10.10.10.137/plugins/transmission/2/_s/treemenu: No JSON object could be decoded
May 25 19:40:37 freenas kernel: epair2a: link state changed to DOWN
May 25 19:40:37 freenas kernel: epair2a: link state changed to DOWN
May 25 19:40:37 freenas kernel: epair2b: link state changed to DOWN
May 25 19:40:37 freenas kernel: epair2b: link state changed to DOWN
May 25 19:40:40 freenas kernel: ifa_del_loopback_route: deletion failed: 48
May 25 19:40:40 freenas Freed UMA keg (udp_inpcb) was not empty (60 items). Lost 6 pages of memory.
May 25 19:40:40 freenas Freed UMA keg (udpcb) was not empty (668 items). Lost 4 pages of memory.
May 25 19:40:40 freenas Freed UMA keg (tcp_inpcb) was not empty (30 items). Lost 3 pages of memory.
May 25 19:40:40 freenas Freed UMA keg (tcpcb) was not empty (9 items). Lost 3 pages of memory.
May 25 19:40:40 freenas Freed UMA keg (ripcb) was not empty (30 items). Lost 3 pages of memory.
May 25 19:40:40 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
May 25 19:40:40 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
May 25 23:40:43 freenas devd: Executing '/etc/pccard_ether epair2a start'
May 25 19:40:43 freenas epair2a: Ethernet address: 02:ff:60:00:06:0a
May 25 19:40:43 freenas epair2b: Ethernet address: 02:ff:b0:00:07:0b
May 25 19:40:43 freenas kernel: epair2a: link state changed to UP
May 25 19:40:43 freenas kernel: epair2a: link state changed to UP
May 25 19:40:43 freenas kernel: epair2b: link state changed to UP
May 25 19:40:43 freenas kernel: epair2b: link state changed to UP
May 25 19:40:43 freenas kernel: epair2a: promiscuous mode enabled
May 25 19:40:43 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 25 19:40:43 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 25 23:40:43 freenas devd: Executing '/etc/pccard_ether epair2b start'
May 25 23:40:43 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair2a'
May 25 19:41:05 freenas manage.py: [freeadmin.navtree:630] An error occurred while unserializing from http://10.10.10.137/plugins/transmission/2/_s/treemenu: No JSON object could be decoded


-------------------------

This is a LAB box, so I can test anything you guys like.

FYI: I won't be close to the computers from Thu 'til Sun, so my replies will be delayed during that time.

​

 

[melloa]

More info before I go:

Fresh 9.10 install plugin install (No IP from DHCP for transmission plugin)

May 25 22:49:47 freenas warden: Building new Jail... Please wait...
May 25 22:49:47 freenas warden: zfs clone raid/cifs/.warden-template-pluginjail@clean raid/cifs/transmission_1
May 25 22:49:48 freenas warden: Success!
May 25 22:49:48 freenas warden: Jail created at /mnt/raid/cifs/transmission_1
May 26 02:49:48 freenas devd: Executing '/etc/pccard_ether epair1a start'
May 26 02:49:48 freenas devd: Executing '/etc/pccard_ether epair1b start'
May 26 02:49:48 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair1a'
May 25 22:49:48 freenas epair1a: Ethernet address: 02:ff:20:00:05:0a
May 25 22:49:48 freenas epair1b: Ethernet address: 02:ff:70:00:06:0b
May 25 22:49:48 freenas kernel: epair1a: link state changed to UP
May 25 22:49:48 freenas kernel: epair1a: link state changed to UP
May 25 22:49:48 freenas kernel: epair1b: link state changed to UP
May 25 22:49:48 freenas kernel: epair1b: link state changed to UP
May 25 22:49:48 freenas kernel: epair1a: promiscuous mode enabled
May 25 22:49:48 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
May 25 22:49:48 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
May 25 22:49:59 freenas notifier: Performing sanity check on nginx configuration:
May 25 22:49:59 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
May 25 22:49:59 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
May 25 22:50:00 freenas manage.py: [freeadmin.navtree:630] An error occurred while unserializing from http://10.10.10.130/plugins/transmission/1/_s/treemenu: No JSON object could be decoded
May 25 22:50:01 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 00000008014CCD60 freenas.local. (Addr) that's already in the list
May 25 22:50:01 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 00000008014CD180 130.10.10.10.in-addr.arpa. (PTR) that's already in the list

Fresh 9.3 with latest build install (transmission plugin obtain IP from DHCP)

May 25 23:51:01 freenas warden: Building new Jail... Please wait...
May 25 23:51:01 freenas warden: zfs clone raid/jails/.warden-template-pluginjail@clean raid/jails/transmission_1
May 25 23:51:01 freenas warden: Success!
May 25 23:51:01 freenas warden: Jail created at /mnt/raid/jails/transmission_1
May 25 23:51:01 freenas epair1a: Ethernet address: 02:27:05:00:08:0a
May 25 23:51:01 freenas epair1b: Ethernet address: 02:27:05:00:09:0b
May 25 23:51:01 freenas kernel: epair1a: link state changed to UP
May 25 23:51:01 freenas kernel: epair1a: link state changed to UP
May 25 23:51:01 freenas kernel: epair1b: link state changed to UP
May 25 23:51:01 freenas kernel: epair1b: link state changed to UP
May 25 23:51:01 freenas kernel: epair1a: promiscuous mode enabled
May 25 23:51:02 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
May 25 23:51:02 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
May 25 23:51:12 freenas notifier: Performing sanity check on nginx configuration:
May 25 23:51:12 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
May 25 23:51:12 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful

Update to 9.10 Stable (No IP for mineos plugin)

May 26 00:08:40 freenas warden: Building new Jail... Please wait...
May 26 00:08:40 freenas warden: zfs clone raid/jails/.warden-template-pluginjail@clean raid/jails/mineos_1
May 26 00:08:41 freenas warden: Success!
May 26 00:08:41 freenas warden: Jail created at /mnt/raid/jails/mineos_1
May 26 04:08:41 freenas devd: Executing '/etc/pccard_ether epair2a start'
May 26 04:08:41 freenas devd: Executing '/etc/pccard_ether epair2b start'
May 26 04:08:41 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair2a'
May 26 00:08:41 freenas epair2a: Ethernet address: 02:ff:20:00:06:0a
May 26 00:08:41 freenas epair2b: Ethernet address: 02:ff:70:00:07:0b
May 26 00:08:41 freenas kernel: epair2a: link state changed to UP
May 26 00:08:41 freenas kernel: epair2a: link state changed to UP
May 26 00:08:41 freenas kernel: epair2b: link state changed to UP
May 26 00:08:41 freenas kernel: epair2b: link state changed to UP
May 26 00:08:41 freenas kernel: epair2a: promiscuous mode enabled
May 26 00:08:41 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 26 00:08:41 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
May 26 00:09:01 freenas notifier: Performing sanity check on nginx configuration:
May 26 00:09:01 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
May 26 00:09:01 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
May 26 00:09:03 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 00000008014C8D60 freenas.local. (Addr) that's already in the list
May 26 00:09:03 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 00000008014C9180 130.10.10.10.in-addr.arpa. (PTR) that's already in the list
May 26 00:09:04 freenas manage.py: [freeadmin.navtree:630] An error occurred while unserializing from http://10.10.10.130/plugins/mineos/2/_s/treemenu: No JSON object could be decoded

Going to shell to force renew

root@mineos_1:/ # dhclient epair2b
DHCPDISCOVER on epair2b to 255.255.255.255 port 67 interval 3
DHCPOFFER from 10.10.10.1
DHCPREQUEST on epair2b to 255.255.255.255 port 67
DHCPACK from 10.10.10.1
bound to 10.10.10.124 -- renewal in 3600 seconds.
root@mineos_1:/ #

 

[melloa]

Gurus,
Still unable to have jails and plug-ins obtaining an ip from dhcp. Any ideas?

 

[sharky]

Hey Melloa,

I had the same problem and the only way to workaround was to reboot the hole sytem.

It is a bug...

 

[melloa]

Hi sharky,

Thanks for your reply.

I've built a new box just for testing, so reboot was done :)

Installed 9.3, no problem. Upgraded and no ip issue started. Installed fresh 9.10 and no ip also started.

I had 9.3 ruining on two asrock, one old dell, and one old hp without issues. After upgrade all four had dhcp broke.

If you know the bug number, I'd like to read the thread to catchup.

 

[sharky]

Feel free to create a bug . I will join the discussion ;-)