NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS NV+ and Lion problem with mDNS and avahi
This is from daemon.log. I first experienced problems with machine that was updated from Snow Leopard, but now it seems the fresh Lion installation also pulls ReadyNAS NV+ (sparc) out of network existence. This is 4.1.8 software problem, not Lion per se. Looks like avahi is somehow vulnerable to mDNS lookups and forces ReadyNAS NV+ to hang all services.
It probably can be fixed from Lion DNS resolution side, but it does not work like in previous Mac OS X versions. I am stuck. Anyone met this issue?
When I connect Lion machine to ReadyNAS NV+ share, it soon make it hang. This is repeated issue.
It probably can be fixed from Lion DNS resolution side, but it does not work like in previous Mac OS X versions. I am stuck. Anyone met this issue?
When I connect Lion machine to ReadyNAS NV+ share, it soon make it hang. This is repeated issue.
Jan 4 12:21:27 nas-89-AF-E6 init: Switching to runlevel: 0
Jan 4 12:23:30 nas-89-AF-E6 avahi-daemon[978]: Found user 'admin' (UID 98) and group 'admin' (GID 98).
Jan 4 12:23:30 nas-89-AF-E6 avahi-daemon[978]: Successfully dropped root privileges.
Jan 4 12:23:30 nas-89-AF-E6 avahi-daemon[978]: avahi-daemon 0.6.15 starting up.
Jan 4 12:23:30 nas-89-AF-E6 avahi-daemon[978]: Loading service file /etc/avahi/services/readynas.service.
Jan 4 12:23:30 nas-89-AF-E6 avahi-daemon[978]: New relevant interface eth0.IPv4 for mDNS.
Jan 4 12:23:30 nas-89-AF-E6 avahi-daemon[978]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.55.
Jan 4 12:23:30 nas-89-AF-E6 avahi-daemon[978]: Network interface enumeration completed.
Jan 4 12:23:30 nas-89-AF-E6 avahi-daemon[978]: Registering new address record for 192.168.0.55 on eth0.
Jan 4 12:23:30 nas-89-AF-E6 avahi-daemon[978]: Registering HINFO record with values 'PADRE'/'LINUX'.
Jan 4 12:23:31 nas-89-AF-E6 avahi-daemon[978]: Server startup complete. Host name is nas-89-AF-E6.local. Local service cookie is 336001692.
Jan 4 12:23:32 nas-89-AF-E6 avahi-daemon[978]: Service "ReadyNAS Discovery [nas-89-AF-E6]" (/etc/avahi/services/readynas.service) successfully established.
Jan 4 12:24:00 nas-89-AF-E6 avahi-daemon[978]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 4 12:24:00 nas-89-AF-E6 avahi-daemon[978]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.55.
Jan 4 12:24:00 nas-89-AF-E6 avahi-daemon[978]: Withdrawing address record for 192.168.0.55 on eth0.
Jan 4 12:24:01 nas-89-AF-E6 avahi-daemon[978]: New relevant interface eth0.IPv4 for mDNS.
Jan 4 12:24:01 nas-89-AF-E6 avahi-daemon[978]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.55.
Jan 4 12:24:01 nas-89-AF-E6 avahi-daemon[978]: Registering new address record for 192.168.0.55 on eth0.
Jan 4 12:24:22 nas-89-AF-E6 avahi-daemon[978]: Withdrawing address record for 192.168.0.55 on eth0.
Jan 4 12:24:22 nas-89-AF-E6 avahi-daemon[978]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.55.
Jan 4 12:24:22 nas-89-AF-E6 avahi-daemon[978]: iface.c: interface_mdns_mcast_join() called but no local address available.
Jan 4 12:24:22 nas-89-AF-E6 avahi-daemon[978]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 4 12:24:22 nas-89-AF-E6 avahi-daemon[978]: New relevant interface eth0.IPv4 for mDNS.
Jan 4 12:24:22 nas-89-AF-E6 avahi-daemon[978]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.55.
Jan 4 12:24:22 nas-89-AF-E6 avahi-daemon[978]: Registering new address record for 192.168.0.55 on eth0.
Jan 4 12:24:39 nas-89-AF-E6 upnpd(eth0)[1582]: Listening on 192.168.0.55:50000
Jan 4 12:24:39 nas-89-AF-E6 upnpd(eth0)[1582]: setsockopt - IP_ADD_MEMBERSHIP: Address already in use
Jan 4 12:24:39 nas-89-AF-E6 upnpd(eth0)[1582]: Failed to add membership for address 192.168.0.55
9 Replies
Replies have been turned off for this discussion
- There have been a number of reports of what appear to be mDNS issues in 4.1.8 - usually the symptom initially noticed is an inability to connect to the TimeMachine service.
I've yet to see any response from Netgear, and the latest beta (4.1.9) does not reference any fix. Primary workaround is to connect manually via IP address - Can you submit your full logs (via link in my sig)?
The runlevel 0 note at the top of your logs above would signal a system shutdown, so those avahi messages are normal in that state. sphardy wrote: Primary workaround is to connect manually via IP address
When you do that, ReadyNAS NV+ (spare) with 4.1.8 software will go out of network in around 20 seconds because of the same issue.
Also, just discovered. A new Lion machine on opening in the network with such ReadyNAS device will also make it stop responding.Jan 5 10:31:46 nas-89-AF-E6 init: Switching to runlevel: 0
Jan 5 10:33:35 nas-89-AF-E6 avahi-daemon[989]: Found user 'admin' (UID 98) and group 'admin' (GID 98).
Jan 5 10:33:35 nas-89-AF-E6 avahi-daemon[989]: Successfully dropped root privileges.
Jan 5 10:33:35 nas-89-AF-E6 avahi-daemon[989]: avahi-daemon 0.6.15 starting up.
Jan 5 10:33:35 nas-89-AF-E6 avahi-daemon[989]: Loading service file /etc/avahi/services/readynas.service.
Jan 5 10:33:35 nas-89-AF-E6 avahi-daemon[989]: New relevant interface eth0.IPv4 for mDNS.
Jan 5 10:33:35 nas-89-AF-E6 avahi-daemon[989]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.55.
Jan 5 10:33:35 nas-89-AF-E6 avahi-daemon[989]: Network interface enumeration completed.
Jan 5 10:33:36 nas-89-AF-E6 avahi-daemon[989]: Registering new address record for 192.168.0.55 on eth0.
Jan 5 10:33:36 nas-89-AF-E6 avahi-daemon[989]: Registering HINFO record with values 'PADRE'/'LINUX'.
Jan 5 10:33:37 nas-89-AF-E6 avahi-daemon[989]: Server startup complete. Host name is nas-89-AF-E6.local. Local service cookie is 743080681.
Jan 5 10:33:38 nas-89-AF-E6 avahi-daemon[989]: Service "ReadyNAS Discovery [nas-89-AF-E6]" (/etc/avahi/services/readynas.service) successfully established.
Jan 5 10:34:03 nas-89-AF-E6 avahi-daemon[989]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 5 10:34:03 nas-89-AF-E6 avahi-daemon[989]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.55.
Jan 5 10:34:03 nas-89-AF-E6 avahi-daemon[989]: Withdrawing address record for 192.168.0.55 on eth0.
Jan 5 10:34:04 nas-89-AF-E6 avahi-daemon[989]: New relevant interface eth0.IPv4 for mDNS.
Jan 5 10:34:04 nas-89-AF-E6 avahi-daemon[989]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.55.
Jan 5 10:34:04 nas-89-AF-E6 avahi-daemon[989]: Registering new address record for 192.168.0.55 on eth0.
Jan 5 10:34:24 nas-89-AF-E6 avahi-daemon[989]: Withdrawing address record for 192.168.0.55 on eth0.
Jan 5 10:34:24 nas-89-AF-E6 avahi-daemon[989]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.55.
Jan 5 10:34:24 nas-89-AF-E6 avahi-daemon[989]: iface.c: interface_mdns_mcast_join() called but no local address available.
Jan 5 10:34:24 nas-89-AF-E6 avahi-daemon[989]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 5 10:34:24 nas-89-AF-E6 avahi-daemon[989]: New relevant interface eth0.IPv4 for mDNS.
Jan 5 10:34:24 nas-89-AF-E6 avahi-daemon[989]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.55.
Jan 5 10:34:24 nas-89-AF-E6 avahi-daemon[989]: Registering new address record for 192.168.0.55 on eth0.
Jan 5 10:34:44 nas-89-AF-E6 upnpd(eth0)[1574]: Listening on 192.168.0.55:50000
Jan 5 10:34:44 nas-89-AF-E6 upnpd(eth0)[1574]: setsockopt - IP_ADD_MEMBERSHIP: Address already in use
Jan 5 10:34:44 nas-89-AF-E6 upnpd(eth0)[1574]: Failed to add membership for address 192.168.0.55
My current workaround is adding reverse resolution for local name of Lion host (editing /etc/hosts , see recent post at ommunist.com). But it does not solve the issue of ReadyNAS NV+ falling down if that machine restarts. Avahi goes down after that anyway :-(((chirpa wrote: Can you submit your full logs (via link in my sig)?
Sent you logs. Pray you enlighten me.- Partially situation is resolved by adding manually reverse resolution for localhost in /etc/hosts on Lion machine. After that it does not hang ReadyNAS NV+ with 4.1.8 until restart. On its restart it will bring network services on ReadyNAS down. So this is only half of the solution.
Can something be done on ReadyNAS device side? chirpa wrote: Can you submit your full logs (via link in my sig)?
The runlevel 0 note at the top of your logs above would signal a system shutdown, so those avahi messages are normal in that state.
ReadyNAS NV+ (sparc) still goes down with Lion machine restarts or wakes on network. Should I send you more logs?
I have to manually restart ReadyNAS at least once a day to get it working and our small office is really frustrated, since this device is a small group file server.- Do you have Jumbo frame devices on the network? The system is receiving packets larger than the RX buffer, causing a buffer overrun. If you have Jumbo frame devices in use, can you try enabling Jumbo frames on the NAS itself (FV>Network>Interfaces)?
What switch/hub do you have the NAS connected to? I see you have speed/duplex forced to 100/Full Duplex. Why not using Auto, to get 1000?
Also, for what purpose was the MTU set to 1430? Do you have Vista/7 Wireless devices, and tried using the workaround posted by a few forum users? chirpa wrote: Do you have Jumbo frame devices on the network? The system is receiving packets larger than the RX buffer, causing a buffer overrun. If you have Jumbo frame devices in use, can you try enabling Jumbo frames on the NAS itself (FV>Network>Interfaces)?
What switch/hub do you have the NAS connected to? I see you have speed/duplex forced to 100/Full Duplex. Why not using Auto, to get 1000?
Also, for what purpose was the MTU set to 1430? Do you have Vista/7 Wireless devices, and tried using the workaround posted by a few forum users?
I'll check for devices that can possibly send Jumbo frames.
Its a gigabit switch/router.
Yes, I tried that. Win7 workstation which had the only option to be connected wirelessly had problems and setting MTU solved that.
Also - can buffer overrun be caused by a printer sending MTU larger than 1430?- After enabling jumbo frames it stopped hanging on print from Lion.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
