10.8.2 - mdworker: Unable to talk to lsboxd

Discussion in 'OS X Mountain Lion (10.8)' started by kbmb, Sep 19, 2012.

  1. macrumors 68030

    kbmb

    Joined:
    Mar 13, 2007
    Location:
    NH
    #1
    Can anyone look in their system.log and see if you have any messages similar to:

    Not really having any issues....but did start noticing these since installing 10.8.2 Combo.

    Thanks for any help.

    -Kevin
     
  2. macrumors 68020

    whsbuss

    Joined:
    May 4, 2010
    Location:
    SE Penna.
    #2
    yep along with some warnings when opening system prefs.
     
  3. thread starter macrumors 68030

    kbmb

    Joined:
    Mar 13, 2007
    Location:
    NH
    #3
    Cool...thanks for the quick response. Doing some searches doesn't turn anything up.....but I did search back through my logs and these didn't start until after I installed 10.8.2.

    -Kevin
     
  4. macrumors member

    Joined:
    Feb 9, 2010
    #4
    I had these. I also noticed that spotlight will randomly start to index my drive even though it is already indexed. It could be related because mdworker and mdimporter are used by spotlight to monitor disk file changes.
     
  5. macrumors 6502

    gwang73

    Joined:
    Jun 14, 2009
    Location:
    San Francisco Area
    #5
    I have these as well since the update to 10.8.2. Didn't have them before either.
     
  6. thread starter macrumors 68030

    kbmb

    Joined:
    Mar 13, 2007
    Location:
    NH
    #6
    Thanks everyone. Good to know I'm not alone. Not having any issues with it...just noticing.

    -Kevin

    ----------

    Did you just start noticing Spotlight in the menubar having the little dot? Does performance suffer?

    I haven't had this happen...but I wonder if a rebuild of Spotlight DB would fix it.

    -Kevin
     
  7. macrumors 6502

    gwang73

    Joined:
    Jun 14, 2009
    Location:
    San Francisco Area
    #7
    I rebuilt the spotlight index and the message is still coming up. I haven't noticed Spotlight automatically rebuilding my index randomly before or now.

    Not causing any issues on my system, just with my OCD :)
     
  8. macrumors newbie

    Joined:
    Sep 20, 2012
    #8
    I have got the same problem here. Mdworker and Mds take up between 40% and 60% of my CPU resources. Excluding all drives from Spotlight does not make a difference. Neither does reindexing.

    It makes using my Mac virtually impossible – the fans keep spinning.
     
  9. macrumors newbie

    Joined:
    Sep 20, 2012
    #9
    I am having same problem. Updated to Mountain Lion 10.8.2 today. Also having trouble with it going to sleep randomly (when on battery power). Mine is a 2.6Ghz rMBP and it is 3 weeks old and I have nothing but regrets in buying it. My "e" key grinds when you push it, the battery doesn't last very long (and no improvement with 10.8.2). My MBP 17 was solo much more reliable....I am really disappointed with the machine (when it runs, it is fast, but it's unreliable)...:(
     
  10. Guest

    Joined:
    Apr 17, 2005
    Location:
    Currently in Switzerland
    #10
    I am having the same issue, which seems to be related to wake-from-sleep problems since updating to 10.8.2...my computer is awake but the screen is dark. Any tips?
     
  11. macrumors regular

    Joined:
    Sep 24, 2011
    #11
    I'm having the exact same problem. Just noticed it today.

    No sleep even though screen is dark. Increased MDS (spotlight) activity and increased sandboxd activity.
     
  12. macrumors 6502

    gwang73

    Joined:
    Jun 14, 2009
    Location:
    San Francisco Area
    #12
    No issues with sleep here but followed your advice on removing the /Library/Caches/com.apple.coresymbolicationd folder. You'll need to CMD-I and add permissions for admin or your username before deleting.

    I didn't have enough patience to see if it fixed it or not, but I re-installed ML by rebooting into recovery mode, CMD-R, and re-installed ML. I no longer get any mdworker errors in system logs. After re-install, the com.apple.coresymbolicationd folder is no longer there.
     
  13. Guest

    Joined:
    Apr 17, 2005
    Location:
    Currently in Switzerland
    #13
    Deactivating Wake for Network Access may also help...
     
  14. thread starter macrumors 68030

    kbmb

    Joined:
    Mar 13, 2007
    Location:
    NH
    #14
    Again, as a reminder I'm not really seeing any issues with my machine....or at least not issues that I am noticing.....I just see the errors.

    I did try this morning clearing both /Library/Caches and ~/Library/Caches

    Didn't help....still seeing the errors in console.

    -Kevin
     
  15. qap
    macrumors regular

    qap

    Joined:
    Mar 29, 2011
    Location:
    Udine, Italy
    #15
    Same here after .2 update :confused: But no issue, all works fine!
     
  16. macrumors newbie

    Joined:
    Sep 24, 2012
    #16
    Hi,

    I have noticed those lines in the logs

    Issues for me so far :

    - fan is acting weird (starting and going up at times it did not use to)
    - can not recover from black screen after sleep (I have to switch off one of my firewire drives to be able to wake up)

    maybe those symptoms are not related but I thought I'd add to the reports
     
  17. macrumors regular

    Joined:
    Mar 6, 2011
    #17
    I'm also seeing these log entries after the .2 update.

    Also, like other posters in this thread, I don't think my iMac is ever sleeping as it should. The screen turns itself off, and I'm greeted with a password prompt when I wake the screen up again, but the console will be full of entries across the whole time that the computer should've been sleeping.

    I've also noticed that the iMac is always available over my LAN, further suggesting that it's not actually sleeping. At first I thought the wake for network access problems had FINALLY been fixed, but obviously this turned out to be wishful thinking!
     
  18. macrumors newbie

    Joined:
    Aug 1, 2010
    Location:
    Tahiti
    #18
    Hi,

    As stated here, you should delete this file :

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

    Can you test this and give us feedback ?

    Regards
     
  19. thread starter macrumors 68030

    kbmb

    Joined:
    Mar 13, 2007
    Location:
    NH
    #19
    This has nothing to do with the lsboxd issue.

    -Kevin
     
  20. macrumors regular

    Joined:
    Mar 6, 2011
    #20
    I've been paying a bit more attention to my iMac since posting in this thread, and have since discovered that it is not going to sleep at all. Last night, I even manually sent it to sleep at around 10:45pm. Checking the log again this morning, it seems that it woke up at 11:10pm, with the log entry '24/09/2012 23:09:00.000 kernel[0]: Network wake from AirPort_AtherosNewma40' denoting the presumable reason, and then from 11:15pm onwards the log is full of '24/09/2012 23:16:50.129 mdworker[8880]: Unable to talk to lsboxd', '24/09/2012 23:16:50.181 sandboxd[8883]: ([8880]) mdworker(8880) deny mach-lookup com.apple.ls.boxd' and '24/09/2012 23:16:50.000 kernel[0]: Sandbox: sandboxd(8883) deny mach-lookup com.apple.coresymbolicationd'.

    I'm pretty pissed off about this: I've had enough trouble over the last year with waking for network access not working; now my £1,000 computer can't even go to sleep reliably. Pathetic.
     
  21. macrumors 65816

    Joined:
    Jun 30, 2007
    #21
    Having the same problem. Wondered why the disk was thrashing when the Time Machine icon was not in use. Something is definitely amiss in Mountain Lion land; there's no reason Spotlight should be completely reindexing the drive often.
     
  22. macrumors newbie

    Joined:
    Sep 24, 2012
    Location:
    Spey Valley
    #22
    Kevin

    I had the same problem - Safe Boot is your friend. ;)

    Mac

    -:apple:iMac-:apple:iPad-:apple:iPhone
     
  23. thread starter macrumors 68030

    kbmb

    Joined:
    Mar 13, 2007
    Location:
    NH
    #23
    So you are saying after safe-booting......the errors in console went away? Or are you talking about the sleep issues? And did you do anything in safe boot....or just restart normally afterwards?

    -Kevin
     
  24. macrumors newbie

    Joined:
    Sep 24, 2012
    Location:
    Spey Valley
    #24
    Kevin

    Safe Boot your machine - do nothing until complete -restart as normal - see if that helps with console errors - may even help the sleep issues.

    Mac

    :apple:iMac-:apple:iPad-:apple:iPhone
     
  25. thread starter macrumors 68030

    kbmb

    Joined:
    Mar 13, 2007
    Location:
    NH
    #25
    Ok done. Looking good so far......haven't seen the error pop back up.

    I did clear caches this weekend....guess I should have just done a safe boot.

    Will update if the error comes back.

    -Kevin
     

Share This Page