Skip navigation

Sandboxd error messages

14705 Views 23 Replies Latest reply: Jun 30, 2013 1:54 AM by AndrewMacintosh RSS
1 2 Previous Next
Mika Inkinen Level 2 Level 2 (235 points)
Currently Being Moderated
Nov 11, 2012 10:02 AM

I seem to get a variety of sandboxd related error messages that I have no idea how to solve. I've tried looking here, but none of the topics have quite had the exact same issue.

 

As background - I recently bought a 15" retina MacBook Pro, and used TimeMachine to move over all my files from my old late 2007 model iMac. But I ran into a problem with the MBP not waking the screen up after the energy saver has turned it off. And upon inspecting my Console, I discovered a raft of different sandboxd related error messages. I also checked the iMac (also running Mountain Lion), and the error messages were there too.

 

Many of them seem to involve the mdworker:

 

11/11/2012 17:38:23.375 mdworker[1966]: Unable to talk to lsboxd

11/11/2012 17:38:23.380 mdworker[1965]: Unable to talk to lsboxd

11/11/2012 17:38:23.435 sandboxd[1967]: ([1966]) mdworker(1966) deny mach-lookup com.apple.ls.boxd

11/11/2012 17:38:23.440 sandboxd[1967]: ([1965]) mdworker(1965) deny mach-lookup com.apple.ls.boxd

 

Others involve qtkits and coresymbolicationd

11/11/2012 17:29:04.050 sandboxd[1901]: ([1899]) com.apple.qtkits(1899) deny system-fsctl 0x7a0c

11/11/2012 17:29:04.124 sandboxd[1901]: ([1899]) com.apple.qtkits(1899) deny system-fsctl 0x7a0c

11/11/2012 17:29:09.725 sandboxd[1901]: ([1899]) com.apple.qtkits(1899) deny system-fsctl 0x7a0c

11/11/2012 17:29:09.733 sandboxd[1901]: ([1899]) com.apple.qtkits(1899) deny system-fsctl 0x7a0c

11/11/2012 17:29:09.741 sandboxd[1901]: ([1899]) com.apple.qtkits(1899) deny system-fsctl 0x7a0c

11/11/2012 17:29:10.310 sandboxd[1901]: ([1899]) com.apple.qtkits(1899) deny system-fsctl 0x7a0c

11/11/2012 17:29:10.317 sandboxd[1901]: ([1899]) com.apple.qtkits(1899) deny system-fsctl 0x7a0c

11/11/2012 17:29:10.326 sandboxd[1901]: ([1899]) com.apple.qtkits(1899) deny system-fsctl 0x7a0c

11/11/2012 17:29:10.504 sandboxd[1901]: ([1899]) com.apple.qtkits(1899) deny system-fsctl 0x7a0c

11/11/2012 17:29:10.525 sandboxd[1901]: ([1899]) com.apple.qtkits(1899) deny system-fsctl 0x7a0c

11/11/2012 17:29:10.545 sandboxd[1901]: ([1899]) com.apple.qtkits(1899) deny system-fsctl 0x7a0c

11/11/2012 17:30:16.927 com.apple.launchd[1]: (com.apple.quicklook.satellite.5BCCE65C-378E-4205-9FCA-DEF8B620C4A0[1898]) Exit timeout elapsed (20 seconds). Killing

11/11/2012 17:30:36.927 com.apple.launchd[1]: (com.apple.qtkitserver[1899]) Exit timeout elapsed (20 seconds). Killing

11/11/2012 17:30:36.927 com.apple.launchd[1]: (com.apple.qtkittrustedmoviesservice[1900]) Could not terminate job: 3: No such process

11/11/2012 17:30:36.927 com.apple.launchd[1]: (com.apple.qtkittrustedmoviesservice[1900]) Using fallback option to terminate job...

11/11/2012 17:30:44.969 sandboxd[1915]: ([1913]) com.apple.qtkits(1913) deny system-fsctl 0x7a0c

11/11/2012 17:30:44.000 kernel[0]: Sandbox: sandboxd(1915) deny mach-lookup com.apple.coresymbolicationd

 

Earlier messages also said:

11/11/2012 14:59:37.225 sandboxd[105]: ([209]) com.apple.qtkits(209) deny file-read-data /Users/*username*/Downloads

11/11/2012 14:59:37.376 sandboxd[105]: ([209]) com.apple.qtkits(209) deny file-read-data /Users/*username*/Downloads

11/11/2012 14:59:37.527 sandboxd[105]: ([209]) com.apple.qtkits(209) deny file-read-data /Users/*username*/Downloads

11/11/2012 14:59:37.667 sandboxd[105]: ([209]) com.apple.qtkits(209) deny file-read-data /Users/*username*/Downloads

11/11/2012 14:59:37.759 sandboxd[105]: ([209]) com.apple.qtkits(209) deny file-read-data /Users/*username*/Downloads

11/11/2012 14:59:37.908 sandboxd[105]: ([209]) com.apple.qtkits(209) deny file-read-data /Users/*username*/Downloads

 

 

What processes cause these errors? I've been trying to figure that out, but haven't had much luck.

MacBook Pro with Retina display, OS X Mountain Lion (10.8.2), 16GB RAM, 512GB SSD, 15" display
  • Kappy Level 10 Level 10 (221,025 points)
    Currently Being Moderated
    Nov 11, 2012 10:10 AM (in response to Mika Inkinen)

    I think you have restored what you should not have restored. I recommend this:

     

    Install or Reinstall Lion/Mountain Lion from Scratch

     

    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.

     

    Boot to the Recovery HD:

     

    Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.

     

    Erase the hard drive:

     

      1. Select Disk Utility from the main menu and click on the Continue button.

     

      2. After DU loads select your startup volume (usually Macintosh HD) from the

          left side list. Click on the Erase tab in the DU main window.

     

      3. Set the format type to Mac OS Extended (Journaled.) Optionally, click on

            the Security button and set the Zero Data option to one-pass. Click on

          the Erase button and wait until the process has completed.

     

      4. Quit DU and return to the main menu.

     

    Reinstall Lion: Select Reinstall Lion/Mountain Lion and click on the Install button.

     

    Note: You will need an active Internet connection. I suggest using Ethernet if possible

                because it is three times faster than wireless.

     

    Afterward you can restore only your Home folder and third-party applications. Before you restore your files check your console log to see that the repetitive messages have ceased.

  • Kappy Level 10 Level 10 (221,025 points)
    Currently Being Moderated
    Nov 11, 2012 10:39 AM (in response to Mika Inkinen)

    I do have a local copy of Mountain Lion as well, is there any way of using that instead of having to re-download it? e.g. starting it in target disk mode and installing it via my iMac, or rebooting from an external OSX drive and installing it from there?

     

    Then just open the install application and go from there. That will be faster than downloading it. Be sure you have the installer in your Downloads folder. Don't run it from the Applications folder or it will be deleted after the installation is complete.

  • Kappy Level 10 Level 10 (221,025 points)
    Currently Being Moderated
    Nov 13, 2012 2:51 PM (in response to Mika Inkinen)

    Got me. Reading console log entries is one thing. Making heads or tails of them is quite another.

  • kylescottmcgill Calculating status...
    Currently Being Moderated
    Nov 15, 2012 2:27 AM (in response to Kappy)

    I had similar issues, however they only became a problem a couple of weeks down the track after a restore.

     

    Problem: Time Machine taking a long time to build/index/query files on the system after an upgrade/restore.

     

    So far i have fixed this in two different ways.:

     

         1) open terminal and running

              sudo chown -R <your-user>:staff /home/<your-user>/

            This fixed a lot of file permissions for Time Machine, and some of the applications i was using, everything in this directory is owned by you, so it is safe to make it yours again!

         2) If you open Console and keep a close eye on it, you can see the mdworker and the sandbox daemons having trouble, but to find out what files it is looking for you can run this command inside Terminal

              sudo opensnoop -n mdworker

             This will query the openfiles that mdworker is looking/using, in the first column we can also see the UID and the Process ID, if you are finding hangs, there is normal a problem with this file, to fix this you will need to Google the file manually to find out what it does and does not, if its in your /home/<user> directory your pretty safe. If your like me, i have brew installed, and the permissions for brew can somtimes become overridden by Mac, and manually i have to reset them back to my user. To keep this short, tread with caution, and keep a backup!

     

    Hope this helps, its been a long night but i managed to get rid of 90% of them and my mac is a lot happier!

     

    Thanks!

     

    - Kyle

  • kylescottmcgill Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 19, 2012 5:39 PM (in response to Mika Inkinen)

    Hi Mika,

     

    Sorry i did mean /Users/<your-users> and also i would like to apologise for the lack of grammar in that last post...

     

    Did opensnoop give you any more clues as to what files were causing problems?

     

    At the moment i still get some, but no-where as many as i used to, however it looks like you still get quite a lot.

     

    Thanks!

     

    - Kyle

  • Kappy Level 10 Level 10 (221,025 points)
    Currently Being Moderated
    Nov 19, 2012 6:30 PM (in response to Mika Inkinen)

    Yes, you could do that, but to connect the two in Target Disk Mode requires both computers be connected by a FireWire cable. You can also do it from an external drive.

  • nevasha Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 7, 2012 6:23 PM (in response to Mika Inkinen)

    Thanks Kyle for sharing, as this resoved all but the following error message that I am aware of hot off the screen

     

    Dec  7 18:14:23  kernel[0]: IOHIDSystem cursor update overdue. Resending.

    Dec  7 18:14:42  mdworker[2956]: Unable to talk to lsboxd

    Dec  7 18:14:42  mdworker[2955]: Unable to talk to lsboxd

    Dec  7 18:14:43  kernel[0]: Sandbox: sandboxd(2959) deny mach-lookup com.apple.coresymbolicationd

    Dec  7 18:14:44  sandboxd[2959] ([2956]): mdworker(2956) deny mach-lookup com.apple.ls.boxd

    Dec  7 18:14:44  sandboxd[2959] ([2955]): mdworker(2955) deny mach-lookup com.apple.ls.boxd

    Dec  7 18:16:17  kernel[0]: IOHIDSystem cursor update overdue. Resending.

    Dec  7 18:16:47 --- last message repeated 1 time ---

    Dec  7 18:17:01  mdworker[2965]: Unable to talk to lsboxd

    Dec  7 18:17:01  mdworker[2964]: Unable to talk to lsboxd

    Dec  7 18:17:02  kernel[0]: Sandbox: sandboxd(2969) deny mach-lookup com.apple.coresymbolicationd

    Dec  7 18:17:03  sandboxd[2969] ([2965]): mdworker(2965) deny mach-lookup com.apple.ls.boxd

    Dec  7 18:17:03  sandboxd[2969] ([2964]): mdworker(2964) deny mach-lookup com.apple.ls.boxd

     

     

    Like Mika I don't wish to rebuild the system, hate to loose my app related prefrences, bookmarks the lot.

    This is now feeling lot like my old Windows XP box !!

  • nevasha Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 7, 2012 7:05 PM (in response to kylescottmcgill)

    Kyle,

     

    Can you qualify the following:

     

    This will query the openfiles that mdworker is looking/using, in the first column we can also see the UID and the Process ID, if you are finding hangs -

     

    as in how do I identify what is hanging?

  • kylescottmcgill Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 7, 2012 7:16 PM (in response to nevasha)

    Hi nevasha,

     

    In my particular case a Hang resulted in permission errors being thrown and a process looping over the same files (trying harder to index the file).

     

    To more or less sum up my experience, i have yet to have any real problems after a general cleanup, i still have the odd console error message come through, but all and all my Mac is running fine. On numerous websites people have commented its not worth a rebuild, and it doesnt cause any real problems. Long Index Times by Spotlight occur every now and then, but its not something too bad.

     

    I hope this helps!

     

    Thanks!

     

    - Kyle

1 2 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.