[1/2 solved] avahi-daemon Invalid response packet from host

The rsyslog.conf is still there with the extra lines that I added, but somehow I still get the same error: avahi-daemon Invalid response packet from host

#
# Where to place spool and state files
#
$WorkDirectory /var/spool/rsyslog


#
# Include all config files in /etc/rsyslog.d/
#
$IncludeConfig /etc/rsyslog.d/*.conf


###############
#### RULES ####
###############


#
# First some standard log files.  Log by facility.
#
auth,authpriv.*                 /var/log/auth.log
:msg, contains, "Invalid response packet from host" stop
*.*;auth,authpriv.none          -/var/log/syslog
#cron.*                         /var/log/cron.log
daemon.*                        -/var/log/daemon.log
kern.*                          -/var/log/kern.log
lpr.*                           -/var/log/lpr.log
mail.*                          -/var/log/mail.log
user.*                          -/var/log/user.log


#
# Logging for the mail system.  Split it up so that
# it is easy to write scripts to parse these files.
#
mail.info                       -/var/log/mail.info
mail.warn                       -/var/log/mail.warn
mail.err                        /var/log/mail.err


#

You are right. After the upgrade to v2.1.25, I also started getting those message again. Here are my observations:

• Those messages started after the upgrade.
• The file /etc/rsyslog.conf hasn't been changed.
• After executed the command 'service rsyslog restart', those messages stopped.
• Restarted the OMV system, and those messages came back flooding again.
• Ran 'service rsyslog restart' to silence those message.

They seem to suggest that OMV uses a different config file for rsyslogd when starting. Once restarting rsyslogd with the regular config file, the modification for ignoring that message takes effect.

I will look into OMV's source codes to see whether my hypothesis is correct or not.

I"m not sure what happened, but after I switched 3.16 to 3.2.0 kernel, I don't get the error message anymore.

After some investigations into this problem, I can definitely say that it is NOT caused by OMV. In fact, it's a bug in the codes of certain versions of Windows (my culprit is a Windows Server 2012) which respond to mDNS requests. Microsoft seems have patched it up in Windows 10 already but not Windows Server 2012.

Here are some ways to fix it:

• Wait for Microsoft to patch up the bug in your version of Windows. In the mean time you can try remove all shared printers on your Windows hosts that cause the messages.
• Upgrade your avahi-daemon to version 0.6.32rc. This version includes a patch for ignoring bad responses from Windows, but is not a stable release and still under development. (This should be the eventual solution when rsyslog 0.6.32 becomes stable.)
• Stop avahi-daemon all together on your OMV. However, some parts of OMV and its plugins use avahi, so that may break some functionalities.
• Modify /etc/rsyslog.conf to ignore those messages as outlined in my earlier post. NOTE: for some unknown reasons rsyslog on some Linux boxes doesn't honor /etc/rsyslog.conf at system boot-up. A restart of rsyslog is required every time the system reboots to let change take effect. (See below for an init script to do it automatically.

I don't see why it worked, but tinh_x7 reported switching the kernel to 3.2.0 fixed the problem of unwanted messages. My OMV box has kernel 3.2.0-4-kirkwood and is experiencing this problem.

If you'd like to use method 4 and the rsyslog on your Linux box doesn't honor /etc/rsyslog.conf at boot, then add this init script as /etc/init.d/restart-rsyslog to your system:

#! /bin/sh
### BEGIN INIT INFO
# Provides:          restart-rsyslog
# Required-Start:    $remote_fs $all
# Required-Stop:
# Default-Start:     2 3 4 5
# Default-Stop:
# Short-Description: Restart rsyslog
# Description:       Need to restart rsyslog to properly
#                    read rsyslog.conf.
### END INIT INFO


NAME=restart-rsyslog
DAEMON=/usr/sbin/rsyslogd


[ -x "$DAEMON" ] || exit 0


case "$1" in
  start)
        /etc/init.d/rsyslog restart
        ;;
  stop|restart|force-reload)
        # No-op
        ;;
  status)
        exec /etc/init.d/rsyslog status
        ;;
  *)
        echo "Usage: $NAME {start|stop|restart|force-reload}" >&2
        exit 3
        ;;
esac

Then enter this command to activate it:

# update-rc.d restart-rsyslog defaults

And verify it:

# find /etc/rc?.d -name '*restart-rsyslog*'

It worked for a while, but not it isn't.
Regardless whether I'm using either kernel, I'm getting the warning message.

How do I update this Avahi?

Avahi 0.6.32-1 has just been released into sid repository. Since sid is the development repository and unstable, using it might cause issues on your system. Currently there are no backports for jessie or wheezy.

The new version changelog showing that fix has been fixed.

Hi.

I now also get this message in my syslog.

avahi-daemon[3126]: Invalid response packet from host

The given ip-address is coming from an Amazon Fire TV stick in my WLAN. Any ideas?

Regards lulu

FYI: I'm using the latest kernel 4.8.6, and so far it working fine.
Don't get this error anymore.

Kernel 4.8.6? Where can I read this out?

I just compiled & uploaded yesterday: http://forum.openmediavault.or…ernel-4-x-Image/?pageNo=6

This is for OMV2 system only.

Download & install it in your system.

sudo dpkg -i linux-headers* linux-image*

Ah ok. Thanks.

But I don't get this. I have 2 Amazon Fire TV Sticks and one normal Fire TV. But only one is giving me this message in the syslog. I powered it off. No problems coming from the other 2. I switched power on again and get the message from this stick again. Very strange.....

Ok, I now tried further to see what the problem could be. I now did a factory reset on this Fire TV stick and after putting it back in the WLAN no further messages concerning avahi-daemon are coming from the stick.

So if somebody gets the avahi-daemon message in syslog coming from an Amazon Fire TV stick a factory reset seems to fix that problem!

Regards lulu

This error still occur on 3.0.59.