freenas mDNSResponder: PenaltyTimeForServer: PenaltyTime negative

[unique_suresh]

I am getting the below message and I have no clue what is causing this message to pollute my log. Does any one have any idea why or what is this message about and how to get rid of this.

FreeNAS : 9.10 - 16 GB RAM ECC
Esxi : 6.0 - I/O pass through


------------------- Message from log -------------------------

Jun 9 19:11:40 freenas mDNSResponder: PenaltyTimeForServer: PenaltyTime negative -482283, (server penaltyTime -1105880718, timenow -1105398435) resetting the penalty
Jun 9 19:26:40 freenas mDNSResponder: PenaltyTimeForServer: PenaltyTime negative -482345, (server penaltyTime -1104959142, timenow -1104476797) resetting the penalty
Jun 9 19:41:40 freenas mDNSResponder: PenaltyTimeForServer: PenaltyTime negative -482274, (server penaltyTime -1104037436, timenow -1103555162) resetting the penalty
Jun 9 19:56:40 freenas mDNSResponder: PenaltyTimeForServer: PenaltyTime negative -482238, (server penaltyTime -1103115511, timenow -1102633273) resetting the penalty
Jun 9 20:11:40 freenas mDNSResponder: PenaltyTimeForServer: PenaltyTime negative -482237, (server penaltyTime -1102193856, timenow -1101711619) resetting the penalty
Jun 9 20:26:40 freenas mDNSResponder: PenaltyTimeForServer: PenaltyTime negative -482292, (server penaltyTime -1101272243, timenow -1100789951) resetting the penalty
Jun 9 20:41:41 freenas mDNSResponder: PenaltyTimeForServer: PenaltyTime negative -482437, (server penaltyTime -1100350737, timenow -1099868300) resetting the penalty
Jun 9 20:56:41 freenas mDNSResponder: PenaltyTimeForServer: PenaltyTime negative -482458, (server penaltyTime -1099429104, timenow -1098946646) resetting the penalty
Jun 9 21:11:41 freenas mDNSResponder: PenaltyTimeForServer: PenaltyTime negative -482465, (server penaltyTime -1098507346, timenow -1098024881) resetting the penalty
Jun 9 21:26:41 freenas mDNSResponder: PenaltyTimeForServer: PenaltyTime negative -482090, (server penaltyTime -1097585354, timenow -1097103264) resetting the penalty


-----------------------------------------------------------------
Thanks

 

[Mirfster]

Think that it can be ignored. I get a ton of them as well, not exactly the same as yours but still coming from "mDNSResponder"

https://bugs.freenas.org/issues/14448

Updated by Jordan Hubbard about 2 months 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.

 

[unique_suresh]

Thanks @Mirfster. It gonna take a while to be fixed since its marked to nice to have. Seems not risky one.

 

[James Ganong]

i send these messages to a file instead of my console.
i editted /etc/sylog.conf like so:

Code:

# following line came with freenas,  we replaced it with 8 lines to suppress *.err from mDNSResponder
# *.err;kern.warning;auth.notice;mail.crit			  /dev/console
# do not send err messages from mDNSReponder to console
kern.warning;auth.notice;mail.crit			  /dev/console  # omit *.err from original line
!mDNSResponder
*.*											 /var/log/mDNSResponder  # all mDNDResponder to file
!*
!-mDNSResponder
*.err										   /dev/console  # all other *.err to console
!*

after doing this edit, i did:

Code:

sudo touch /var/log/mDNSResponder
sudo pkill -9 syslogd
sudo /etc/rc.d/syslogd onestart

then i tested it:

Code:

logger -p 'daemon.err' -t 'mDNSResponder' hello

nothing shows up on the console, but it gets logged in /var/log/mDNSResponder

 

[Mirfster]

i editted /etc/sylog.conf like so:

Wondering if that survive a reboot or updates?

 

[James Ganong]

yes it still works after a reboot, i have tested it.
i do not know for sure about an update.