I told them NOT to do sandboxing in a bug report. Sandboxing is the stupidest, worst idea ever. It's purposeless. It's like forcing people to have safe sex. Look. When did personal responsibility go out the window? Let us have freedom. Overzealous security measures always backfire.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
10.8.2 - mdworker: Unable to talk to lsboxd
- Thread starter netnothing
- Start date
- Sort by reaction score
I told them NOT to do sandboxing in a bug report. Sandboxing is the stupidest, worst idea ever. It's purposeless. It's like forcing people to have safe sex. Look. When did personal responsibility go out the window? Let us have freedom. Overzealous security measures always backfire.
It's neither purposeless nor stupid. It is a very aggressive, broad, and blunt means of dealing with malware that has essentially no user adjustable settings.
Umm, I think you're confused about the nature of Apple and the platform. If you want freedom, you need to go with OpenIndiana, FreeBSD or a Linux distribution. OS X is significantly restricted for user choice. iOS is totally restricted.
So to sum things up:
So Im boord and am waiting until one of the solutions I found here finishes reindexing the drive. While I waited I did some more digging, and now know it wont help because I've just seem post #48.
So for the benefit of all us poor saps watching our older macs get crushed under the load of the runaway spotlight process, I've put together this synopsis. And here is what we've learned in this thread so far:
Possible solution 1:
#48 Terminal solution which erases Spotlight cashses and forces a reindex
-- and it dosent work
Possible solution 2:
#60 calls for editing system.sb wich does reduces sandboxing issues ie:
seen in #62
Its unclear if this solves the continuous reindexing issue however. (anyone?)
Temporary solution 3:
Reboot the computer periodically in "Safe Boot Mode"
(hold down the shift key just after the chime)
cue twilight zone music
This works but the problem seems to resurface for some after an unknown period of time (week).
Possible Solution 4:
Remove plugins in:
Not from this forum (dont know where I read it) but it might work for some. I removed the bootcamp plugin as I dont have a bootcamp partition any longer - but it didn't help me. See also 6
Solution 5:
Disable Spotlight all together by adding the root drive to the "Privacy" list:
System Prefs > Spotlight > Privacy
-- Obvious disadvantages here - but hey no problems!
Possible Solution 6:
Add Dropbox/Google Drive/Boot Camp partition/ To the above mentioned privacy list. (Can't find where thats mentioned . . .)
-- Didn't work for me though it might help some
Possible solution 7:
delete:
#18 -- Well that seems to really be about another problem entirely.
Possible solution 8:
Reinstall ML -- Not going to try to track that one down - that's crazy talk!
Possible solution 9:
Shut off screen savers https://forums.macrumors.com/posts/16048287/
-- Also dosent seem to be related ?
Possible solution 10:
Wait for ML 10.8.3 - or UHFO 74
-- I for one cant wait on thatchance
Possible solution 11:
Possible corrupt file in User Account. Not sure where I read that one, may not have been on this thread. See also 6 & 8
Possible solution 12: Guinness method.
- Power Down Machine (hold down power switch and mutter swear words)
- Go have a Guinness, possibly three or more just to be sure.
- Go back to work
Solution 12 seems to midigate the urgency of the problem significantly. Source: We've been making alcohol from
s about as long as we could walk its ancient wisdom!
Cheers!
So Im boord and am waiting until one of the solutions I found here finishes reindexing the drive. While I waited I did some more digging, and now know it wont help because I've just seem post #48.
So for the benefit of all us poor saps watching our older macs get crushed under the load of the runaway spotlight process, I've put together this synopsis. And here is what we've learned in this thread so far:
Possible solution 1:
#48 Terminal solution which erases Spotlight cashses and forces a reindex
-- and it dosent work
Code:
<despair>Possible solution 2:
#60 calls for editing system.sb wich does reduces sandboxing issues ie:
Code:
10/7/12 3:46:23.546 AM mdworker[11148]: Unable to talk to lsboxd
10/7/12 3:46:23.549 AM mdworker[11149]: Unable to talk to lsboxd
10/7/12 3:46:23.553 AM mdworker[11147]: Unable to talk to lsboxd
10/7/12 3:46:23.662 AM sandboxd[11150]: ([11148]) mdworker(11148) deny mach-lookup com.apple.ls.boxd
10/7/12 3:46:23.666 AM sandboxd[11150]: ([11149]) mdworker(11149) deny mach-lookup com.apple.ls.boxd
10/7/12 3:46:23.669 AM sandboxd[11150]: ([11147]) mdworker(11147) deny mach-lookup com.apple.ls.boxd
10/7/12 3:46:24.000 AM kernel[0]: Sandbox: sandboxd(11150) deny mach-lookup com.apple.coresymbolicationdIts unclear if this solves the continuous reindexing issue however. (anyone?)
Temporary solution 3:
Reboot the computer periodically in "Safe Boot Mode"
(hold down the shift key just after the chime)
cue twilight zone music
This works but the problem seems to resurface for some after an unknown period of time (week).
Possible Solution 4:
Remove plugins in:
Code:
~/Library/Spotlight/
/Library/Spotlight/Solution 5:
Disable Spotlight all together by adding the root drive to the "Privacy" list:
System Prefs > Spotlight > Privacy
-- Obvious disadvantages here - but hey no problems!
Possible Solution 6:
Add Dropbox/Google Drive/Boot Camp partition/ To the above mentioned privacy list. (Can't find where thats mentioned . . .)
-- Didn't work for me though it might help some
Possible solution 7:
delete:
Code:
/System/Library/LaunchAgents/com.apple.afpstat.plistPossible solution 8:
Reinstall ML -- Not going to try to track that one down - that's crazy talk!
Possible solution 9:
Shut off screen savers https://forums.macrumors.com/posts/16048287/
-- Also dosent seem to be related
?Possible solution 10:
Wait for ML 10.8.3 - or UHFO 74
-- I for one cant wait on that
chance Possible solution 11:
Possible corrupt file in User Account. Not sure where I read that one, may not have been on this thread. See also 6 & 8
Code:
</despair>
<apathy>- Power Down Machine (hold down power switch and mutter swear words)
- Go have a Guinness, possibly three or more just to be sure.
- Go back to work
Solution 12 seems to midigate the urgency of the problem significantly. Source: We've been making alcohol from
s about as long as we could walk its ancient wisdom! Cheers!
Code:
</apathy >So Im boord and am waiting until one of the solutions I found here finishes reindexing the drive. While I waited I did some more digging, and now know it wont help because I've just seem post #48.
So for the benefit of all us poor saps watching our older macs get crushed under the load of the runaway spotlight process, I've put together this synopsis. And here is what we've learned in this thread so far:
Possible solution 1:
#48 Terminal solution which erases Spotlight cashses and forces a reindex
-- and it dosent work
Code:<despair>
Possible solution 2:
#60 calls for editing system.sb wich does reduces sandboxing issues ie:
seen in #62Code:10/7/12 3:46:23.546 AM mdworker[11148]: Unable to talk to lsboxd 10/7/12 3:46:23.549 AM mdworker[11149]: Unable to talk to lsboxd 10/7/12 3:46:23.553 AM mdworker[11147]: Unable to talk to lsboxd 10/7/12 3:46:23.662 AM sandboxd[11150]: ([11148]) mdworker(11148) deny mach-lookup com.apple.ls.boxd 10/7/12 3:46:23.666 AM sandboxd[11150]: ([11149]) mdworker(11149) deny mach-lookup com.apple.ls.boxd 10/7/12 3:46:23.669 AM sandboxd[11150]: ([11147]) mdworker(11147) deny mach-lookup com.apple.ls.boxd 10/7/12 3:46:24.000 AM kernel[0]: Sandbox: sandboxd(11150) deny mach-lookup com.apple.coresymbolicationd
Its unclear if this solves the continuous reindexing issue however. (anyone?)
Temporary solution 3:
Reboot the computer periodically in "Safe Boot Mode"
(hold down the shift key just after the chime)
cue twilight zone music
This works but the problem seems to resurface for some after an unknown period of time (week).
Possible Solution 4:
Remove plugins in:
Not from this forum (dont know where I read it) but it might work for some. I removed the bootcamp plugin as I dont have a bootcamp partition any longer - but it didn't help me. See also 6Code:~/Library/Spotlight/ /Library/Spotlight/
Solution 5:
Disable Spotlight all together by adding the root drive to the "Privacy" list:
System Prefs > Spotlight > Privacy
-- Obvious disadvantages here - but hey no problems!
Possible Solution 6:
Add Dropbox/Google Drive/Boot Camp partition/ To the above mentioned privacy list. (Can't find where thats mentioned . . .)
-- Didn't work for me though it might help some
Possible solution 7:
delete:#18 -- Well that seems to really be about another problem entirely.Code:/System/Library/LaunchAgents/com.apple.afpstat.plist
Possible solution 8:
Reinstall ML -- Not going to try to track that one down - that's crazy talk!
Possible solution 9:
Shut off screen savers https://forums.macrumors.com/posts/16048287/
-- Also dosent seem to be related
Possible solution 10:
Wait for ML 10.8.3 - or UHFO 74
-- I for one cant wait on that
Possible solution 11:
Possible corrupt file in User Account. Not sure where I read that one, may not have been on this thread. See also 6 & 8
Possible solution 12: Guinness method.Code:</despair> <apathy>
- Power Down Machine (hold down power switch and mutter swear words)
- Go have a Guinness, possibly three or more just to be sure.
- Go back to work
Solution 12 seems to midigate the urgency of the problem significantly. Source: We've been making alcohol from
Cheers!
Code:</apathy >
Well, I would just add "Possible solution 13":
Apple wakes up and fixes the problem once and for all in 10.8.3.
Not fixed in 10.8.3. In fact, I fixed the problem with a safe boot, but then it comes back every time I install a new beta. My guess is that the update process messes with sandboxing, since clean installing to 10.8.2 resulted in no mdworker messages.
This is outrageous. I have reinstalled ML Core Files with a fresh copy from the App Store (without erasing user data) and the problem of Spotlight constant reindexing bogging down my Macs performance still persists. Before reinstalling ML I´ve even experienced some Kernel Panics. No System is perfect, but come on: There is something seriously messed up here, Apple.
Applied Solution #7 right now which seems to have prompted Spotlight to do a full reindex. Also disabled "Wake Up on Network Access" and created a new user account. I will let the System do its thing and if it does not work I will try the "Safe Boot" fix next.
Apple needs to address this, it really made me and I bet a lot of other users dislike OSX. Gosh, I´ve never had this issues with Snow Leopard. I´m not one who rants easily, but this is really p*ssing me off.
Thanks for all the help given in this thread, folks.
Update:
Some of the fixes I´ve tried have rendered my machine to be unable to boot. Glad I was able to roll back the last TM Backup.
Applied Solution #7 right now which seems to have prompted Spotlight to do a full reindex. Also disabled "Wake Up on Network Access" and created a new user account. I will let the System do its thing and if it does not work I will try the "Safe Boot" fix next.
Apple needs to address this, it really made me and I bet a lot of other users dislike OSX. Gosh, I´ve never had this issues with Snow Leopard. I´m not one who rants easily, but this is really p*ssing me off.
Thanks for all the help given in this thread, folks.
Update:
Some of the fixes I´ve tried have rendered my machine to be unable to boot.
Glad I was able to roll back the last TM Backup.
Last edited:
Is Evernote the cause?
How many people on this thread are using Evernote?
I bought a new computer and it was working fine (OS X 10.8.2) until I installed Evernote. After I installed it I started seeing the lsboxd errors. Then I deleted Evernote and the errors went away. Then I installed it again and they came back.
Details:
Based on other stuff I've read I think these errors are from third-party spotlight importers so it may be that just removing those importers will solve the problem (although it will keep the custom documents out of Spotlight).
How many people on this thread are using Evernote?
I bought a new computer and it was working fine (OS X 10.8.2) until I installed Evernote. After I installed it I started seeing the lsboxd errors. Then I deleted Evernote and the errors went away. Then I installed it again and they came back.
Details:
- Installed Evernote 5.0.6 by downloading from Evernote site.
- Immediately installed update to 5.0.7 via in-app update.
- Deleted Evernote by dragging application to trash and emptying trash.
- Installed Evernote 5.0.7 by downloading from Evernote site.
Based on other stuff I've read I think these errors are from third-party spotlight importers so it may be that just removing those importers will solve the problem (although it will keep the custom documents out of Spotlight).
I'm using an application that has a 3rd-party Spotlight importer. Thanks for the info!
Never used Evernote but have always had these issues (with 10.8.2) - will check the spotlight importers, though.
Has the ML 10.8.3 update sorted out the mdworker problems?
I'm away from home at the moment.
Hope the fix is there
Mac
iMac iPad iPhone iPod
I'm away from home at the moment.
Hope the fix is there
Mac
iMac iPad iPhone iPodHas the ML 10.8.3 update sorted out the mdworker problems?
I'm away from home at the moment.
Hope the fix is there
Mac
Nope, mdworker and sandboxd Console messages STILL THERE. Although they do seem to occur less often now.
Nope. I did the combo update, and they're still spamming my log at the same clip.
Apple obviously doesn't give a **** about making their operating system stable.
Apple obviously doesn't give a **** about making their operating system stable.
Do the console messages in any way affect the system's stability?
The fact that mdworker is being barred from completing certain tasks due to sandboxing issues is a 'stability' issue, even if it doesn't result in something like a kernel panic.
Exactly. Not to mention that this issue was widely reported to Apple through its bug report form - and my own report was already flagged as "duplicate" since there were so many people doing the same.
This is the problem when you have two guys working on OS X, as opposed to 2000 on iOS.
Yes, I´ve been using Evernote and the mdworker Errors seem to be related with this Application somehow. Have now updated to latest version of Evernote.
OSX 10.8.3 is still giving me
16.03.13 14:23:34,033 mdworker[1381]: Unable to talk to lsboxd
though, even without Evernote running.
How does one remove this importers?
OSX 10.8.3 is still giving me
16.03.13 14:23:34,033 mdworker[1381]: Unable to talk to lsboxd
though, even without Evernote running.
How does one remove this importers?
Depends on where the importer files live. Normally they'll be inside the application bundle, or in one of the Library folders.
Clearly there's a problem, too many people are reporting it. Apple released Lion and Mountain Lion Supplemental updates that fixed this problem for many, but didn't fix it for many others. So duh yes there is a problem, I find it annoying when some people try to apologize for Apple at the expense of the user experience.
I suspect it's a sandboxing related problem, but that doesn't mean it's sandboxing itself that's the problem, largely due to what I found in this thread. Whether an Apple or 3rd party induced bug, short of actual malware being thwarted, the behavior people are experiencing is a bug and it's not OK.
I suspect it's a sandboxing related problem, but that doesn't mean it's sandboxing itself that's the problem, largely due to what I found in this thread. Whether an Apple or 3rd party induced bug, short of actual malware being thwarted, the behavior people are experiencing is a bug and it's not OK.
Of course the console messages do not affect the system's stability. They're just string written into a text file or database. The cause of the console messages also causes Spotlight indexing to crash, causing Spotlight to eat up CPU and disk I/O while not providing a full index of the disk. Since Time Machine relies on Spotlight for proper functioning, Spotlight's crashes also affect Time Machine's performance.
Since both Spotlight and Time Machine are system agents, I would say that the problems discussed on this thread are a source of system instability. Given the functional problems and resource-wasting problems, it is very disappointing that Apple has let this go on for so long.
I have this entry in my Console logs too. My MBP seems to be running fine, although I've only had it for 4 days now.
I'm also using 10.8.3.
Maybe 10.8.4 will fix it....
I'm also using 10.8.3.
Maybe 10.8.4 will fix it....
OK... Say you are right -- we all get a safe computer... Which is great...
But @ which cost ???
In this case (sandboxing) performance is the cost.. Not so bad for folks using the computer to do emailing and non-high-performance applications. But -- for those who rely on the computer to perform... Like when using NLEs, DAWs etc.. Sandboxing is a killer.
Even Apples own apps pro apps are suffering under sandboxing...
Look -- there is NO such think as 100% secure in word full of code. There just isnt.. If someone is persistent enough, he can reverse-engineer any software..
Remember this : if the computer can read the CODE --- So can a hacker !!!