Project

General

Profile

Bug #38265

At boot, have MDNS wait for /etc/resolv.conf to be available and valid

Added by Joe Maloney about 2 years ago. Updated about 2 years ago.

Status:
Done
Priority:
Nice to have
Assignee:
John Hixson
Category:
Services
Target version:
11.2-BETA2
Seen in:
11.2-BETA1
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I have noticed some errors about unreachable network before pool import that may be related. Attaching a debug to provide a log. Basically the problem I am seeing is that mdns does not work at all upon boot up until I restart a service like smb, or ssh.

IMG_0197.jpg (811 KB) IMG_0197.jpg Screenshot showing mdns error before volume import Joe Maloney, 07/16/2018 06:20 AM
mDNS.jpg (1.68 MB) mDNS.jpg Bonnie Follweiler, 07/25/2018 10:50 AM
Screen Shot 2018-07-25 at 2.38.23 PM.png (78.4 KB) Screen Shot 2018-07-25 at 2.38.23 PM.png Bonnie Follweiler, 07/25/2018 11:38 AM
Screen Shot 2018-07-25 at 2.37.53 PM.png (81.9 KB) Screen Shot 2018-07-25 at 2.37.53 PM.png Bonnie Follweiler, 07/25/2018 11:38 AM
Screen Shot 2018-07-25 at 5.26.10 PM.png (81.6 KB) Screen Shot 2018-07-25 at 5.26.10 PM.png Bonnie Follweiler, 07/25/2018 02:26 PM
Screen Shot 2018-07-25 at 5.25.40 PM.png (105 KB) Screen Shot 2018-07-25 at 5.25.40 PM.png Bonnie Follweiler, 07/25/2018 02:27 PM
21505
22603
22608
22613
22673
22678

Related issues

Copied to FreeNAS - Bug #40692: At boot, have MDNS wait for /etc/resolv.conf to be available and validDone

Associated revisions

Revision fd5b5a43 (diff)
Added by John Hixson about 2 years ago

Wait for /etc/resolv.conf to be available and valid Ticket: #38265

Revision aab0c3de (diff)
Added by John Hixson about 2 years ago

Wait for /etc/resolv.conf to be available and valid Ticket: #38265 (cherry picked from commit fd5b5a434f39c7bc527f6e97b946865160c6d0ca) (11.1-stable) Ticket: #40692

History

#1 Updated by Joe Maloney about 2 years ago

  • File debug-joemini-20180715225747.txz added
  • Private changed from No to Yes

#2 Updated by Dru Lavigne about 2 years ago

  • Assignee changed from Release Council to John Hixson
  • Target version changed from Backlog to 11.2-RC2

#3 Updated by Joe Maloney about 2 years ago

After more testing I wanted to add more details. If I use AFP mdns always works. I can always ping, and access FreeNAS from finder upon reboot of the FreeNAS. If I try to use SMB, or SSH together or separately mdns does not work upon reboot. I cannot see the object in the finder until I restart SMB, or SSH. I cannot ping the FreeNAS until I restart SMB, or SSH.

#4 Updated by Joe Maloney about 2 years ago

21505

#5 Updated by Dru Lavigne about 2 years ago

  • Target version changed from 11.2-RC2 to 11.2-BETA3

#6 Updated by John Hixson about 2 years ago

  • Status changed from Unscreened to Screened

#7 Updated by John Hixson about 2 years ago

This is still related to /etc/resolv.conf not existing when the mdns plugin is loaded. I've got a couple ways of dealing with this, will look at it more tomorrow.

#10 Updated by John Hixson about 2 years ago

The problem here is the middleware begins very early in boot. The mDNS plugin is loaded at that time. While the mDNS plugin waits for mDNS to be available, it does not wait for DNS to be available. I have fixed this to wait for DNS and a valid /etc/resolv.conf to be available.

#11 Updated by John Hixson about 2 years ago

  • Status changed from Screened to Ready for Testing

#12 Updated by Dru Lavigne about 2 years ago

  • Subject changed from mdns does not work at boot up to At boot, have MDNS wait for /etc/resolv.conf to be available and valid
  • Target version changed from 11.2-BETA3 to 11.2-BETA2
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#13 Updated by Dru Lavigne about 2 years ago

  • File deleted (debug-joemini-20180715225747.txz)

#14 Updated by Dru Lavigne about 2 years ago

  • Private changed from Yes to No

#15 Updated by Bonnie Follweiler about 2 years ago

  • File mDNS.jpg mDNS.jpg added
  • Status changed from Ready for Testing to Failed Testing
22603

Test Failed After updating to the latest Nightlies I got the mDNS errors in the console (see Screenshots)

#16 Updated by Bonnie Follweiler about 2 years ago

  • Status changed from Failed Testing to Ready for Testing

re-test
Test Case:
turn off all services, make sure when you boot, no services start, including ssh
absolutely all of them unchecked and not to start at boot
reboot the system
open the web shell
run this: dns-sd -B _middleware
that should show your hostname
and then dns-sd -B .
that should show your hostname in the output as well

Eample:
[root@devnas ~]# dns-sd B _middleware
Browsing for _middleware._tcp
DATE: ---Wed 25 Jul 2018--
14:06:55.168 ...STARTING...
Timestamp A/R Flags if Domain Service Type Instance Name
14:06:55.168 Add 3 1 local. _middleware._tcp. freenas
14:06:55.168 Add 2 1 local. _middleware._tcp. devnas
[root@devnas ~]# dns-sd B .
Browsing for _http._tcp
DATE: ---Wed 25 Jul 2018--
14:07:10.614 ...STARTING...
Timestamp A/R Flags if Domain Service Type Instance Name
14:07:10.615 Add 3 1 local. _http._tcp. freenas
14:07:10.615 Add 3 1 local. _http._tcp. macmini
14:07:10.615 Add 3 1 local. _http._tcp. vmnas
14:07:10.615 Add 3 1 local. _http._tcp. Officejet Pro 8600 [91BB64]
14:07:10.615 Add 2 1 local. _http._tcp. devnas
This is all from a host named "devnas"

#17 Updated by Bonnie Follweiler about 2 years ago

22608
22613

Test Passed in FreeNAS-11.2-MASTER-201807250900

#18 Updated by Dru Lavigne about 2 years ago

  • Status changed from Passed Testing to Done

#19 Updated by John Hixson about 2 years ago

Bonnie Follweiler wrote:

Test Passed in FreeNAS-11.2-MASTER-201807250900

How can you tell this passed? If you change your hostname to something like "Bonnie", that will be the only way to distinguish yourself here. All this shows is lots of freenas boxes on the network.

#20 Updated by John Hixson about 2 years ago

  • Status changed from Done to Ready for Testing

#21 Updated by Dru Lavigne about 2 years ago

  • Needs QA changed from No to Yes

#22 Updated by Bonnie Follweiler about 2 years ago

22673
22678

#23 Updated by Dru Lavigne about 2 years ago

  • Status changed from Passed Testing to Done

#24 Updated by John Hixson about 2 years ago

  • Copied to Bug #40692: At boot, have MDNS wait for /etc/resolv.conf to be available and valid added

Also available in: Atom PDF