Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

mDNSResponder stuck in restart loop

Hello all,


I have a mid 2011 Mac Mini (Macmini5,2) running OS X 10.9 (13A603). I started having Time Machine issues where TM could still find my ReadyNAS NV+ server; however, it would no longer bring up the login window. (Note that I am running successful TM backups of a MBP without issue, and I can still login into the backup share from the Mini via AFP.) I started digging around the console logs and found the following line repeating every ten seconds.


Nov 12 08:36:07 wolf-av-mini.home mDNSResponder[1401]: mDNSResponder mDNSResponder-522.1.11 (Aug 24 2013 23:49:34) starting OSXVers 13

Nov 12 08:36:07 wolf-av-mini.home mDNSResponder[1401]: launch_data_array_get_count(skt) returned 0

Nov 12 08:36:07 wolf-av-mini.home mDNSResponder[1401]: No unicast UDP responses

Nov 12 08:36:07 wolf-av-mini.home mDNSResponderHelper[716]: Unauthorized access by euid=502 pid=1401

Nov 12 08:36:07 wolf-av-mini.home mDNSResponder[1401]: mDNSKeychainGetSecrets: 2302 0x8FE (Not authorized)

Nov 12 08:36:07 wolf-av-mini.home mDNSResponder[1401]: SetDomainSecrets: mDNSKeychainGetSecrets failed error 2302 CFArrayRef 0000000000000000

Nov 12 08:36:07 wolf-av-mini.home mDNSResponder[1401]: D2D_IPC: Loaded

Nov 12 08:36:07 wolf-av-mini.home mDNSResponder[1401]: D2DInitialize succeeded

Nov 12 08:36:07 wolf-av-mini.home mDNSResponder[1401]: ERROR: bind(listenfd, (struct sockaddr *) &laddr, sizeof(laddr)); failed: 48 (Address already in use)

Nov 12 08:36:07 wolf-av-mini.home mDNSResponder[1401]: ERROR: udsserver_init: 48 (Address already in use)

Nov 12 08:36:07 wolf-av-mini.home mDNSResponder[1401]: Daemon start: udsserver_init failed

Nov 12 08:36:07 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder[1401]): Exited with code: 255

Nov 12 08:36:07 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder): Throttling respawn: Will start in 10 seconds


My attempts to solve this issue included unloading and loading the mDNSRespond plist, flushing the DNS cache with SIGHUP, installing the latest NV+ firmware, and even downloading the full Mavericks install and running it twice, all to no avail. Curiously, Safari and iTunes are not obviously affected by this issue (or they're just more resiliant than TM.)


Anyway, could someone please assist me with this Time Machine and mDNSResponder issue. For reference, the full system.log transcript of the selection the TM server is below.


Thanks,

Ira



Nov 12 09:06:12 wolf-av-mini.home WindowServer[135]: WSSetSharedWindowState: Window 84 is not buffered; Only buffered windows may be shared

Nov 12 09:06:12 wolf-av-mini.home com.apple.prefs.backup.remoteservice[575]: CGSSetWindowSharingState

Nov 12 09:06:12 wolf-av-mini.home WindowServer[135]: window 54 is already attached to window 52

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: mDNSResponder mDNSResponder-522.1.11 (Aug 24 2013 23:49:34) starting OSXVers 13

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: launch_data_array_get_count(skt) returned 0

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: No unicast UDP responses

Nov 12 09:06:13 wolf-av-mini.home mDNSResponderHelper[716]: Unauthorized access by euid=502 pid=1635

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: mDNSKeychainGetSecrets: 2302 0x8FE (Not authorized)

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: SetDomainSecrets: mDNSKeychainGetSecrets failed error 2302 CFArrayRef 0000000000000000

Nov 12 09:06:13 wolf-av-mini.home configd[17]: network changed.

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: D2D_IPC: Loaded

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: D2DInitialize succeeded

Nov 12 09:06:13 wolf-av-mini.home configd[17]: network changed.

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: ERROR: bind(listenfd, (struct sockaddr *) &laddr, sizeof(laddr)); failed: 48 (Address already in use)

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: ERROR: udsserver_init: 48 (Address already in use)

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: Daemon start: udsserver_init failed

Nov 12 09:06:13 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder[1635]): Exited with code: 255

Nov 12 09:06:13 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder): Throttling respawn: Will start in 10 seconds

Nov 12 09:06:16 wolf-av-mini.home WindowServer[135]: window 1ec is already attached to window 52

Nov 12 09:06:16 wolf-av-mini.home WindowServer[135]: _CGXGetWindowOrderingGroup: Operation on a window 0x54 requiring rights 0x5 by caller System Preferences

Nov 12 09:06:23 wolf-av-mini.home mDNSResponder[1638]: mDNSResponder mDNSResponder-522.1.11 (Aug 24 2013 23:49:34) starting OSXVers 13

Nov 12 09:06:23 wolf-av-mini.home mDNSResponder[1638]: launch_data_array_get_count(skt) returned 0

Nov 12 09:06:23 wolf-av-mini.home mDNSResponder[1638]: No unicast UDP responses

Nov 12 09:06:23 wolf-av-mini.home mDNSResponderHelper[716]: Unauthorized access by euid=502 pid=1638

Nov 12 09:06:23 wolf-av-mini.home mDNSResponder[1638]: mDNSKeychainGetSecrets: 2302 0x8FE (Not authorized)

Nov 12 09:06:23 wolf-av-mini.home mDNSResponder[1638]: SetDomainSecrets: mDNSKeychainGetSecrets failed error 2302 CFArrayRef 0000000000000000

Nov 12 09:06:23 wolf-av-mini.home configd[17]: network changed.

Nov 12 09:06:23 wolf-av-mini.home mDNSResponder[1638]: D2D_IPC: Loaded

Nov 12 09:06:23 wolf-av-mini.home mDNSResponder[1638]: D2DInitialize succeeded

Nov 12 09:06:23 wolf-av-mini.home configd[17]: network changed.

Nov 12 09:06:23 wolf-av-mini.home mDNSResponder[1638]: ERROR: bind(listenfd, (struct sockaddr *) &laddr, sizeof(laddr)); failed: 48 (Address already in use)

Nov 12 09:06:23 wolf-av-mini.home mDNSResponder[1638]: ERROR: udsserver_init: 48 (Address already in use)

Nov 12 09:06:23 wolf-av-mini.home mDNSResponder[1638]: Daemon start: udsserver_init failed

Nov 12 09:06:23 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder[1638]): Exited with code: 255

Nov 12 09:06:23 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder): Throttling respawn: Will start in 10 seconds

Nov 12 09:06:33 wolf-av-mini.home mDNSResponder[1639]: mDNSResponder mDNSResponder-522.1.11 (Aug 24 2013 23:49:34) starting OSXVers 13

Nov 12 09:06:33 wolf-av-mini.home mDNSResponder[1639]: launch_data_array_get_count(skt) returned 0

Nov 12 09:06:33 wolf-av-mini.home mDNSResponder[1639]: No unicast UDP responses

Nov 12 09:06:33 wolf-av-mini.home mDNSResponderHelper[716]: Unauthorized access by euid=502 pid=1639

Nov 12 09:06:33 wolf-av-mini.home mDNSResponder[1639]: mDNSKeychainGetSecrets: 2302 0x8FE (Not authorized)

Nov 12 09:06:33 wolf-av-mini.home mDNSResponder[1639]: SetDomainSecrets: mDNSKeychainGetSecrets failed error 2302 CFArrayRef 0000000000000000

Nov 12 09:06:33 wolf-av-mini.home configd[17]: network changed.

Nov 12 09:06:33 wolf-av-mini.home mDNSResponder[1639]: D2D_IPC: Loaded

Nov 12 09:06:33 wolf-av-mini.home mDNSResponder[1639]: D2DInitialize succeeded

Nov 12 09:06:33 wolf-av-mini.home configd[17]: network changed.

Nov 12 09:06:33 wolf-av-mini.home mDNSResponder[1639]: ERROR: bind(listenfd, (struct sockaddr *) &laddr, sizeof(laddr)); failed: 48 (Address already in use)

Nov 12 09:06:33 wolf-av-mini.home mDNSResponder[1639]: ERROR: udsserver_init: 48 (Address already in use)

Nov 12 09:06:33 wolf-av-mini.home mDNSResponder[1639]: Daemon start: udsserver_init failed

Nov 12 09:06:33 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder[1639]): Exited with code: 255

Nov 12 09:06:33 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder): Throttling respawn: Will start in 10 seconds

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: mDNSResponder mDNSResponder-522.1.11 (Aug 24 2013 23:49:34) starting OSXVers 13

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: launch_data_array_get_count(skt) returned 0

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: No unicast UDP responses

Nov 12 09:06:43 wolf-av-mini.home mDNSResponderHelper[716]: Unauthorized access by euid=502 pid=1640

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: mDNSKeychainGetSecrets: 2302 0x8FE (Not authorized)

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: SetDomainSecrets: mDNSKeychainGetSecrets failed error 2302 CFArrayRef 0000000000000000

Nov 12 09:06:43 wolf-av-mini.home configd[17]: network changed.

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: D2D_IPC: Loaded

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: D2DInitialize succeeded

Nov 12 09:06:43 wolf-av-mini.home configd[17]: network changed.

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: ERROR: bind(listenfd, (struct sockaddr *) &laddr, sizeof(laddr)); failed: 48 (Address already in use)

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: ERROR: udsserver_init: 48 (Address already in use)

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: Daemon start: udsserver_init failed

Nov 12 09:06:43 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder[1640]): Exited with code: 255

Nov 12 09:06:43 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder): Throttling respawn: Will start in 10 seconds

Nov 12 09:06:45 wolf-av-mini.home NetAuthSysAgent[1636]: DNSAddressResolver:Resolve CFNetServiceResolveWithTimeout failed

Nov 12 09:06:45 wolf-av-mini.home NetAuthSysAgent[1636]: ERROR: AFP_GetServerInfo - connect failed 64

Nov 12 09:06:48 wolf-av-mini.home com.apple.prefs.backup.remoteservice[575]: Error while confirming network destination: Error Domain=NSOSStatusErrorDomain Code=64 "The operation couldn’t be completed. (OSStatus error 64.)" (kOTSerialFramingErr / EHOSTDOWN: / Host is down)

Nov 12 09:06:48 wolf-av-mini.home WindowServer[135]: WSSetSharedWindowState: Window 84 is not buffered; Only buffered windows may be shared

Nov 12 09:06:48 wolf-av-mini.home com.apple.prefs.backup.remoteservice[575]: CGSSetWindowSharingState

Nov 12 09:06:49 wolf-av-mini.home WindowServer[135]: window 54 is already attached to window 52

Nov 12 09:06:49 wolf-av-mini.home WindowServer[135]: _CGXGetWindowOrderingGroup: Operation on a window 0x1ec requiring rights 0x5 by caller System Preferences

Nov 12 09:06:52 wolf-av-mini.home WindowServer[135]: _CGXGetWindowOrderingGroup: Operation on a window 0x54 requiring rights 0x5 by caller System Preferences

Posted on Nov 12, 2013 6:12 AM

Reply
18 replies

Nov 12, 2013 8:01 AM in response to Ira Wolf 81

WARNING:: I'm not a networking expert but suggest you look at permission issues.


...
Nov 12 08:36:07 wolf-av-mini.home mDNSResponderHelper[716]: Unauthorized access by euid=502 pid=1401
...

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: No unicast UDP responses

Nov 12 09:06:13 wolf-av-mini.home mDNSResponderHelper[716]: Unauthorized access by euid=502 pid=1635

...
Nov 12 09:06:33 wolf-av-mini.home mDNSResponderHelper[716]: Unauthorized access by euid=502 pid=1639
...

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: No unicast UDP responses

Nov 12 09:06:43 wolf-av-mini.home mDNSResponderHelper[716]: Unauthorized access by euid=502 pid=1640

...


It seems as though mDNSResponder keeps restarting using different Process IDs but the user with the UniqueID of 502 does not have the correct permissions to access it. Possible solutions may be to:


1) repair disk permissions

2) delete that particular user's mDNSResponder plist

3) delete the keychain entry for the ReadyNAS NV+ server in case the keychain entry is corrupted. You can always re-enter the credentials and ask it to be remembered the next time it starts

4) The above are easy, but if they all fail to resolve the issue you could repair your installation from the Recovery Mode in case mDNSResponder failed to install correctly.


See instructions on how to do this below:


[https://www.apple.com/uk/osx/recovery/] & About OS X Recovery: [http://support.apple.com/kb/HT4718]

Nov 12, 2013 8:54 AM in response to ViShVa

The last resets the DNS cache and may help your computer connect


Learn how to reset (flush) the DNS cache.


http://support.apple.com/kb/HT5343



Additional Information

When you might want to do this

OS X keeps a local cache of resolved DNS queries for a time defined by the DNS server, but sometimes it may be necessary to reset the cache immediately and re-query a DNS server. For example, you might do this after an entry on the server is changed or a new entry is added.


Last Modified: Aug 7, 2012


Nov 12, 2013 9:26 AM in response to ViShVa

Hello ViShVa,


Thank you for your detailed comments. I previously performed the following steps as well, all to no avail:


1. I did run Repair Disk Permissions.

2. I (foolishly) deleted the mDNSResponder.plist and mDNSResponderHelper.plist, which killed internet access. I used SneakerNet to copy the files from my MBP to the Mini, repaired disk permissions, and then reinstalled Mavericks.

3. I deleted all keychain entries for the NAS.

4. I used the "sudo killall -HUP mDNSResponder" command to send the SIGHUP to mDNSResponder, both when it was loaded and unloaded via the "launchctl {unload|load} -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist" commands.


The only thing I have not yet tried is OS X Recovery; however, how is that any different/better that reinstalling the OS from the App Store?


Thank you,

Ira

Nov 12, 2013 9:59 AM in response to Ira Wolf 81

Ira,


Wow you have done all that already!


A long shot perhaps, but one last thing to try before reinstalling the OS is to repair your Keychain Access. Go to /Applications/Utilities and launch ' Keychain Access'. Go to the "Keychain Access" pulldown menu and select "Keychain First Aid". In the new window enter your password, set the radio button to "Repair", and click "Start". After that quit Keychain Access.


If that fails then I can only suggest you reinstall the OS. To answer your question, if you have a bootable USB Mac OS X 10.9 install drive, it will save you the time and bandwidth of downloading Mavericks all over again. If you do redownload it then try to connect to your router via an ethernet cable instead of Wi-Fi as it will speed up the download.


Good luck and do let us know if you get this sorted.

Nov 12, 2013 1:16 PM in response to ViShVa

Hi and thanks again ViShVa!


I suppose I should say that I am a network engineer, though I work primarily in access/security protocol daemons.


In addition to my aforementioned steps, I also enabled mDNSResponder debug logging with the following commands, however, I still have to learn more about DNS before I could fully understand the output:


// Toggle debug logging for mDNSResponder in /var/log/system.log

sudo killall -USR1 mDNSResponder


// Enable all logging levels for mDNSResponder in /var/log/system.log

sudo syslog -c mDNSResponder -d


I will try your keychain repair technique and make a bootable USB drive to simplify the installs. I'll also move the MacMini to a different part of my network to see if that helps, and change network access from wired to WiFi.


Regards,

Ira

Nov 12, 2013 1:38 PM in response to Ira Wolf 81

One other thought...


The second log entry below from the full transcript above indicates that mDSNResponder could not get any file descriptors during launching, which is perplexing. I'll also check the number of open FDs with lsof later tonight.


Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: mDNSResponder mDNSResponder-522.1.11 (Aug 24 2013 23:49:34) starting OSXVers 13

Nov 12 09:06:13 wolf-av-mini.home mDNSResponder[1635]: launch_data_array_get_count(skt) returned 0


Regards,

Ira

Nov 12, 2013 1:56 PM in response to Ira Wolf 81

Good luck with that! I really don't have a clue so if anyone else reading this can give an insight please chip in!


Besides what you have just posted, some other failures stand out from your log which may be worth investigating:


...

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: ERROR: bind(listenfd, (struct sockaddr *) &laddr, sizeof(laddr)); failed: 48 (Address already in use)

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: ERROR: udsserver_init: 48 (Address already in use)

Nov 12 09:06:43 wolf-av-mini.home mDNSResponder[1640]: Daemon start: udsserver_init failed

Nov 12 09:06:43 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder[1640]): Exited with code: 255

Nov 12 09:06:43 wolf-av-mini com.apple.launchd.peruser.502[172] (com.apple.mDNSResponder): Throttling respawn: Will start in 10 seconds

Nov 12 09:06:45 wolf-av-mini.home NetAuthSysAgent[1636]: DNSAddressResolver:Resolve CFNetServiceResolveWithTimeout failed

Nov 12 09:06:45 wolf-av-mini.home NetAuthSysAgent[1636]: ERROR: AFP_GetServerInfo - connect failed 64

Nov 12 09:06:48 wolf-av-mini.home com.apple.prefs.backup.remoteservice[575]: Error while confirming network destination: Error Domain=NSOSStatusErrorDomain Code=64 "The operation couldn’t be completed. (OSStatus error 64.)" (kOTSerialFramingErr / EHOSTDOWN: / Host is down)

...

I have no clue what they mean though!

Nov 12, 2013 3:36 PM in response to Ira Wolf 81

Ira,


A great tip posted by baltwo to create a bootable install disk can be found here:


baltwo San Diego, CA


http://osxdaily.com/2013/10/23/create-os-x-mavericks-install-drive/

27" i7 iMac SL, MLion, OS X Mavericks (10.9), G4 450 MP w/Leopard, 9.2.2


It may help you...

Nov 13, 2013 8:28 AM in response to ViShVa

Hi ViShVa,


The short story is that I think I found the trouble maker - the Plex Media Server, which was one of my login items.


Now for the longer story...


I tried switching from wired to WiFi and repaired the keychain, both to no avail. I then booted into Safe Mode, but this time I monitored the Console and system.log, which I did not previously do. At this point, there were no mDNSResponder issues in the system.log, even though the Console was reporting them. (The Console entries were about twenty minutes old and were reporting the pre-Safe Mode events - whew!) It then occurred to me to remove the login items from my account, which were iTunes and the Plex Media Server, since they are not run under Safe Mode. I did so and rebooted into Normal Mode, and viola' - no more mDNSResponder errors in system.log! They remained away after launching iTunes manually. This left the Plex Media Server as the culprit.


I'll now go onto the Plex forums to try to resolve its mDNSResponder issue. At least this experience gave me a bootable OXS Mavericks USB for backup, and helped me chose an ATV3 over a Roku3 w/Plex.


Thanks for your continued help!


Regards,

Ira

Nov 13, 2013 9:30 PM in response to Ira Wolf 81

Hi ViShVa,


Well, removing the Plex Media Server from my user login items list stopped mDNSResponder from repeatedly crashing at startup; however, it did not solve my Time Machine issue...


I cleaned everything with Onyx, repaired permissions, re-installed Mavericks (from USB), re-flushed the DNS cache, and I still couldn't get the login prompt for the selected Time Machine disk. Finally, I logged into the TM disk via AFP in the Finder, and only then I was able to select this disk via the TM preference pane.


A TM backup is in progress now. After it completes, I'll eject the TM disk from the Finder and see if TM backups still work.


I still don't know what's really broken or why this workaround works (at least for now.) I suspect there's a defect in the Bonjour/mDNSResponder implementation in Mavericks and/or the ReadyNAS NV+ firmware. Regardless, I've spent more time on this issue that I really should've.


Now onto my work-related issues...


Regards,

Ira

Nov 13, 2013 10:08 PM in response to Ira Wolf 81

Hello,

I ran into what looks like the same problem trying to get TM to work on a ReadyNAS. In my logs I had:


com.apple.prefs.backup.remoteservice[27536]: Error while confirming network destination: Error Domain=NSOSStatusErrorDomain Code=64 "The operation couldn’t be completed. (OSStatus error 64.)" (kOTSerialFramingErr / EHOSTDOWN: / Host is down)


I opened up my key chain tool, and deleted all saved passwords to the readynas.

Then I reconnected with finder to the readynas using the username and password specified in the readynas admin screen. I had previously connected with another user and I think the was the issue. The next time I tried a backup, I saw the disk (as before) but it asked me for a username and password. Once entered TM began to work.

Nov 14, 2013 2:57 AM in response to Ira Wolf 81

Ira,

Ira Wolf 81 wrote:

... Finally, I logged into the TM disk via AFP in the Finder, and only then I was able to select this disk via the TM preference pane.


A TM backup is in progress now. After it completes, I'll eject the TM disk from the Finder and see if TM backups still work.

...

This leads me again to believe it is a POSIX or ACL permissions issue.


derekclee


...

I ran into what looks like the same problem trying to get TM to work on a ReadyNAS. In my logs I had:


com.apple.prefs.backup.remoteservice[27536]: Error while confirming network destination: Error Domain=NSOSStatusErrorDomain Code=64 "The operation couldn’t be completed. (OSStatus error 64.)" (kOTSerialFramingErr / EHOSTDOWN: / Host is down)


... I had previously connected with another user and I think the was the issue. The next time I tried a backup, I saw the disk (as before) but it asked me for a username and password. Once entered TM began to work...



Derek, thanks so much for this. It will help Ira narrow down the issue. The error is the same as Ira has had to connect to the Time Machine via the "backup.remoteservice"


Ira Wolf 81 wrote:


...

I still don't know what's really broken or why this workaround works (at least for now.) I suspect there's a defect in the Bonjour/mDNSResponder implementation in Mavericks and/or the ReadyNAS NV+ firmware

...


It may be working again becaus you logged into the TM via Apple File Protocol with the right credentials, so recognises you again


Let us know how you fared and most importantly whether the TM backup works as expected.

Nov 14, 2013 7:58 AM in response to Ira Wolf 81

HI all,


My initial TM backup succeed after first logging into the ReadyNAS NV+ via AFP in Finder with the TM backup disk credentials (user "ReadyNAS"; password <xxx>). However, after ejecting the ReadyNAS NV+ from Finder, I was unable to log back into it via the TM preference plane.


I finally got TM backups to be stable by making the mounting of the ReadyNAS NV+ via AFP in Finder a login item, which enabled TM to find it without issue and proceed with backups. This solution is similar to what Derek came up with.


I'll dig through the current logs later tonight to see if they are any new errors to persue. Given the relative "newness" of Mavericks, the "oldness" of the NV+, and the past difficulty of Netgear/ReadyNAS adapting its TM support to new OS X versions, I wouldn't be surprised if there's new NV+ firmware version in the works.


One last (perhaps?) thought, even though I stopped launching the Plex Media Server at login, the application is still present on my Mac Mini and could be causing trouble. Grasping at straws, I could deleted the application, reinstall Mavericks, and see if that really solves the issue.


Regards,

Ira

mDNSResponder stuck in restart loop

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.