Bnicke

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Posted in:
  • 16. September 2015 at 18:31 #15713

    Well, the log is from a A+ (no LAN interface) so it will be a little difficult.
    It still dont explain why my other Pi (an A) with only a LAN cable have the same problem.. after about the same time.
    I dont see the „Withdrawing address“ message for eth0 on my version A.

    The odd thing is that it has been working since I powered off the Windows 10 machine after my last post even though my wife booted it again next evening. I still have those „avahi-daemon: Invalid response packet from host“ in the logs on both Pies when her computer is on but it is still working.
    Both Raspberrys have been up since then, I dare not restart them.
    I replicated the crach/hang/disable/e.g behavior at least 10 times before posting it here.

    • This reply was modified 6 years ago by  Bnicke.
    14. September 2015 at 23:00 #15672

    No.. I use the internal analog jack of the Pi.. no HDMI attached.
    I tried to expand the filesysten, same issue.

    However, I snooped around in the log files after it disappeared from the iPhone and found this in deamon.log:

    First the startup: (I named it Kitchen)
    Sep 13 20:34:01 Kitchen avahi-daemon[2180]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.104.
    Sep 13 20:34:01 Kitchen avahi-daemon[2180]: New relevant interface wlan0.IPv4 for mDNS.
    Sep 13 20:34:01 Kitchen avahi-daemon[2180]: Registering new address record for 192.168.0.104 on wlan0.IPv4.

    Then after a while:
    Sep 13 20:58:12 Kitchen avahi-daemon[2180]: Invalid response packet from host 192.168.0.114.
    Sep 13 20:58:12 Kitchen avahi-daemon[2180]: Invalid response packet from host 192.168.0.114.

    Sep 13 22:04:31 Kitchen avahi-daemon[2180]: Withdrawing address record for 192.168.0.104 on wlan0.
    Sep 13 22:04:31 Kitchen avahi-daemon[2180]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.104.
    Sep 13 22:04:31 Kitchen avahi-daemon[2180]: Interface wlan0.IPv4 no longer relevant for mDNS.
    ….
    Sep 14 22:08:06 Kitchen avahi-daemon[2310]: Invalid response packet from host 192.168.0.114.
    Sep 14 22:08:07 Kitchen avahi-daemon[2310]: Invalid response packet from host 192.168.0.114.
    Sep 14 22:08:08 Kitchen avahi-daemon[2310]: Invalid response packet from host 192.168.0.114.
    Then silence from the avahi-daemon in the log.

    192.168.0.114 is a my wife’s Windows 10 machine..
    I also saw the same log entries from another IP that is my sons gaming computer.. also running Windows 10.
    I have a Windows 7 and Macbook but there are no „Invalid packets“ from their IP-adresses.

    I can not pinpount that it stopped working right at 22:08 or 22:04 e.g., I was watching the latest episode of Fear the Walking Dead but it worked before and afterwards it did not (approx. 22:28 and an episode is about 45 minutes)
    It is probably something bad that Windows 10 does to the service discovery on the max2play pi.
    I will shut the Win 10 PC down, restart the shairport deamon and see if it still working in the morning.

    • This reply was modified 6 years ago by  Bnicke.
Viewing 2 posts - 1 through 2 (of 2 total)