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

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
63 replies

Oct 29, 2014 12:29 PM in response to Cyril Kay

I ran the command (thanks). I found 504 again in the directories discussed in this forum. I also had several thousand hits, all in backups.


594 appears to be an account for my son.


I had done a clean install of mavericks prior to installing yosemite. I did not migrate accounts (I was trying to clean detritus, possibly from consecutive upgrades/migrations going all the way back to a Centris 650). I have the only account on the computer, all other references are in backup files or on other hard drives with older versions of the operating system.


The 1104188992 id was there as well. I deleted both folders.


Also folders for:

89 (spotlight)

235 (assetcache)


I found this command online


dscl . -list /Users UniqueID


Useful as it lists all ids on the computer. 504 and 1104188992 were not on the list.


Posting before reboot so I still had info handy. Hopefully this works.

Oct 30, 2014 5:23 AM in response to William Paplham

William Paplham wrote:


Whatever deleting the folders does, it's only a temporary solution. Problem reappeared within 3 hours. Same folders are back.

Well, that simply means that something is regularly re-creating them. You may have a chance finding the process creating the files with wrong UID using "lsof". After identifying the incriminated files try running


lsof | grep <file to check>


like in this example:


lsof | grep /private/var/folders/wt/9h7d00q51nvfsqkvsdgxq0240000gn/T/com.apple.iChat

Messages 1610 admin 40u REG 1,5 512 1848404 /private/var/folders/wt/9h7d00q51nvfsqkvsdgxq0240000gn/T/com.apple.iChat/etilqs _uDh9zk5ow73vZNt

Messages 1610 admin 41u REG 1,5 4096 1848405 /private/var/folders/wt/9h7d00q51nvfsqkvsdgxq0240000gn/T/com.apple.iChat/etilqs _RDjd1IjXyGHnFI5

Messages 1610 admin 42u REG 1,5 512 1848406 /private/var/folders/wt/9h7d00q51nvfsqkvsdgxq0240000gn/T/com.apple.iChat/etilqs _vpzC2mqdnblrXqg

Messages 1610 admin 43u REG 1,5 4096 1848407 /private/var/folders/wt/9h7d00q51nvfsqkvsdgxq0240000gn/T/com.apple.iChat/etilqs _iUA3XeCrMKN6LQo


Then you can get the full path of the process doing


ps -ef | grep <PID>


Where <PID> (the process ID) is the first number you see in the previous output (1610 in my example). That may or may not work, depending on the process being still alive. If you're lucky and can find it update/uninstall/delete it or its correspondent application. Or check its preferences, whatever its needed to get a rid of those UIDs. You'll need to do some more digging.

Oct 30, 2014 1:07 PM in response to Cyril Kay

I have this similar issue, with the 502 UID. This user is non existent on my system.

I deleted the files suggested in the /var folder, but the warnings are still happening.

Running the search suggested by Cyril resulted in a long list of files elsewhere on the drive.

sudo find / -user 504 -exec ls -ld {} \;


I have Applications owned by this user, tons of files in /Library, etc.

Which probably explains why this message appears in the Console over and over. Whenever mdworker finds one of them, to writes this message into the Console.


I wish there was a way to run "lsof" only in the newly spawned processes....

Should we maybe fix / set the user of these files to something else?

Something that exists in the system?

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.

Oct 31, 2014 8:34 AM in response to William Paplham

You probably won't find any open files, since the event mentioned in the log messages are happening almost instantly (very fast).

The best way to find them is to use the command mentioned earlier:

sudo find / -user 504 -exec ls -ld {} \;


This could take a while. I collected the output to a file on the Desktop with the following command:

sudo find / -user 504 -exec ls -ld {} \; > ~/Desktop/foo.txt


I looked through my list, and most were just applications (with many-many nested folders inside).

So changing the owner to my user was relatively quick, and not so difficult.


As you are suspecting, I am also suspecting that these files are leftovers from previous system installs and HD migrations.

Since I fixed the owner on my list of files, the messages in the logs stopped.

Oct 31, 2014 11:10 AM in response to Andras Dombovari

Were the files you found on the boot drive?


All the 504 references I found were on other drives, specifically a Mountain Lion boot drive (at the time 504 was a real user account) and backups of that drive. I'm not at home to look, but from memory, the files were in the user folder, not applications.


Which leads me to something I haven't tested yet, unmounting those drives or excluding from Spotlight search. Something to play with while handing out Halloween candy.

Oct 31, 2014 5:15 PM in response to William Paplham

So after a clean install and over twelve hours, no mdworker issues.


In summary:

(A) Main system (Yosemite install over Maverick, which was a clean install several weeks earlier) - mdworker errors associated with 504 and 1104188992.


(B) Clean install of Yosemite on freshly wiped hard drive, using migration from Main system above - mdworker errors associated with 504


(C) Clean Clean install of Yosemite on freshly wiped hard drive, no migration, but iCloud data used to configure settings. NO ERRORs.


Since I have the same set of hard drives attached, mere presence of old system installations (not the boot drive) and backups aren't enough to trigger the mdworker issues.


So what triggers the errors?

Spotlight appears to be done indexing (at least it's not consuming CPU). Doesn't appear to be the cause.

Time machine would be running in case (B) since all my settings were migrated, whereas it's not set up in case (C). The time machine archive is where most of the 504 userid files were located. Also, when I do a find on 504 it appears the only locations are in the TM Machine backup.


I can't say for sure, but I don't think I reset the Time Machine backup after installing Yosemite. I don't remember what happened when I did the Mavericks clean install. It's possible that the Time Machine backup has references to users that don't exist anymore.


Is everyone seeing this issue using Time Machine.


Next step in troubleshooting is to reboot in Main system, wipe the Time Machine drive and start over and see what happens.

Oct 31, 2014 7:45 PM in response to William Paplham

Interesting behavior on booting back to my main system drive. I wasn't getting mdworker errors related to "phantom" ids.


I manually started Time Machine to see if I could trigger errors. It appears that running on another boot drive for a day changed enough files that Time Machine could not used it's cached scans. From logs:

Oct 31 20:31:27 Mac-Pro-2.local com.apple.backupd[929]: Starting manual backup

Oct 31 20:31:28 Mac-Pro-2.local com.apple.backupd[929]: Backing up to /dev/disk11s2: /Volumes/DroboTM/Backups.backupdb

Oct 31 20:31:32 Mac-Pro-2.local com.apple.backupd[929]: Event store UUIDs don't match for volume: Hitachi 2TB

Oct 31 20:31:32 WMac-Pro-2.local com.apple.backupd[929]: Event store UUIDs don't match for volume: Seagate 4TB

Oct 31 20:31:32 Mac-Pro-2.local com.apple.backupd[929]: Event store UUIDs don't match for volume: WD Black 1000

Oct 31 20:31:32 Mac-Pro-2.local com.apple.backupd[929]: Forcing deep traversal on source: "SanDisk240" (device: /dev/disk0s2 mount: '/' fsUUID: 31D86B38-3F77-30C7-B2AC-8E0274C41535 eventDBUUID: 235CDDDF-EDF3-40C4-9C10-2B11DD9CBEE8)

Oct 31 20:31:48 Mac-Pro-2.local com.apple.backupd[929]: Deep event scan at path:/Volumes/Hitachi 2TB reason:must scan subdirs|new event db|

Oct 31 20:31:48 Mac-Pro-2.local com.apple.backupd[929]: Unable to use cached scan; fsevent uuid mismatch

Oct 31 20:31:48 Mac-Pro-2.local com.apple.backupd[929]: Running event scan

Oct 31 20:32:29 Mac-Pro-2.local com.apple.backupd[929]: Finished scan

Oct 31 20:32:29 Mac-Pro-2.local com.apple.backupd[929]: Saved event cache at /Volumes/DroboTM/Backups.backupdb/William’s Mac Pro (2)/2014-10-31-203132.inProgress/EC26B84B-A5EA-4C88-829E-27733E985103/.CF113335 -FFC3-394A-B363-1A0B068CB412.eventdb

Oct 31 20:32:29 Mac-Pro-2.local com.apple.backupd[929]: Not using file event preflight for Hitachi 2TB

Oct 31 20:32:33 Mac-Pro-2.local com.apple.backupd[929]: Deep event scan at path:/Volumes/Seagate 4TB reason:must scan subdirs|new event db|

Oct 31 20:32:33 Mac-Pro-2.local com.apple.backupd[929]: Unable to use cached scan; fsevent uuid mismatch

Oct 31 20:32:33 Mac-Pro-2.local com.apple.backupd[929]: Running event scan

Oct 31 20:32:36 Mac-Pro-2.local com.apple.backupd[929]: Finished scan

Oct 31 20:32:36 Mac-Pro-2.local com.apple.backupd[929]: Saved event cache at /Volumes/DroboTM/Backups.backupdb/William’s Mac Pro (2)/2014-10-31-203132.inProgress/EC26B84B-A5EA-4C88-829E-27733E985103/.0DC0DAA8 -2F46-36FD-9A05-638EF4172DD7.eventdb


This was repeated for all backed up drives.


I still have some time to go (somehow it found 46 GB of material that needed backup), but hopefully this cleaned everything out.


The one error I am getting consistently is

Oct 31 21:51:48 Mac-Pro-2.local mdworker[1217]: 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, 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.

Nov 2, 2014 7:54 AM in response to Michelasso

I recently began getting some unexpected shutdowns on my iMac - always when I'm away (makes me think it is related to the screen saver).


However, I did notice that the console logs have tons of lines like this:


com.apple.xpc.launchd: (com.apple.mdworker.bundles[182xx]) Could not find uid associated with service: 0: Undefined error: 0 501


The tail end is always 501. (I noticed that you have 502 in your error msgs.)


My console logs are filled with lines like this ... and I'm wondering if that has something to do with the shutdowns.


Most irritating ... and I'm using Yosemite, iMac 2.5 i5, 16GB, 2TB.


I'd love to figure out what the problem is ...

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 ID.