9.10 mDNS_Register_internal errors, help please

[radeon]

hey guys,

i just upgraded from 9.3 to 9.10 and now i'm getting these error messages:

Code:

Apr 4 12:39:40 freenas smbd: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Apr 4 12:39:41 freenas smbd: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Apr 4 12:39:42 freenas smbd: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Apr 4 12:39:43 freenas smbd: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:35 Err:-1 Errno:2 No such file or directory
Apr 4 12:39:47 freenas mDNSResponder: mDNSResponder (Engineering Build) (Mar 25 2016 21:58:46) starting
Apr 4 12:39:47 freenas mDNSResponder: 9: Listening for incoming Unix Domain Socket client requests
Apr 4 12:39:47 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Apr 4 12:39:47 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Apr 4 12:39:47 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Apr 4 12:39:54 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801406D60 freenas.local. (Addr) that's already in the list
Apr 4 12:39:54 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801407180 137.1.168.192.in-addr.arpa. (PTR) that's already in the list
Apr 4 12:39:54 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801409D60 freenas.local. (AAAA) that's already in the list
Apr 4 12:39:54 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 000000080140A180 8.2.9.5.A.B.E.F.F.F.9.6.B.E.2.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. (PTR) that's already in the list

Code:

Apr  4 21:45:24 freenas mDNSResponder: mDNSResponder (Engineering Build) (Mar 25 2016 21:58:46) stopping
Apr  4 21:45:24 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 0000000801483580 01   26 _http._tcp.local. PTR freenas._http._tcp.local.
Apr  4 21:45:24 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 000000080147A580 01   25 _smb._tcp.local. PTR freenas._smb._tcp.local.
Apr  4 21:45:24 freenas smbd: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Apr  4 21:45:25 freenas mDNSResponder: mDNSResponder (Engineering Build) (Mar 25 2016 21:58:46) starting
Apr  4 21:45:25 freenas mDNSResponder:  11: Listening for incoming Unix Domain Socket client requests
Apr  4 21:45:25 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Apr  4 21:45:25 freenas mDNSResponder: CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for PCP & NAT-PMP announcements
Apr  4 21:45:26 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801406D60 freenas.local. (Addr) that's already in the list
Apr  4 21:45:26 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801407180 137.1.168.192.in-addr.arpa. (PTR) that's already in the list

is this a critical error, should i be worried about it?

any ideas how to solve this? :s

 

[dlavigne]

Looks like someone reported this: https://bugs.freenas.org/issues/14448.

 

[radeon]

Looks like someone reported this: https://bugs.freenas.org/issues/14448.

yeah it was me x)

 

[Søren Madsen]

I can confirm this error.
I upgraded from
FreeNAS-FreeNAS-9.3-STABLE-201412090832
to
FreeNAS-8863f903d550e9d8a1e9f8c73ae9b4f0

Code:

Apr  6 10:45:33 smadsenserver mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801406D60 <serverName>.local. (Addr) that's already in the list
Apr  6 10:45:33 smadsenserver mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801407180 <IP>.in-addr.arpa. (PTR) that's already in the list

 

[enemy85]

i got the same error too

 

[Cybix]

I can also confirm this error. Never had it in 9.3 or 9.3.1. Clean installs each time

 

[nojohnny101]

just to add myself, i am getting this error as well after upgrading from 9.3.1. to 10

 

[BigDave]

FYI, this has been addressed and is nothing to worry about.
Here is Jordan's reply as of Saturday April 16th 2016
RE: Bug #14448


Updated by Jordan Hubbard 1 day ago

• Status changed from Screened to Behaves correctly

mDNSResponder is just naturally chatty about anything and everything it thinks you might like to know about (even when the warnings are benign network conditions it has detected and compensated for). We have a separate ticket open about making it shut up a bit more, so no need to keep this one open.

 

[Cybix]

Thank-you BigDave

 

[manojkply]

@Big Dave & Cybix,
could you please explain me this error. I am unable to get rid of this after many tries. need solution for this problem.
can mail me personally also on manojkply@gmail.com.
waiting for your response mates.

 

[manojkply]

FYI, this has been addressed and is nothing to worry about.
Here is Jordan's reply as of Saturday April 16th 2016
RE: Bug #14448


Updated by Jordan Hubbard 1 day ago

• Status changed from Screened to Behaves correctly

mDNSResponder is just naturally chatty about anything and everything it thinks you might like to know about (even when the warnings are benign network conditions it has detected and compensated for). We have a separate ticket open about making it shut up a bit more, so no need to keep this one open.

@Big Dave
could you please explain me this error. I am unable to get rid of this after many tries. need solution for this problem.
can mail me personally also on manojkply@gmail.com.
waiting for your response mates.

 

[Mirfster]

I *think* that the separate ticket that was being spoken of is: https://bugs.pcbsd.org/issues/14429

could you please explain me this error.

It is just due to that being a chatty protocol. From what I understand this is actually a port, so not that easy to modify. However, per the bug I linked they do have a proposed solution (just not incorporated yet; maybe they are still testing it):

Updated by Neha Rathod 4 months ago
Hi Jordan,

On investigation into this bug, it is observed that the syslog-ng daemon directs all the logs to their respective destination files from the syslog-ng.conf file at /usr/local/etc/syslog-ng.conf.
Therefore, if we make changes to the following line of code in syslog-ng.conf file: "log { source(src); filter(f_err); destination(console); };";
by changing the destination from console to a new file, it redirects all the mDNSResponder messages to the new file.

I supposed one could edit the syslog-ng.conf file themselves and try, but I am not. :)

 

[Cybix]

@Big Dave & Cybix,
could you please explain me this error. I am unable to get rid of this after many tries. need solution for this problem.
can mail me personally also on manojkply@gmail.com.
waiting for your response mates.

Hi manojkply

I ended updating to a newer version of Freenas, 9.10 (FreeNAS-9.10-STABLE-201604140622)
*Started with this Image and currently updated to "FreeNAS-9.10-STABLE-201606270534" (not the latest version)

As "Mirfster says below: "It is just due to that being a chatty protocol"

For me updating sorted out my problem but killed LACP but I think my HP switch has something to do with this :(

Sorry for the late reply

Hope that helps
Cybix