Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

SOLVED Time Machine no longer working

Western Digital Drives - The Preferred Drives of FreeNAS and TrueNAS CORE
Status
Not open for further replies.

james88

Neophyte
Joined
Jun 26, 2017
Messages
11
Hi there,

I have had my trusty FreeNAS server working well for several years now - it handles most tasks and used to be my time machine server for my Mac too.

However at the beginning of this year the Time Machine backups suddenly started working after I updated to 9.10.2-U2. In spite of reverting to 9.10.2-U1 they have never started working again. I updated to FreeNAS 11 today which is looking great. The AFP shares are all still present and AFP is shown as working, but Time Machine backups are still broken. What is noticeable is that:

1. If I manually connect to the AFP share from my Mac using Finder, I can browse the share just fine, so AFP is working.
2. Time Machine never gets past the "Looking for backup disk..." phase.
3. My FreeNAS server no longer appears in the list of Shared devices in Finder.

I am not on a separate VLAN or network, and my Mac Mini still shows up in Finder so my initial thinking (if I am correct) is that this is related to mdns? I'm not sure how to debug or fix this - can anyone point me in the right direction to get this resolved? Happy to supply logs, screenshots, and whatever else is needed.

Kind regards,

James
 

james88

Neophyte
Joined
Jun 26, 2017
Messages
11
Ok it turns out the problem was an unused network adapter on my file server. I added a 4-port NIC last year to test out the performance of using a separate network for storage traffic. I have since abandoned the idea, and left the NIC unconnected - however I left the configuration in FreeNAS.

From looking at the mdnsresponder.log file, if you start AFP with a NIC configured but unconnected, you get this kind of output:
```
Jan 16 14:51:35 freenas2 mDNSResponder: mDNSResponder (Engineering Build) (Jan 11 2017 17:19:08) starting
Jan 16 14:51:35 freenas2 mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Jan 16 14:51:35 freenas2 mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Jan 16 14:51:35 freenas2 mDNSResponder: CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for PCP & NAT-PMP announcements
Jan 24 23:34:40 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:34:42 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:34:45 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:34:46 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:34:46 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:34:46 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:34:47 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:34:49 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:34:53 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:03 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:04 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:04 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:04 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:05 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:06 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:08 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:12 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:12 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:14 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:15 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:15 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:15 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:15 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:16 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:18 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:39:23 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:46:03 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:46:04 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:46:04 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:46:04 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:46:04 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:46:05 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:46:07 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60/em3/4
Jan 24 23:46:11 freenas2 mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.25.60
```

Even if you configure AFP to bind to a specific interface, it mdnsd still tries to use the unconnected adapter, and the failures on this adapter seem to prevent it from working on the connected adapter.

Not sure if this is a bug - it certainly is an edge case.

Hope this helps someone out there....

James
 
Status
Not open for further replies.
Top