com.apple.xpc.launchd & com.apple.mdworker.bundles pollute logs with errors

I made a clean install of Yosemite to MacBook Pro (13-inch, Early 2011), and restored documents and apps from TM backup, no problems so far, but I observe following repeating messages in system log and it concerns me, because apparently, launchd is trying to do something related to spotlight, but fails and this happens every 10 seconds.. I see no suspicious activity apart from too much CPU time spent on mds and mds_stores (but I guess it's due to fresh install, hence Spotlight needs to index everything...).


Any ideas where to dig?


21/10/2557 BE 2:11:43.811 PM com.apple.xpc.launchd[1]: (com.apple.mdworker.bundles[2654]) Could not find uid associated with service: 0: Undefined error: 0 502

21/10/2557 BE 2:11:43.835 PM com.apple.xpc.launchd[1]: (com.apple.mdworker.bundles) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

21/10/2557 BE 2:11:53.838 PM com.apple.xpc.launchd[1]: (com.apple.mdworker.bundles[2655]) Could not find uid associated with service: 0: Undefined error: 0 502

21/10/2557 BE 2:11:53.838 PM com.apple.xpc.launchd[1]: (com.apple.mdworker.bundles) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

[goes forever]

Posted on Oct 21, 2014 12:44 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 27, 2014 3:58 PM

I see, Dustmoo.. I thought the issue was caused by having that account with UID 502 in my main partition. So I dug it a bit more using your example. I actually couldn't find any mdworkers directory in /var. So I looked for the files owned by UID 502 (but it could be any other UID. One must check the last number in the error message, the one I underlined in my first post and use it instead of 502 in the following code):


cd /var

sudo find . -user 502 -exec ls -ld {} \;


This has been the output:


drwx------ 5 michele _spotlight 170 Oct 16 19:10 ./folders/zz/zyxvpxvq6csfxvn_n0000000000000/0/com.apple.Spotlight/502

drwx------ 2 michele _spotlight 68 Oct 16 19:10 ./folders/zz/zyxvpxvq6csfxvn_n0000000000000/0/com.apple.Spotlight/502/0

drwx------ 2 michele _spotlight 68 Oct 16 19:10 ./folders/zz/zyxvpxvq6csfxvn_n0000000000000/0/com.apple.Spotlight/502/C

drwx------ 2 michele _spotlight 68 Oct 16 19:10 ./folders/zz/zyxvpxvq6csfxvn_n0000000000000/0/com.apple.Spotlight/502/T


(michele is my username for UID 502)


So it was still in the /var/folder directory, but something related to or created by Spotlight one week ago. Not sure how it went there, since this was a fresh installation in that partition. It really looks like junk to me.


Just in case I removed the incriminated directory:


cd /private/var/folders/zz/

# I did some directory listing and other things just to check

sudo rm -r zyxvpxvq6csfxvn_n0000000000000

And rebooted. I can't really say if it changed anything because I had already made the new account, but it does look like the culprit.

63 replies

Nov 1, 2014 6:10 AM in response to Andras Dombovari

Yet another false hope. Issue popped up again.


Looking at the log there's Spotlight related errors right before it starts, but not sure what it means. Also, in addition to user ids 04 and 1104188992 I know have a user id 99 in the /private/var/folders... path.


Here's log entries from time period immediately before the mdworker errors associated with 504, note no errors (yet) on other ids.


Nov 1 01:37:45 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Starting index consistency check for /Volumes/Mac HD 320/.Spotlight-V100/Store-V2/E7AA3AF6-80B8-4495-81E5-6F154D834F80

Nov 1 01:37:45 Pro-2 com.apple.xpc.launchd[1] (com.apple.quicklook[2620]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook

Nov 1 01:37:45 Pro-2.local mds[34]: (DiskStore.Normal:1705) Starting health check...

Nov 1 01:37:45 --- last message repeated 5 times ---

Nov 1 01:37:45 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Starting index consistency check for /Volumes/Seagate 2TB/.Spotlight-V100/Store-V2/5EAD3D9D-6C8F-4A7E-92AC-2C219FE707D6

Nov 1 01:37:45 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Starting index consistency check for /Volumes/WD Green 2 TB/.Spotlight-V100/Store-V2/EDC8D163-5B16-43F3-BEFF-F511D3668289

Nov 1 01:37:45 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Starting index consistency check for /Volumes/WD320 Hitachi/.Spotlight-V100/Store-V2/1B85EFB9-D7CF-4687-A58C-A035CC86F027

Nov 1 01:37:45 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Starting index consistency check for /Volumes/WD 2TB G393/.Spotlight-V100/Store-V2/7515D292-486D-4083-8AFD-D70CE411F35D

Nov 1 01:37:45 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Starting index consistency check for /Volumes/WD 2TB G401/.Spotlight-V100/Store-V2/175E4A2D-8C29-4550-AA78-EADD4B814CF6

Nov 1 01:37:46 Pro-2 com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The _DirtyJetsamMemoryLimit key is not available on this platform.

Nov 1 01:37:46 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Starting index consistency check for /Volumes/Seagate 4TB/.Spotlight-V100/Store-V2/346EB2B6-C96A-4AD6-8CAF-777D4102AF29

Nov 1 01:37:46 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Finished index consistency check for /Volumes/WD320 Hitachi/.Spotlight-V100/Store-V2/1B85EFB9-D7CF-4687-A58C-A035CC86F027. Missing deletes:0

Nov 1 01:37:46 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Finished index consistency check for /Volumes/WD 2TB G401/.Spotlight-V100/Store-V2/175E4A2D-8C29-4550-AA78-EADD4B814CF6. Missing deletes:0

Nov 1 01:37:46 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Finished index consistency check for /Volumes/Seagate 4TB/.Spotlight-V100/Store-V2/346EB2B6-C96A-4AD6-8CAF-777D4102AF29. Missing deletes:0

Nov 1 01:37:46 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Finished index consistency check for /Volumes/Seagate 2TB/.Spotlight-V100/Store-V2/5EAD3D9D-6C8F-4A7E-92AC-2C219FE707D6. Missing deletes:0

Nov 1 01:37:46 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Finished index consistency check for /Volumes/WD 2TB G393/.Spotlight-V100/Store-V2/7515D292-486D-4083-8AFD-D70CE411F35D. Missing deletes:0

Nov 1 01:37:46 Pro-2.local mds[34]: (DiskStore.Warning:967) ReimportedAltNames repair issued for 0 items

Nov 1 01:37:47 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Finished index consistency check for /Volumes/WD Green 2 TB/.Spotlight-V100/Store-V2/EDC8D163-5B16-43F3-BEFF-F511D3668289. Missing deletes:0

Nov 1 01:37:47 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_checkDuplicateOids(void *, Boolean):Finished index consistency check for /Volumes/Mac HD 320/.Spotlight-V100/Store-V2/E7AA3AF6-80B8-4495-81E5-6F154D834F80. Missing deletes:0

Nov 1 01:37:47 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_consistencyCheck(void *, Boolean):Starting internal consistency check for /Volumes/Mac HD 320/.Spotlight-V100/Store-V2/E7AA3AF6-80B8-4495-81E5-6F154D834F80

Nov 1 01:37:47 Pro-2.local mds_stores[191]: (/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T)(Warning) IndexSDB in void si_consistencyCheck(void *, Boolean):Finished internal consistency check for /Volumes/Mac HD 320/.Spotlight-V100/Store-V2/E7AA3AF6-80B8-4495-81E5-6F154D834F80. Checks: 167955 Missing:0 Inconsistent:0 Missing deletes:0

Nov 1 01:37:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.FileSyncAgent.PHD.isRunning): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.

Nov 1 01:37:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.mbloginhelper.user): This key does not do anything: OnDemand

Nov 1 01:37:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.mbpluginhost.user): This key does not do anything: OnDemand

Nov 1 01:37:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.secd): This key does not do anything: OnDemand

Nov 1 01:37:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.secd): The ServiceIPC key is no longer respected. Please remove it.

Nov 1 01:37:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.speech.speechsynthesisd): This key does not do anything: OnDemand

Nov 1 01:37:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.TrustEvaluationAgent): This key does not do anything: OnDemand

Nov 1 01:37:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles[2624]): Could not find uid associated with service: 0: Undefined error: 0 504

Nov 1 01:37:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.sizing[2625]): Could not find uid associated with service: 0: Undefined error: 0 504

Nov 1 01:37:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Nov 1 01:37:58 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles[2627]): Could not find uid associated with service: 0: Undefined error: 0 504

Nov 1 01:37:58 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Nov 1 01:37:58 Pro-2 com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The _DirtyJetsamMemoryLimit key is not available on this platform.

Nov 1 01:38:03 Pro-2.local com.apple.SecurityServer[57]: Session 100025 created

Nov 1 01:38:06 Pro-2.local mdworker[2630]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

Nov 1 01:38:07 Pro-2.local discoveryd[53]: Basic DNSResolver dropping message because it doesn't match the one sent Port:0 MsgID:256

Nov 1 01:38:07 Pro-2.local discoveryd[53]: Basic DNSResolver dropping message because it doesn't match the one sent Port:0 MsgID:34048

Nov 1 01:38:07 Pro-2.local discoveryd[53]: Basic Warn DD_Warn: Bad count; corrupt TXT RDATA

Nov 1 01:38:07 Pro-2.local discoveryd[53]: Basic DNSResolver dropping message because it doesn't match the one sent Port:0 MsgID:1

Nov 1 01:38:08 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles[2633]): Could not find uid associated with service: 0: Undefined error: 0 504

Nov 1 01:38:08 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Nov 1 01:38:18 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles[2635]): Could not find uid associated with service: 0: Undefined error: 0 504

Nov 1 01:38:18 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Nov 1 01:38:28 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles[2637]): Could not find uid associated with service: 0: Undefined error: 0 504

Nov 1 01:38:28 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Nov 1 01:38:38 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles[2639]): Could not find uid associated with service: 0: Undefined error: 0 504

Nov 1 01:38:38 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Nov 1 01:38:47 Pro-2.local mdworker[1219]: (Import.Normal:1286) Using too many resources after 320 files (wired: 0 resident: 436564 swapped: 2 regions: 912), hit usage threshold importing /Volumes/Mac HD 320/System/Library/CoreServices/Folder Actions Dispatcher.app, exiting to clean up now.

Nov 1 01:38:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles[2642]): Could not find uid associated with service: 0: Undefined error: 0 504

Nov 1 01:38:48 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Nov 1 01:38:58 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles[2644]): Could not find uid associated with service: 0: Undefined error: 0 504

Nov 1 01:38:58 Pro-2 com.apple.xpc.launchd[1] (com.apple.mdworker.bundles): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Dec 6, 2014 12:40 PM in response to bmacgreg

Glad it worked out for you. Your problems were much worse than mine. I had just annoying log messages and a performance hit.

I guess though if permissions are screwed then programs will have all sorts of problems trying to open files etc.

Your snappier performance should simply be because you don't have mds turning in the background non stop, trying to access files it can't, and writing loads of log records.

These "phanton" users should only be from files or programs you installed using a user that you later deleted. In my case it was an upgrade of a 5 year old machine which has had users added and deleted many times. It will never happens if you do a clean install as there are no files owned by users that have been deleted, but that was not an option for me.

At the end of the day mds should be a bit cleverer and just skip files it has no permission to read, rather than getting stuck.

Nov 4, 2014 7:58 AM in response to William Paplham

Interesing. Doing a search through the primary HD for the UID causing the every 10 second messages found the UID associated with two applications, Aperature and DxO in my case, and these are files associated with the application which can't be deleted. I have deleted all the rest associated with the UID explained in previous posts here. I'm curious why applications create fake UID's which isn't registered.

Nov 5, 2014 5:56 AM in response to Andras Dombovari

First, the applications were installed by me, not another user. I'm the only person registered on the Mac. The applications weren't deleted nor any data or stuff migrated, I only noted the UID was created by the application installation, by Aperture and DxO plug-ins. I'm not sure why but they use UID 505 and group staff which was the UID in the error mesages on my Mac. The reinstallation was to resolve the memory issues, not this one which was a secondary result. Turning the messages off won't stop Spotlight, and if it's Spotlight's search that's creating the messages, then stopping its searching is an option if you don't use it. The command-R on bootup only reinstalls OS-X while preserving everything else, with only a few changes by some applications to default. As to "not necssary", after trying the recommendations on this thread, what options were left since, as someone noted, the Apple techs said it was a bad installation of Yosemite. So I don't think spending 3+ hours is too much when it resolved one problem and maybe both.

Dec 19, 2014 3:35 PM in response to cloudranger

Right - I've ploughed through the whole of this thread - most of which is way beyond my comfort zone - and it leaves me with a puzzle. I have the same problem as everyone else here, the offending number in my case being 501. I did the sudo find / -uid 501 command some time ago and it's still churning out files - thousands of them. The thing is, I'm sure I /used/ to be 501, but the id command tells me I'm 503 now. I'm pretty reluctant to do the command that changes all those files at once (and yikes! it's started churning out files on my Time Machine volume now, so I've interrupted it) especially as a lot of them seem to be in /Library and someone (on an earlier page - sorry I've forgotten who you are) suggested these should be owned by the system not by me.


I suppose one idea, if indeed it's possible, would be to change my own ID back to 501 - but then I'd probably get the same behaviour with 503 in the logs instead.


I'm reluctant to tinker in Terminal at the best of times, but I really don't like what's going on in my logs. Is there an equivalent, for example, to:

sudo find / -uid 501 -exec chown -h 503:20 {} \; -print

that would leave my Time Machine volume untouched... or should I change all that as well?

Jan 8, 2015 11:13 PM in response to David King1

latecomer to this thread... but I've been chasing down strange random Finder / login window crashes ever since upgrading my iMac to Yosemite (basically, using Fast User Switching to leave my userid active and applications running sometimes randomly quits all my apps and dumps out to the login window as if I actually logged out...). While looking through console logs trying to find the trigger point of my problem, I noticed tons of these com.apple.mdworker.bundles messages


using the find command as mentioned in this thread, I notice that ALL the offending files are related to Adobe software updates (not sure if that's a significant clue to the origin of the problem)


anyhow following the excellent instructions by cloudranger (thanks!) I managed to rid my Mac of these particular console messages. No idea if this has any relation to the problem I was originally debugging, but at least I can now more easily look through the console logs without all the extra mdworker warnings.

Jan 10, 2015 8:30 PM in response to jomiku

As an update, when I created the second user, apparently that spawned a permanent UID 502 even though I changed it to 505 right after creation and before restarting. I added a third user, which immediately took UID 502, and that is now reflected in the Info panel Sharing & Permissions. The system did that on its own, as it should, so I'm hoping the "fix" lasts.

Feb 20, 2015 9:57 AM in response to cloudranger

Thanks Cloudranger et al


I eventually got my issue sorted with these instructions and a bit of fiddling. I put it down to having deleted a couple of old user accounts recently but it may have predated that as my own guid is now 509 and there's only ever been seven accounts at maximum. I had three rogue accounts that were tripping up Spotlight including 1422 (from memory)—root. There were a number of apps that I had installed from a different user account and some installed by another user. Most of these were redundant and I deleted the whole app. Some I changed the permissions via Finder and some I used Terminal to change the owner. Somewhere along the line I messed something up and Console was reporting all sorts of errors. My Time Capsule also stopped working and I couldn't even connect to it.


I performed a reinstall as described (four hours+) and had to manually connect to the house wifi (hidden network) once it restarted. I have now connected to the Time Capsule by ethernet as it was refusing to recognise it over the wifi (despite it being the source of the wifi connection) and hopefully will be able to re-establish the backing up.


Here's hoping for a smoother running experience!

Oct 25, 2014 2:31 AM in response to Dustmoo

Interesting idea, thanks for your input!

It did not work for me however. Disk Utility repaired permissions mostly in /printers/.. folders (which I never use anyway), and after quitting all apps and reboot, system log was clear for a while, but once mdworker came back to life, same mess started again.. At least in my case it's every 10 seconds, not as bad as several times a second.

Oct 27, 2014 10:25 AM in response to Michelasso

Great, I meant to come back here and say that the solution above didn't keep. For me, it always happens when my machine is waking up. I am trying to figure out what is asking it to run for user 502 so that I can fix it without creating another user. 😀


But that is great feedback. I'll see if I can figure it out, for me a restart fixes the problem until my machine goes to sleep, upon waking the error starts.

Oct 27, 2014 6:39 PM in response to Michelasso

Intersting, I had the numbers 504 and 1104188992./


Followed your suggestion for 504. Reboot safe boot, then normal.


Got the following errors

Oct 27 21:24:55 [name deleted]-2.local mdworker[582]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

Oct 27 21:24:55 [name deleted]-.local mdworker[581]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

Oct 27 21:25:46 [name deleted]-.local mdworker[866]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

Oct 27 21:25:46 [name deleted]-.local mdworker[867]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

Oct 27 21:27:12 [name deleted]-.local mdworker[885]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

Oct 27 21:27:12 [name deleted]-.local mdworker[884]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

Oct 27 21:30:32 [name deleted]-.local mdworker[1094]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

Oct 27 21:30:32 [name deleted]-.local mdworker[1095]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"


Then no more. Hopefully gone.

Oct 31, 2014 7:39 AM in response to Michelasso

I did try searching for open files but didn't find any. The directories formed for the two user ids don't have any files in them.


I did stop by the genius bar and discuss log files (didn't bring in Mac Pro... that's a last resort).This is one of several processes (discoveryd is a prime offender) that are generating several thousand log entries an hour.


Several geniuses conferred and suggested that my install may be bad.


As a first test I reformatted an external drive. Did a fresh install, with migration from the Yosemite drive.


It didn't fix my discoveryd issues.


For mdworker, the 1104188992 ID is not longer showing up, but the 504 is.


So I reformatted again, this time installing without any migrations. I left it to run for the day and I'll see what the log looks like when I get home. Then I'll ad applications slowly to see what happens.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

com.apple.xpc.launchd & com.apple.mdworker.bundles pollute logs with errors

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