optiman Posted August 23, 2015 Share Posted August 23, 2015 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? Link to comment
CHBMB Posted August 23, 2015 Share Posted August 23, 2015 It's been well described several times on here recently, fixed in RC5 and the messages are harmless. Link to comment
optiman Posted August 23, 2015 Author Share Posted August 23, 2015 Thanks for replying! Glad it's no big deal. Not sure why my search didn't find any of those posts... Link to comment
trurl Posted August 24, 2015 Share Posted August 24, 2015 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. Link to comment
optiman Posted August 24, 2015 Author Share Posted August 24, 2015 thanks for rubbing it in.... Link to comment
trurl Posted August 24, 2015 Share Posted August 24, 2015 thanks for rubbing it in.... Just trying to help. How to use the search feature here isn't obvious. Link to comment
Squid Posted August 24, 2015 Share Posted August 24, 2015 Just trying to help. How to use the search feature here isn't obvious. Annoying at times actually... Link to comment
trurl Posted August 24, 2015 Share Posted August 24, 2015 Just trying to help. How to use the search feature here isn't obvious. Annoying at times actually... Me, or the search feature? Link to comment
Squid Posted August 25, 2015 Share Posted August 25, 2015 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 Link to comment
CHBMB Posted August 25, 2015 Share Posted August 25, 2015 Hehe, nah trurl, you're alright, we'll keep you around for a bit longer! Link to comment
uldise Posted August 25, 2015 Share Posted August 25, 2015 sorry for asking second time, but are there any workarounds for existing 6.0 version to suppress those messages from syslog? Link to comment
CHBMB Posted August 25, 2015 Share Posted August 25, 2015 Ignore them or upgrade I think are your options. Link to comment
uldise Posted August 25, 2015 Share Posted August 25, 2015 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.. Link to comment
CHBMB Posted August 25, 2015 Share Posted August 25, 2015 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? Link to comment
uldise Posted August 25, 2015 Share Posted August 25, 2015 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 Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.