MDWorker on strike? Not talking to lsBoxd?

Have you started to notice these error messages in your console log?

  • mdworker[299]: Unable to talk to lsboxd
  • sandboxd[296] ([299]): mdworker(299) deny mach-lookup com.apple.ls.boxd
  • kernel[0]: Sandbox: sandboxd(314) deny mach-lookup com.apple.coresymbolicationd

Then your not alone…

In most cases, this appears to have started with Mountain Lion 10.8.2….

Some symptoms that have been reported are:

  • Spotlight randomly starting to reindex drives
  • High CPU activity spikes
  • Sleep issues, with computers not always waking from sleep…

At this point, performing a Safe Boot (booting in Safe Mode), seems to help eliminate or at least reduce the number of times this occurs.  One user reported that they went from thousands of console entries to 2 per day….  Your mileage will vary though…

4 thoughts on “MDWorker on strike? Not talking to lsBoxd?

  1. Did the safe reset – machine quiet for 2 days – started again after I set up the network backup via Time Machine

  2. This is happening to me too. I have Power Nap enabled and the fans are running after leaving it over night. When I try to wake up my computer it doesn’t respond. I also have Time Machine backup over the network, so that could be part of the issue.

  3. Are we even sure these are errors or even warnings? I just see so many novices who read through their console messages and then do really stupid things to their systems in an effort to “fix” what they perceive to be a problem

Leave a Reply

Your email address will not be published.

*