9.2.1 mDNSResponder messages

Status
Not open for further replies.

Kymmitsu

Cadet
Joined
Jan 24, 2014
Messages
6
I have updated to the shiny new 9.2.1 yesterday and I am getting mDNS responder messages.
Code:
Starting mdnsd.
Feb  9 07:49:51 HPEENAS mDNSResponder: mDNSResponder (Engineering Build) (Feb  8 2014 00:26:22) starting
Feb  9 07:49:51 HPEENAS mDNSResponder:  8: Listening for incoming Unix Domain Socket client requests
Feb  9 07:49:51 HPEENAS mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)


Code:
Waiting up to 5 seconds for ixdiagnose to finish... done.
Feb  9 07:49:51 HPEENAS mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Feb  9 07:49:53 HPEENAS mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C2FD60 HPEENAS.local. (Addr) that's already in the list
Feb  9 07:49:53 HPEENAS mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C30180 245.1.168.192.in-addr.arpa. (PTR) that's already in the list


I have attached dmesg output.

Original - 9.2.0 - messages werent there or suppressed.

9.2.1 upgrade:
First upgrade was through GUI using the upgrade Firmware.
Second was clean install using CD to create USB.
I have gone back to 9.2.0 again but happy to upgrade again if needed.

Also getting
Code:
Feb  9 07:50:34 HPEENAS smbd[4435]: [2014/02/09 07:50:34.168855,  0] ../source3/lib/util_sock.c:941(matchname)
Feb  9 07:50:34 HPEENAS smbd[4435]:  matchname: host name/name mismatch: 192.168.1.140 != (NULL)
Feb  9 07:50:34 HPEENAS smbd[4435]: [2014/02/09 07:50:34.169384,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Feb  9 07:50:34 HPEENAS smbd[4435]:  matchname failed on 192.168.1.140


Turning off "Hostname Lookup" fixes this - but in 9.2.0 I never had to do that. Maybe related to mDNSResponder errors.

It was reported in Bug #3965 and #3991 and it insinuated error was addressed + fixed.

My FreeNAS application - Simple Personal Home Server - No plugins, Media server and personal file server backup point. Connecteed via 1GB switch and ADSL Router.

Any ideas? This new version has IE fix , UPS driver,MAC time Machine and better reporting tools which is why I have upgraded. I am back at 9.2.0 but I am very happy to update for testing or ideas.
 

Attachments

  • dmesg.txt
    18.2 KB · Views: 319

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
I would report it as a bug again.
 

FlangeMonkey

Contributor
Joined
Dec 6, 2012
Messages
111
I've been looking into into this error and read the bug report, however I'm not seeing the mDNSResponder service as started:

[root@freenas] ~# service mdnsresponder status
Will not 'status' mdnsresponder because mdnsresponder_enable is NO.

Is this related because I'm unable to resolve local clients from freenas via mDNS.
 
D

dlavigne

Guest
[root@freenas] ~# service mdnsresponder status
Will not 'status' mdnsresponder because mdnsresponder_enable is NO.

Try using: service mdnsresponder onestart
 

Kymmitsu

Cadet
Joined
Jan 24, 2014
Messages
6
Hope I havent necro'ed this too much...

Great to see problem has been addressed - when this is released I can finally upgrade.

Thanks
 
Status
Not open for further replies.
Top