August 23, 201510 yr I have 2 pc's that I upgraded to Windows 10. They work fine and so does my Unraid server. However, the syslog is getting hammered with these errors, Aug 23 16:04:32 Tower avahi-daemon[3751]: Invalid response packet from host <pc ip address> I had no errors before upgrading and I have reviewed the network settings and do not see any issues. It seems Unraid does not like Windows 10 pc's on the same LAN. My unraid seems to be working fine, except for these errors. Any ideas?
August 23, 201510 yr It's been well described several times on here recently, fixed in RC5 and the messages are harmless.
August 23, 201510 yr Author Thanks for replying! Glad it's no big deal. Not sure why my search didn't find any of those posts...
August 24, 201510 yr Community Expert Thanks for replying! Glad it's no big deal. Not sure why my search didn't find any of those posts... I just searched for "Invalid response packet from host" and got 35 results. See search tips in my sig.
August 24, 201510 yr Community Expert thanks for rubbing it in.... Just trying to help. How to use the search feature here isn't obvious.
August 24, 201510 yr Just trying to help. How to use the search feature here isn't obvious. Annoying at times actually...
August 24, 201510 yr Community Expert Just trying to help. How to use the search feature here isn't obvious. Annoying at times actually... Me, or the search feature?
August 25, 201510 yr Just trying to help. How to use the search feature here isn't obvious. Annoying at times actually... Me, or the search feature? If I was American, I'd reply that I'm taking the 5th
August 25, 201510 yr sorry for asking second time, but are there any workarounds for existing 6.0 version to suppress those messages from syslog?
August 25, 201510 yr Ignore them or upgrade I think are your options. not an option for me to upgrade. but fixed it by myself, created rsyslog filter, found some examples on internet, not sure it's a correct way but no more tons of messages..
August 25, 201510 yr Ignore them or upgrade I think are your options. not an option for me to upgrade. but fixed it by myself, created rsyslog filter, found some examples on internet, not sure it's a correct way but no more tons of messages.. Why don't you post how so you can help others that may want to do the same?
August 25, 201510 yr Why don't you post how so you can help others that may want to do the same? Here you go, please correct me if needed: - first i created a new file avahi.conf (name is not important) in /etc/rsyslog.d with one line in it: :syslogtag, contains, "avahi-daemon" ~ - then restart rsyslogd by /etc/rc.d/rc.rsyslogd restart and no more messages in syslog from avahi daemon. as side note, a warning is generated for deprecated rsyslog option "~". if someone can correct me how to use this filter with newer "stop" directive, just let me know
Archived
This topic is now archived and is closed to further replies.