Update to U2 = no ip for dhcpd?

[Rudi Pittman]

I previously had the issue with 9.10.1 U1 where I already had a media user so the update failed. I rolled back to 9.10.1 and things were fine. When the updates for U2 came out I applied them. I just got around to rebooting the system and U2 does not get an ip for dhcpd.....things seem to go downhill from there. Rolling back to 9.10.1 again fixes things fine.

I don't want to report a bug until I know if anyone else has encountered it and whether there is an easy fix. Also if I do report it as a bug what files should I attach to the bug report? I've rebooted so not sure anything is still available that would be useful.


Thanks for your time.

 

[Ericloewe]

Aaaand, what hardware are you using? Literally nobody else has complained about DHCP not working.

 

[Rudi Pittman]

Aaaand, what hardware are you using? Literally nobody else has complained about DHCP not working.

Lucky me. *sigh*

If I missed something let me know....

Codegen Server 9011-C10 ATX case with power supply. [ http://www.pc-experience.de/wbb2/thread.php?threadid=18342 ]
GIGABYTE GA-Z87-DS3H LGA 1150 Intel Z87 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard
LGA3220T cpu
Ballistix Tactical 16GB Kit 8GBx2 DDR3 1600 MT/s PC3-12800 CL8 at 1.5V UDIMM 240-Pin Memory BLT2KIT8G3D1608DT1TX0
G.Skill F3-1600C9D-16GAR Ares 16GB (2x8GB) DDR3-1600Mhz Memory RAM
SYBA SI-PEX40064 PCI-Express 2.0 Low Profile Ready SATA III (6.0 Gb/s) Controller Card
SYBA SI-PEX40094 PCI Express Low Profile Ready SATA SATA III 2 Internal 6Gbps Ports PCI-e Controller Card
4 x Seagate ST5000DM000-1FK178 (5TB)
2 x TOSHIBA MD04ACA500 (5TB)
16 GB Flashdrive
1 x iStarUSA BPN-DE110SS-BLUE Trayless 5.25" to 3.5" SATA SAS 6 Gbps HDD Hot-swap Rack
2 x iStarUSA BPN-DE340SS-BLACK 3 x 5.25" to 4 x 3.5" SAS / SATA 6.0 Gb/s Trayless Hot-Swap Cage - Black Handle - OEM

The log for 10/22 including the failed boots is available at http://pastebin.com/AjQ4eLqE
If there is an easy way to wipe out U1 and U2 and have it reapply clean I'd be willing to try that. The server's been running fine for about a year including at least a couple of updates.

I note some messages such as:

Code:

Oct 22 03:31:48 freenas mDNSResponder: mDNSResponder (Engineering Build) (Oct  3 2016 06:58:50) stopping
Oct 22 03:31:48 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 0000000801480580 01   25 _smb._tcp.local. PTR freenas._smb._tcp.local.
Oct 22 03:31:48 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 000000080144F580 01   25 _ssh._tcp.local. PTR freenas._ssh._tcp.local.
Oct 22 03:31:48 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 000000080147D580 01   30 _sftp-ssh._tcp.local. PTR freenas._sftp-ssh._tcp.local.
Oct 22 03:31:48 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 0000000801485580 01   26 _http._tcp.local. PTR freenas._http._tcp.local.
Oct 22 03:31:48 freenas smbd: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Oct 22 03:31:50 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Oct 22 03:31:50 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Oct 22 03:31:50 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Oct 22 03:31:51 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Oct 22 03:31:51 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Oct 22 03:31:51 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Oct 22 03:31:51 freenas ntpd[1933]: ntpd exiting on signal 15 (Terminated)
Oct 22 03:31:52 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Oct 22 03:31:52 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Oct 22 03:31:52 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Oct 22 03:31:53 freenas python: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:8 Err

etc.....

 

[Ericloewe]

GIGABYTE GA-Z87-DS3H LGA 1150 Intel Z87 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard

Realtek LAN... Sounds like a likely culprit.

 

[Rudi Pittman]

Realtek LAN... Sounds like a likely culprit.

If it's been running fine for almost a year including through a major update from 9.3 to 9.10 why would it now flake out on the U2 changes because U1 WILL boot...just gives me a nag messages about the media user and 9.10.1 (and all previous versions) run fine. If the realtek lan was an issue would it not be a CONSISTANT one?

The U2 changelog (https://download.freenas.org/9.10/STABLE/9.10.1-U2/ChangeLog) lists:

#17908 Bug Ready For Release Expected EFI install fails with complaint about more than one boot device
#17904 Bug Ready For Release Expected Failed to report when snapshot failed to create
#17869 Bug Ready For Release Critical Virtualbox cannot run any VMachine after upgrade to 9.10.1-U1
#17826 Bug Ready For Release Critical Errors reported during replication
#17819 Bug Ready For Release Critical iSCSI LUN ID's all set to 0
#17809 Bug Ready For Release Important GRUB needs modules specified for improved reliability
#17789 Bug Ready For Release Critical Bug from latest updates for 9.10.1 on 09/27/2016
#17787 Bug Ready For Release Expected OpenSSL Fix Use After Free for large message sizes (CVE-2016-6309)

It doesn't look at first glance like any of those have anything to do with the lan.

 

[Ericloewe]

If it's been running fine for almost a year including through a major update from 9.3 to 9.10 why would it now flake out on the U2 changes because U1 WILL boot...just gives me a nag messages about the media user and 9.10.1 (and all previous versions) run fine. If the realtek lan was an issue would it not be a CONSISTANT one?

With Realtek, you never know. The driver is not known for its stability.

The log for 10/22 including the failed boots is available at http://pastebin.com/AjQ4eLqE

Your log seems to say that the NIC does get an IP address. That was with -U2?

 

[Rudi Pittman]

With Realtek, you never know. The driver is not known for its stability.

Your log seems to say that the NIC does get an IP address. That was with -U2?

I rolled back to 9.10.1 in the boot menu and it got an ip from that. If it got one before that I'm unware of it and it won't get one now (on U2).

I opened a bug with alot of the same info here: https://bugs.freenas.org/issues/18455


The log shows these:

Oct 22 03:52:34 freenas Trying to mount root from zfs:freenas-boot/ROOT/9.10.1-U2 []...
Oct 22 04:43:01 freenas Trying to mount root from zfs:freenas-boot/ROOT/9.10.1 []...

All I can say is the boot at 03:52 that appears to have grabbed an ip rebooted ITSELF at 03:55:51 and I didn't get an ip again until I went back to 9.10.1 at 04:43. I'll have to open it and see if I have a slot for a gigabit card and order one. Got a recommended chipset?

Every cheap ethernet card I've found on amazon has ended up being either RTL 8111 or RTL8169.

 

[Ericloewe]

Were you using -U2 at 4am?

 

[SweetAndLow]

Lucky me. *sigh*

If I missed something let me know....

Codegen Server 9011-C10 ATX case with power supply. [ http://www.pc-experience.de/wbb2/thread.php?threadid=18342 ]
GIGABYTE GA-Z87-DS3H LGA 1150 Intel Z87 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard
LGA3220T cpu
Ballistix Tactical 16GB Kit 8GBx2 DDR3 1600 MT/s PC3-12800 CL8 at 1.5V UDIMM 240-Pin Memory BLT2KIT8G3D1608DT1TX0
G.Skill F3-1600C9D-16GAR Ares 16GB (2x8GB) DDR3-1600Mhz Memory RAM
SYBA SI-PEX40064 PCI-Express 2.0 Low Profile Ready SATA III (6.0 Gb/s) Controller Card
SYBA SI-PEX40094 PCI Express Low Profile Ready SATA SATA III 2 Internal 6Gbps Ports PCI-e Controller Card
4 x Seagate ST5000DM000-1FK178 (5TB)
2 x TOSHIBA MD04ACA500 (5TB)
16 GB Flashdrive
1 x iStarUSA BPN-DE110SS-BLUE Trayless 5.25" to 3.5" SATA SAS 6 Gbps HDD Hot-swap Rack
2 x iStarUSA BPN-DE340SS-BLACK 3 x 5.25" to 4 x 3.5" SAS / SATA 6.0 Gb/s Trayless Hot-Swap Cage - Black Handle - OEM

The log for 10/22 including the failed boots is available at http://pastebin.com/AjQ4eLqE
If there is an easy way to wipe out U1 and U2 and have it reapply clean I'd be willing to try that. The server's been running fine for about a year including at least a couple of updates.

I note some messages such as:

Code:

Oct 22 03:31:48 freenas mDNSResponder: mDNSResponder (Engineering Build) (Oct  3 2016 06:58:50) stopping
Oct 22 03:31:48 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 0000000801480580 01   25 _smb._tcp.local. PTR freenas._smb._tcp.local.
Oct 22 03:31:48 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 000000080144F580 01   25 _ssh._tcp.local. PTR freenas._ssh._tcp.local.
Oct 22 03:31:48 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 000000080147D580 01   30 _sftp-ssh._tcp.local. PTR freenas._sftp-ssh._tcp.local.
Oct 22 03:31:48 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 0000000801485580 01   26 _http._tcp.local. PTR freenas._http._tcp.local.
Oct 22 03:31:48 freenas smbd: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Oct 22 03:31:50 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Oct 22 03:31:50 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Oct 22 03:31:50 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Oct 22 03:31:51 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Oct 22 03:31:51 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Oct 22 03:31:51 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Oct 22 03:31:51 freenas ntpd[1933]: ntpd exiting on signal 15 (Terminated)
Oct 22 03:31:52 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Oct 22 03:31:52 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Oct 22 03:31:52 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Oct 22 03:31:53 freenas python: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:8 Err

etc.....

Omg this is one of the scariest setups I have seen in awhile.

Have you tried setting a static IP? Maybe realtek broke something in DHCP.

Sent from my Nexus 5X using Tapatalk

 

[F!$hp0nd]

I had weird issues with 9.10.1U2 and DHCP. For me, it was easily solved by physically plugging a keyboard and screen into the server, shutting down the server. Unplugging the network from the server, booting the server. Deleting any interfaces I had configured, then shutting down the server, then plugging the network back in. Then booting the server and seeing if it gets a DHCP address. If it does, great! If not then move to step 2.
Unplug ethernet cable from server, shutdown server, boot it up, delete any configured interfaces, then configure a new one making sure to select the correct interface (if you have more than one LAN port on your server), then name it (i usually stick with the default), then set a static IP. Then I also set up all DNS and routing that needs to be done using the console menu. Then shutdown the server. Plug the ethernet back in, then boot the server.

If that still does not work. Use a PCIe based internet card and repeat step two but choosing the new card and see if it works.