Q: After cloning hard drive from backup ARD won't launch
OS: 10.11.6 (issue happened on 10.11.5 as well; updated today to see if that helped)
I recently reformatted my hard drive to fix some wacky partitioning I'd been playing with and cloned my drive back from a CCC direct clone. I also recreated my Recovery partition, setup Boot Camp, and installed Windows.
I then went to go launch Remote Desktop and received the following error:
Being a logical person, I uninstalled the app using the steps here, reinstalled, and launched it again... to get the same error.
At this point I Google'd a bit and found mention of a permissions issue that was causing other folks to have the same issue. I checked my log and lo and behold, I had the same errors:
The hard and fast solution appeared to be to delete that folder and recreate it. First, I did this by logging into the Recovery partition and deleting the "C" folder via Terminal so I didn't have to turn off System Integrity checks. This resulting in no change on a reboot, even after doing it again, uninstalling Remote Desktop, then reinstalling.
Next, I turned off System Integrity (csrutil disable) in Recovery and booted to delete it while booted. I ran through the same hoops as above because it continuously didn't work.
I even went so crazy far just now as to delete the top level folder instead of just the "C" subfolder. That didn't work either. I changed permissions on the folder to 777. No change. Changed the owner to my user account since it doesn't prompt for an admin account. No change.
I went to the ARD support page and tried submitting an actual ticket, but turns out that ARD isn't in the list of software that you can drop a ticket on.
I'm out of ideas. Any chance someone can provide some guidance?
MacBook Pro, OS X El Capitan (10.11.6), 13-inch, Mid 2012, 1TB SSD, 8GB
Posted on Jul 22, 2016 9:41 AM
Hi Mike,
I think that leaving this at "faulty clone" could give future readers the wrong idea; maybe we can elaborate on that? Based on the console errors in your original post and the context of the other users that have replied (some resolving the issue, some reporting that things worked fine while booted from the backup), it seems like this issue is inconsistent, and probably a bug in ARD -- if there's a problem creating a cache directory, they should be able to fix that. I don't think there's an issue creating that cache folder, though. You said off the bat that you deleted that "C" folder, so the fact that it was already present would suggest that the "confstr" error result was invalid (e.g. it shouldn't attempt to create that folder if it already exists, and it shouldn't get a "permission denied" error if it's running as root).
Looking closer at the "confstr" API, it looks like that function will attempt to create the folder if it doesn't exist. The error returned was "permission denied". So that begs the questions: a) Is the ARD Agent supposed to run as root, and if it is running as root, why was it unable to create a folder in the root user cache directory?, b) if ARD Agent is not running as root, why would confstr return the root-user cache directory location rather than the ARD Agent user-specific cache directory (or that of the logged-in user)?, and c) why would confstr return a "permission denied" error when the specified cache folder ("/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/C/") did actually exist and the process was running as root? There has to be more to this than simply an error creating the cache folder.
Another, perhaps simpler troubleshooting method arose when I was reading up on confstr:
_CS_DARWIN_USER_CACHE_DIR
Provides the path to the user's cache directory. The directory will be created if it does not already exist. This direc-
tory is created with access permissions of 0700 and restricted by the umask(2) of the calling process and is a good
location for user cache data as it will not be automatically cleaned by the system.
Files in this location will be removed during safe boot.
If the solution turns out to be deleting that cache folder, perhaps ARD would work just fine after an initial Safe Boot run.
As an aside, if you're having any other issues while booted from the backup (or from a restored volume), please don't hesitate to engage us via the "Report a problem" menu item in CCC's help menu.
Mike
Posted on Aug 2, 2016 10:38 AM



