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

10.8.2 spotlight indexing issue

Since updating to 10.8.2 I noticed that spotlight will randomly start indexing for a while and then stop. Basically everything IS already indexed because when I search in spotlight I got what I need but from time to time there will be indexing progress bar in the bottum of the spotlight dropdown menu, which is full but keeps rolling. I checked console.app and saw a lot of messages regarding mdworker, mdimporter and lsboxd like the following:


mdworker: Unable to talk to lsboxd

mdimporter: Unable to talk to lsboxd

sandboxd: mdworker(692) deny mach-lookup com.apple.ls.boxd


I suspect that there might be some issue with spotlight and the sandbox mechanism? When I boot the computer I also notice that lsboxd keeps running in activity monitor, which wasn't the case prior to 10.8.2 update.


Has anyone seen the same symptom?


I'm on a mid-2010 MacBook Pro with Crucial M4 SSD.

OS X Mountain Lion

Posted on Sep 19, 2012 8:28 PM

Reply
53 replies

Jan 16, 2013 9:14 PM in response to adrianruica

Originally I was getting three sets of messages in console. Now I'm only getting two, and those come less often. So the fix is worth doing.


The first messgae set would be "mdworker[xxxx]: Unable to talk to lsboxd" (one for every userid + one for _spotlight)


This would then be followed by one "PM kernel[0]: Sandbox: sandboxd(yyy) deny mach-lookup com.apple.coresymbolicationd" message


and then followed by "PM sandboxd[yyy]: ([xxxx]) mdworker(xxxx) deny mach-lookup com.apple.ls.boxd" messages (one for every userid + one for _spotlight)


This didn't seem to be a CPU hog, and spotlight still seemed to be working correctly, but it flooded the system log with messages obscured other information, and the time covered by the log was less. On my MacBookAir, I'm worried about this wearing out the flash in SSD..


The fix to "System.sb" got rid of the "deny mach-lookup com.apple.ls.boxd" message and the "Unable to talk to lsboxd" messages occur less frequently now, about every 4 minutes. A short time (20s??) after sending the "Unable to talk to lsboxd" message, the mdworker process dies. Activity monitor doesn't note any faults or hangs associated with the dying mdworker processes after the console messages.


The "deny mach-lookup com.apple.coresymbolicationd" " message now occurs very infrequently, perhaps once per hour.

Feb 13, 2013 1:10 PM in response to adrianruica

For the record, modifying system.sb effectively killed my machine. I'm not sure if I did something wrong, but after modifing my machine went from being slow to completely unusable. Sure, spotlight isn't indexing, but then again my machine isn't really doing much after logging in so it doesn't matter.


Not sure if I did anything wrong, but I wouldn't recommend this fix.


Turns out that spelling is VERY IMPORTANT ("boxed" is not the same as "boxd"). This fix works, I'm just a moron. Sorry for sounding the alarm before I did a thorough check.


10.8.2

iMac 2010

8 GB RAM

Mar 4, 2013 2:28 AM in response to jianglai

I came acrross this problem, when I noticed, that when building a jar or a zip file, it took a long time to complete. The cause seems to be this mdworker process starting and boosting up towards 100% cpu usage.


So I applied the fix suggested by adrianruica


After restarting the system, I am now back to seconds instead of minutes building my jar and zip files.


thanks for finding this temporary solution.

Mar 12, 2013 6:56 PM in response to jianglai

Hi guys. Having same issues too. After reading this came up with an idea to exclude the whole Home folder from search results by adding it to Privacy tab in Spotlight Pref Pane. Log out - Log in, removed it from Privacy tab in Preferences. Log out - Log in, open Spotlight, tyle any letter, OS starts indexing. 55mins remaining in my case. Afterwards, everything worked normal, quick serach without indexing prompt and high processing.
Hope this works for you.
Cheers.


MBP 5,1 10.8.2.

Apr 6, 2013 9:10 PM in response to jianglai

None of the fixes work for me, on 10.8.3. First, don't change the "i" to "l" or the Finder won't load. The guy who sent that in and then wrote in the correction didn't specify which "l" he's talking about. Also, I assume "boxd" is correct. Either way, didn't work. Home folder in and out didn't work. Since I don't know where var/folders is, I haven't tried that one. I also tried a couple of Terminal fixes with spotlight, nada.


Does anyone have a real, tried, tested fix that works on 10.8.3? And, of course, why can't Apple fix it, it would take them 10 minutes, while the rest of us

fool around blindly.


MBP Retina 13

10.8.3

Miffed

Apr 9, 2013 4:46 AM in response to jianglai

I occasionnally get this mdworker process to grab 100% of processor activity in short bursts jumping from one core to another (iMac 10.8.3 - 4 cores), which causes sluggish operation and brings heat problems in a matter of a few minutes.


I've read somewhere that restarting in safe mode (Shift key at reboot) and restarting again after a complete boot cures the problem (or, more precisely, the symptom).


I've had to do just that 4 times in the past 2-3 months, and it worked all the times.


Of course it doesn't cure the unknown cause of the problem, but it sure is a relief to be able to get back to work with no more overheating and no more of this sluggish operation.


I wish you tried this and report if it works.


I only hope we are dealing with the same problem here.


YM

Apr 17, 2013 8:31 AM in response to adrianruica

Go to /System/Library/Sandbox/Profiles/ and there should be a file named "system.sb".

1 Make a backup of the original one and place somewhere safe on your harddisk.

2 Copy system.sb on the desktop to can edit.

3 Open it with a text editor and check for the block thext:

;;; Allow IPC to standard system agents.

(allow mach-lookup

(global-name "com.apple.bsd.dirhelper")

(global-name "com.apple.system.logger")

(global-name "com.apple.system.notification_center")

(global-name "com.apple.system.opendirectoryd.libinfo")

(global-name "com.apple.system.DirectoryService.libinfo_v1")

(global-name "com.apple.system.opendirectoryd.membership")

(global-name "com.apple.xpcd"))


4 Add these 2 lines (in bold), then the block thext will look like this:

;;; Allow IPC to standard system agents.

(allow mach-lookup

(global-name "com.apple.bsd.dirhelper")

(global-name "com.apple.system.logger")

(global-name "com.apple.system.notification_center")

(global-name "com.apple.system.opendirectoryd.libinfo")

(global-name "com.apple.system.DirectoryService.libinfo_v1")

(global-name "com.apple.system.opendirectoryd.membership")

(local-name "com.apple.ls.boxd")

(global-name "com.apple.is.boxd")

(global-name "com.apple.xpcd"))


5 Save system.sb on the destop, then delete the original one in the /System/Library/Sandbox/Profile and replace with this modified one. Spotlight (mdworker) should calm down.


Thanks to Phobos.


This looks like it is working for us. THANK YOU!

10.8.2 spotlight indexing issue

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