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

Error: mdworker lsboxd deny mach-lookup

Getting the following, every 5 min, in Console.


9/25/12 10:35:21.415 AM mdworker[503]: Unable to talk to lsboxd

9/25/12 10:35:21.419 AM mdworker[504]: Unable to talk to lsboxd

9/25/12 10:35:21.474 AM sandboxd[505]: ([503]) mdworker(503) deny mach-lookup com.apple.ls.boxd

9/25/12 10:35:21.480 AM sandboxd[505]: ([504]) mdworker(504) deny mach-lookup com.apple.ls.boxd

MacBook Pro with Retina display, OS X Mountain Lion, Apple Mail 6.0 (1485)

Posted on Sep 25, 2012 8:52 AM

Reply
19 replies

Sep 26, 2012 9:27 AM in response to jacooper11

I had the same issue. Place the retina to sleep and closed the lid. Came back next morning to find the Retina fans running. Opened it up to a black screen and unresponsive. Had to reboot it holding the power button down. The Retina had been running all night with console messages every 2-5 minutes stating:

mdworker[18520]: Unable to talk to lsboxd

sandboxd[18521]: ([18520]) mdworker(18520) deny mach-lookup com.apple.ls.boxd

kernel[0]: Sandbox: sandboxd(20128) deny mach-lookup com.apple.coresymbolicationd

Sep 26, 2012 11:25 AM in response to Pedro Gelabert

I'm seeing the same issue and I think it started after the 10.8.2 update on my 2012 MBP (not retina). I usually do a command-option-eject to put the machine to sleep when I leave work at night but the last three mornings when I get back to work the MBP will not wake up and I have to hold the power button to force it off. The console is full of the following messages, even during the time when it should have been sleeping:


Sep 25 00:18:55 kernel[0]: Sandbox: sandboxd(3819) deny mach-lookup com.apple.coresymbolicationd

Sep 25 00:20:56 mdworker[3822]: Unable to talk to lsboxd

Sep 25 00:20:56 mdworker[3823]: Unable to talk to lsboxd

Sep 25 00:20:56 kernel[0]: Sandbox: sandboxd(3824) deny mach-lookup com.apple.coresymbolicationd

Sep 25 00:20:56 sandboxd[3824] ([3822]): mdworker(3822) deny mach-lookup com.apple.ls.boxd

Sep 25 00:20:56 sandboxd[3824] ([3823]): mdworker(3823) deny mach-lookup com.apple.ls.boxd


Also, when re-start it indexes my external Time Machine hard drive for what seems like hours - never used to do that.

Sep 27, 2012 6:14 AM in response to jacooper11

When I got to work this morning, my MBP was not locked up and came to life as soon as I opened the lid. I also checked the system.log and there was no activity from the time I did the command-option-eject last night until I opened the lid this morning - just like it should be.


I'm afraid I wasn't very scientific on my troubleshooting. I did all of the following based on different discussions:


1. set hibernate mode to 0 (sudo pmset -a hibernatemode 0)

2. shut off WiFi (I've got a direct wired connection)

3. turned off "Wake for network access"

4. removed /System/Library/LaunchAgents/com.apple.afpstat.plist

5. removed directory /Library/Caches/com.apple.coresymbolicationd

6. booted into safe mode, then re-booted


I'm not sure if it was any one thing or some combination, but it seemed to fix the problem. At least for one day.

Oct 1, 2012 4:49 PM in response to rmitchell2301

I see the same issue. If I sleep my Retina MacBook with an external display connected, the console shows that it waked-up every two hours, and eventually hang. When I open up the Retina, the screen is blank, the fans are running, and the case is hot. If disconnect the external monitor, then sleep. I have no problem waking up the Retina.


I also turned off the Energy Saver -> Wake for Network Access. This seems to take care of the problem of waking up every couple of hours. Maybe that will also fixed the failure to wake up from sleep. I will test it again tonight.

Oct 6, 2012 3:31 AM in response to Pedro Gelabert

Had same issue for some weeks now (MBP not sleeping, then crashing, in my case a mid-2009 model), with external (Dell) display and keyboard connected. Burned out one of the fans, since replaced. I thought it was the Microsoft wireless keyboard, so upgraded to Apple Keyboard and Magic Mouse, but no difference. Will try disabling Wake for Network Access and Safe Reboot.


This message is in the system log:


Oct 4 08:00:14 localhost kernel[0]: Sleep failure code 0x00008000 0x27006900


This was logged around the time I forced a restart with the power button.


Ben

Oct 12, 2012 9:43 AM in response to Pedro Gelabert

I ended up going to my local Genius Bar, where they figured my MacBook Pro was overheating. The Genius wisked the machine away, and came back a little later saying he had removed the logic board and reapplied thermal paste. The machine appears now to be working, so I think it is likely it was overheating when left on overnight (performing backups and maintenance), hence crashed by morning.

Dec 27, 2012 10:18 AM in response to jacooper11

Try this:


  1. Restart your computer in safe mode (read that link for more info about what it will do.) This is done by restarting as normal from the Apple menu, then holding down shift after you hear the Apple noise on startup. Note, you must wait to hold down shift until after the Apple noise has started. As proof that you're loading into safe mode, you'll see a little progress bar beneath the Apple and you'll have to wait a while.
  2. Once the wait is over, you can log into OSX, but since you're still in safe mode you'll want to restart again, this time without holding shift.
  3. Log in again, check your Console -- if this worked, the error should be gone.

See: http://www.princeton.edu/~jcjb/docs/osx_error_fix/


A simple solution that worked for me.


Cheers

Error: mdworker lsboxd deny mach-lookup

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