Running latest unraid v6.0.1

 

getting this error every few secs in the system log.

 

Jul 1 19:11:05 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:29 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:29 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:29 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:29 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:30 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:30 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

 

192.168.1.155 is my main system running latest build of Windows 10

 

I believe this started with the latest unraid version v6.0.1  not sure though.

 

I only noticed this after my unraid would become unresponsive after a day or 2 and needed to be restarted to get it back working.

 

Attached is my system log..

 

Moderator edit: changed icon

tower-syslog-20150701-2154.zip

Running latest unraid v6.0.1

 

getting this error every few secs in the system log.

 

Jul 1 19:11:05 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:29 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:29 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:29 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:29 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:30 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

Jul 1 19:11:30 Tower avahi-daemon[1957]: Invalid response packet from host 192.168.1.155.

 

192.168.1.155 is my main system running latest build of Windows 10

 

I believe this started with the latest unraid version v6.0.1  not sure though.

 

I only noticed this after my unraid would become unresponsive after a day or 2 and needed to be restarted to get it back working.

 

Attached is my system log..

 

AFAIK that service is discovery of network services. Printers et al. Not sure if Unraid uses it for something else or if you have something running that is using it.

 

I have a W10 VM running and I just checked by Syslog and I don't have the same errors you have. Maybe I am not running the same Dockers, Plugins etc you are.

 

If I was a gambling man id say that the W10 machine is broadcasting a service which avahi has discovered (be it File Printer Sharing or similar) and the response it has received does not match what it is expecting.

 

This is just a guess. Could be a Software bug with the service broadcaster? Might be a shot in the dark, but have you applied all patches to the W10 machine?

Yes my windows 10 box has all patches and updates..

 

 

I upgraded one of my computers to Windows 10 on 7/3 with all the latest updates and now I'm seeing these entries in my unRAID 6.0.1 log too.:

 

Jul 6 10:37:52 Tower avahi-daemon[3446]: Invalid response packet from host 192.168.0.2.

 

There are tons of them. It would be nice if it would only log the error once....

There appears to be a patch available to avahi here:

https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1342400

 

But no new version of avahi has been made available with a fix.  It would be nice to be able to at least filter this out of the syslog if nothing else.  It's hard to keep track of incidents with this filling everything up.  I have 3 win10 machines and am getting 6-8 of these a minute.  I missed a disk error i've been getting for almost 3 weeks since this was all that was shown in the syslog.

I have reproduced this in my testing with Windows 10.  Looking into this with the team.

There appears to be a patch available to avahi here:

https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1342400

 

But no new version of avahi has been made available with a fix.  It would be nice to be able to at least filter this out of the syslog if nothing else.  It's hard to keep track of incidents with this filling everything up.  I have 3 win10 machines and am getting 6-8 of these a minute.  I missed a disk error i've been getting for almost 3 weeks since this was all that was shown in the syslog.

 

Our avahi package already includes that patch.  Maybe I'll just go in there an comment out the line that generates the message and be done with it 

That would make the syslog more usefull.  Mine is filling up with this error.

Aug 8 14:54:00 Tower avahi-daemon[1953]: Invalid response packet from host 192.168.1.56.
Aug 8 14:54:00 Tower avahi-daemon[1953]: Invalid response packet from host 192.168.1.66.
Aug 8 14:54:00 Tower avahi-daemon[1953]: Invalid response packet from host 192.168.1.56.
Aug 8 14:54:00 Tower avahi-daemon[1953]: Invalid response packet from host 192.168.1.66.
Aug 8 14:54:00 Tower avahi-daemon[1953]: Invalid response packet from host 192.168.1.56.
Aug 8 14:54:00 Tower avahi-daemon[1953]: Invalid response packet from host 192.168.1.66.
Aug 8 14:54:01 Tower avahi-daemon[1953]: Invalid response packet from host 192.168.1.66.
Aug 8 14:54:01 Tower avahi-daemon[1953]: Invalid response packet from host 192.168.1.56.

There appears to be a patch available to avahi here:

https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1342400

 

But no new version of avahi has been made available with a fix.  It would be nice to be able to at least filter this out of the syslog if nothing else.  It's hard to keep track of incidents with this filling everything up.  I have 3 win10 machines and am getting 6-8 of these a minute.  I missed a disk error i've been getting for almost 3 weeks since this was all that was shown in the syslog.

 

Our avahi package already includes that patch.  Maybe I'll just go in there an comment out the line that generates the message and be done with it 

 

Would it be better to allow the message once, but set a flag and disallow any further output of it?  Bit more work though.

Drawing attention to one users discovery -

 

i think i've found the answer.. i disabled ipv6 on both my win10 computers since i wasn't using it anyway and the avahi-daemon log entries have stopped

Drawing attention to one users discovery -

 

i think i've found the answer.. i disabled ipv6 on both my win10 computers since i wasn't using it anyway and the avahi-daemon log entries have stopped

 

I suppressed the message entirely in 6.1-rc3.

Drawing attention to one users discovery -

 

i think i've found the answer.. i disabled ipv6 on both my win10 computers since i wasn't using it anyway and the avahi-daemon log entries have stopped

 

sorry this was a false alarm

anyone found a fix for this problem? I have noticed tons of these entries in the syslog after i upgraded to windows 10 on my main machine.

 

Invalid response packet from host 192.168.1.4.

(my main win10 pc)

 

om running unRAID 6.0.1

anyone found a fix for this problem? I have noticed tons of these entries in the syslog after i upgraded to windows 10 on my main machine.

 

Invalid response packet from host 192.168.1.4.

(my main win10 pc)

 

om running unRAID 6.0.1

6.1 RC5 suppresses those log entries.  Its a harmless entry.  All it means is that win10 isn't perfect yet (go figure)

Yeah windows 10 is far from "perfect" yet... problems will come and go I guess.

 

The 6.1 RC5 supresses the log entires? so really it just hides them?

 

I'm running 6.0.1 can Install it within unRAID or do I need to format and manually install it? (6.1-rc5)

Yeah windows 10 is far from "perfect" yet... problems will come and go I guess.

 

The 6.1 RC5 supresses the log entires? so really it just hides them?

 

I'm running 6.0.1 can Install it within unRAID or do I need to format and manually install it? (6.1-rc5)

Yeah, you can install it within unRaid.  Just install the plg in the RC5 thread. 

 

and yes RC5 basically just suppresses the entries...  Its a harmless entry.  Basically its just avahi just logging that it received an invalid response to a "question".  Windows isn't providing the correct answer.  Purely a windows issue.  The logging and the error is 100% harmless, but annoying enough that RC5 suppresses it.

Ok, thanks for the information Squid really appreciate it! I'll see if I just "ignore" the entries or update to RC5. The system is running fine right now so I'll probably just Ignore it.

are there any workaround for stable versions of unRAID? i have some Win10 on my network and full syslog of avahi messages..

@uldise-- i don't think there is yet. Only the version 6.1 RC5 which suppresses the log entries. Like Squid said;

Its a harmless entry.  Basically its just avahi just logging that it received an invalid response to a "question".  Windows isn't providing the correct answer.  Purely a windows issue.  The logging and the error is 100% harmless, but annoying enough that RC5 suppresses it.

 

I just chose to ignore it until it gets fixed somehow.

@uldise-- i don't think there is yet. Only the version 6.1 RC5 which suppresses the log entries. Like Squid said;

Its a harmless entry.  Basically its just avahi just logging that it received an invalid response to a "question".  Windows isn't providing the correct answer.  Purely a windows issue.  The logging and the error is 100% harmless, but annoying enough that RC5 suppresses it.

 

I just chose to ignore it until it gets fixed somehow.

@niven, i fixed it by myself as i wrote in another thread, see here: http://lime-technology.com/forum/index.php?topic=42411.msg403715#msg403715

That's awesome, thanks!