10.8.2 - mdworker: Unable to talk to lsboxd

[BRLawyer]

Can anyone confirm if the supplemental update has fixed this?

[mrapplegate]

Originally Posted by BRLawyer

Can anyone confirm if the supplemental update has fixed this?

Nope, it is not fixed on my system.

[razmarino]

Originally Posted by BRLawyer

Can anyone confirm if the supplemental update has fixed this?

nope, it doesn't...

[kbmb]

Still getting the messages here after the update.

-Kevin

[petsounds]

Well, has anyone actually filed a bug on this?

[gwang73]

Originally Posted by BRLawyer

Can anyone confirm if the supplemental update has fixed this?

Nope, not fixed. I did mod the mdworker.sb and mdworker-bundle.sb system files with safe-boot and so far so good. I will let you know if the issue comes back like before after a few days.

----------

Originally Posted by petsounds

Well, has anyone actually filed a bug on this?

Of course. Does Apple really do anything with them? That's the real question

[clayj]

I have all three of the error messages from the original post all through my System.log. This is on a Mac Pro (2008) with 24 GB of RAM, running VMware Fusion 5.0.1 and OS X 10.8.2 with yesterday's update.

[Joesg]

Originally Posted by kbmb

Well after the Safe boot....the messages went away for a week. However, as of this morning they are back.

Guess we'll have to wait until 10.8.3 for a fix.

-Kevin

I had a return of the lsboxd messages after one week as well. It seems that safe mode boot is a temporary, but reliable fix.

[whiskymac]

Originally Posted by Joesg

I had a return of the lsboxd messages after one week as well. It seems that safe mode boot is a temporary, but reliable fix.

After loading up the supplemental update lsboxd messages are back.

Agree with Kevin - we will have to wait for 10.8.3 fix.

Another safe boot on the cards later

Mac

iMaciPadiPhone

[phobox]

You can completely fix all the mdworker related sandbox errors in Console (including the 'cannot talk to lsboxd') by editing the system.sb profile rather than the mdworker ones. The system.sb file is used by all Apple system processes that run under the sandbox, including mdworker. If you modify this file (which is located in /System/Library/Sandbox/Profiles) to include:

(allow mach-lookup (global-name "com.apple.ls.boxd"))

(allow mach-lookup (local-name "com.apple.ls.boxd"))

This will stop all the lsbox related mdworker issues.

I must warn however that modifying this file is potentially dangerous if you're not really sure what you're doing. Take a backup of it just in case. And only add the lines above, do not modify anything else.

[gwang73]

Originally Posted by phobox

You can completely fix all the mdworker related sandbox errors in Console (including the 'cannot talk to lsboxd') by editing the system.sb profile rather than the mdworker ones. The system.sb file is used by all Apple system processes that run under the sandbox, including mdworker. If you modify this file (which is located in /System/Library/Sandbox/Profiles) to include:

(allow mach-lookup (global-name "com.apple.ls.boxd"))

(allow mach-lookup (local-name "com.apple.ls.boxd"))

This will stop all the lsbox related mdworker issues.

I must warn however that modifying this file is potentially dangerous if you're not really sure what you're doing. Take a backup of it just in case. And only add the lines above, do not modify anything else.

Thanks phobox, I thought it would be better to mod the system.sb after looking at the code in mdworker.sb. So far, so good. I hope it's a permanent fix.

[honkj]

Originally Posted by phobox

You can completely fix all the mdworker related sandbox errors in Console (including the 'cannot talk to lsboxd') by editing the system.sb profile rather than the mdworker ones. The system.sb file is used by all Apple system processes that run under the sandbox, including mdworker. If you modify this file (which is located in /System/Library/Sandbox/Profiles) to include:

(allow mach-lookup (global-name "com.apple.ls.boxd"))

(allow mach-lookup (local-name "com.apple.ls.boxd"))

This will stop all the lsbox related mdworker issues.

I must warn however that modifying this file is potentially dangerous if you're not really sure what you're doing. Take a backup of it just in case. And only add the lines above, do not modify anything else.

hmmm, i did your change, and only your change, I used to get:

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


now after your change, i get this

10/7/12 4:02:08.720 AM mdworker[11247]: Unable to talk to lsboxd
10/7/12 4:02:08.722 AM mdworker[11248]: Unable to talk to lsboxd


so it fixed something, but there is still some more to look for????

[gwang73]

Originally Posted by honkj

hmmm, i did your change, and only your change, I used to get:

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


now after your change, i get this

10/7/12 4:02:08.720 AM mdworker[11247]: Unable to talk to lsboxd
10/7/12 4:02:08.722 AM mdworker[11248]: Unable to talk to lsboxd


so it fixed something, but there is still some more to look for????

The additional change I did after the errors came back was deleted the com.apple.coresymbolicationd file and I do not have any mdworker or sandbox errors related to lsboxd.

[cascaman]

But do you have your spotlight re-indexing indexed drives all the time?

[phobox]

The two changes I noted above should fix sandbox related issues, but I cant promise it will fix any indexing issues you have. The cause of those are as yet undetermined, but people on other forums have had success by removing the /var/folders directory and rebooting. I wouldnt recommend that though, instead I would delete the indexes and rebuild them, it seems to be the safer way of doing it.

As for the sandbox, Im convinced Apple haven't done enough to allow it to work properly and trouble-free. A lot of people have issues with spotlight and Im fairly sure they are sandbox related. I also had problems with TextEdit not saving my document yesterday which were also related to sandbox, luckily just restarting TextEdit fixed that one but it does highlight an ongoing sandbox issue. Im all for the beefing up of security but currently the sandbox seems to do little other than cause problems and add overhead. Perhaps rather than spending all their time adding flashy features to releases, they should have a team concentrate on fixing the deeper issues and making the underlying system a lot more efficient. If things carry on the way they are, adding complexity and inefficiencies, we'll end up in Windows territory and NONE of us want that :P

[Mandaraxa]

Originally Posted by phobox

You can completely fix all the mdworker related sandbox errors in Console (including the 'cannot talk to lsboxd') by editing the system.sb profile rather than the mdworker ones. The system.sb file is used by all Apple system processes that run under the sandbox, including mdworker. If you modify this file (which is located in /System/Library/Sandbox/Profiles) to include:

(allow mach-lookup (global-name "com.apple.ls.boxd"))

(allow mach-lookup (local-name "com.apple.ls.boxd"))

This will stop all the lsbox related mdworker issues.

I must warn however that modifying this file is potentially dangerous if you're not really sure what you're doing. Take a backup of it just in case. And only add the lines above, do not modify anything else.

Thank you Phobox. You are a life saver.

[clayj]

Originally Posted by honkj

hmmm, i did your change, and only your change, I used to get:

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


now after your change, i get this

10/7/12 4:02:08.720 AM mdworker[11247]: Unable to talk to lsboxd
10/7/12 4:02:08.722 AM mdworker[11248]: Unable to talk to lsboxd


so it fixed something, but there is still some more to look for????

Same as honkj here -- I followed phobox's directions and now I've gone from having lsboxd/mdworker deny messages every two to four minutes to ONE "Unable to talk to lsboxd" error in almost three HOURS.

Hope my Mac stops freezing!

[DOlsson]

After doing this, and deleting that the stuff in the /System/Library/Caches and then doing a Safeboot - everything seems ok! No more messages - so far

Originally Posted by phobox

You can completely fix all the mdworker related sandbox errors in Console (including the 'cannot talk to lsboxd') by editing the system.sb profile rather than the mdworker ones. The system.sb file is used by all Apple system processes that run under the sandbox, including mdworker. If you modify this file (which is located in /System/Library/Sandbox/Profiles) to include:

(allow mach-lookup (global-name "com.apple.ls.boxd"))

(allow mach-lookup (local-name "com.apple.ls.boxd"))

This will stop all the lsbox related mdworker issues.

I must warn however that modifying this file is potentially dangerous if you're not really sure what you're doing. Take a backup of it just in case. And only add the lines above, do not modify anything else.

[agentx]

I am a Mac/Linux and Windows when i have to System Admin.
I manage lots of machines.

1) No OS (operating system) is perfect......get over it....

2) MOST USERS DO NOT KNOW ANYTHING ABOUT CONSOLE MESSAGES AND PANIC WHEN THEY SEE SOMETHING IN THERE. Please let us pros unravel the enigma code and get on with your life.

3) ANYONE ADVISING A RE-INSTALL for minor issues is a total Numb Nut. A reinstall will not sort most issues out anyway as restoring a User folder will more than likely bring the same problems back anyway. We very rarely have to reinstall the OS (cough apart from Windows).

4) Goto a site with people that know there arse from elbow to get advice.

The real question is "Is the machine working" if YES then get on and use it and stop trying to solve "problems" that frankly are not affecting anything anyway.

There was an issues with Lion 10.7.5 update and Time machine which screwed indexing a Supplemental update resolves this and 10.8.2 has same errors......but overall Apple cannot even get their own Sandboxing right yet...wait for 10.8.3 and see what gets fixed and broken ;-)

[clayj]

Originally Posted by clayj

Same as honkj here -- I followed phobox's directions and now I've gone from having lsboxd/mdworker deny messages every two to four minutes to ONE "Unable to talk to lsboxd" error in almost three HOURS.

Hope my Mac stops freezing!

Nope -- froze up again this morning. This is three freezes in three days.

Apple -- FIX THIS PROBLEM NOW. I am getting ready to start telling people NOT to buy Macs. I've never had this sort of problem with Windows.

[clayj]

One thought: Does this always happen (the freezing thing) when you are away from your machine? If so, what happens if you disable your screen saver and just let the Energy Saver turn off your monitor?

[cascaman]

I don't care about console messages that I actually don't know wether they are errors or can cause problems or are (more or less) normal. The problem here is that my time machine HD (I don't know the other ones, because I can't hear them, but it is posible) is reindexig and reindexing and reindexing....
It's true that starting up in safe mode has stopped this behaviour, but I have read that probably it will continue to reindex again in a few days. That's the problem, not the console messages.

[clayj]

Not to jinx myself, but I've been over 24 hours now without any freezing after disabling my screen saver. Can anyone else try this and see if it helps?

[clayj]

Originally Posted by clayj

Not to jinx myself, but I've been over 24 hours now without any freezing after disabling my screen saver. Can anyone else try this and see if it helps?

Four days have passed since I disabled my screen saver and still no freezes. I am convinced that the screen saver (Flurry, in my case) has something to do with the Mac freezing.

Can anyone else please try disabling their screen saver and see if this helps?

[BRLawyer]

Originally Posted by clayj

Four days have passed since I disabled my screen saver and still no freezes. I am convinced that the screen saver (Flurry, in my case) has something to do with the Mac freezing.

Can anyone else please try disabling their screen saver and see if this helps?

Stupid question: how does one DISABLE the screen saver? I couldn't find any such option.