PDA

View Full Version : 10.8.2 - mdworker: Unable to talk to lsboxd




kbmb
Sep 19, 2012, 09:40 PM
Can anyone look in their system.log and see if you have any messages similar to:

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


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

Thanks for any help.

-Kevin



whsbuss
Sep 19, 2012, 09:43 PM
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

yep along with some warnings when opening system prefs.

kbmb
Sep 19, 2012, 09:44 PM
yep along with some warnings when opening system prefs.

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

jianglai
Sep 19, 2012, 10:31 PM
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

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.

gwang73
Sep 20, 2012, 12:49 AM
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

I have these as well since the update to 10.8.2. Didn't have them before either.

kbmb
Sep 20, 2012, 08:31 AM
Thanks everyone. Good to know I'm not alone. Not having any issues with it...just noticing.

-Kevin

----------

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.

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

gwang73
Sep 20, 2012, 09:58 AM
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 :)

jonathan.muth
Sep 20, 2012, 09:59 AM
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.

bobkivi
Sep 20, 2012, 09:05 PM
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)...:(

50548
Sep 21, 2012, 10:49 AM
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

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?

blatopilot
Sep 21, 2012, 06:34 PM
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?

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.

gwang73
Sep 21, 2012, 08:51 PM
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?

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.

50548
Sep 22, 2012, 03:03 AM
Deactivating Wake for Network Access may also help...

kbmb
Sep 22, 2012, 07:45 AM
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

qap
Sep 23, 2012, 09:32 AM
Same here after .2 update :confused: But no issue, all works fine!

resume
Sep 24, 2012, 02:47 AM
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

EmpyreanUK
Sep 24, 2012, 09:17 AM
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!

tahitibub
Sep 24, 2012, 04:31 PM
Hi,

As stated here (https://discussions.apple.com/thread/4213550?start=0&tstart=0), you should delete this file :

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

Can you test this and give us feedback ?

Regards

kbmb
Sep 24, 2012, 04:48 PM
Hi,

As stated here (https://discussions.apple.com/thread/4213550?start=0&tstart=0), you should delete this file :

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

Can you test this and give us feedback ?

Regards

This has nothing to do with the lsboxd issue.

-Kevin

EmpyreanUK
Sep 25, 2012, 02:27 AM
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.

petsounds
Sep 25, 2012, 03:11 AM
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.

whiskymac
Sep 25, 2012, 05:55 AM
Kevin

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

Mac

-:apple:iMac-:apple:iPad-:apple:iPhone

kbmb
Sep 25, 2012, 01:22 PM
Kevin

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

Mac

-:apple:iMac-:apple:iPad-:apple:iPhone

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

whiskymac
Sep 25, 2012, 02:05 PM
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

kbmb
Sep 25, 2012, 03:04 PM
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

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

EmpyreanUK
Sep 25, 2012, 05:09 PM
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

Thanks for taking the time to post this advice, whiskymac. I just tried to safe boot my Mac *I have File Vault enabled, so I had to log in before the OS loaded. As the OS loaded, I got the spinning pin wheel as normal, only it remained on that screen for longer than normal. The system then restarted itself, without the OS progressing beyond the loading screen and displaying the desktop. Is this normal?

kbmb
Sep 25, 2012, 05:37 PM
So far so good after the safe boot. The only message related to lsboxd is:

Sep 25 18:09:29 lsboxd[218]: @AE relay 4755524c:4755524c

Doesn't happen as frequently as the other message.

I never seemed to have the sleep or spotlight issues, so will be interested if someone who had those can see if the safeboot fixes it or not.

-Kevin

Joesg
Sep 25, 2012, 05:50 PM
I'll add my name to the list that this bug affects. I first noticed this when going through my console logs to figure out why it takes so long to wake from power nap. I'm not sure if this is part of the reason or not.

I get 100s of these every time I wake from power nap:
mdworker[2357]: Unable to talk to lsboxd
sandboxd[2359]: ([2357]) mdworker(2357) deny mach-lookup com.apple.ls.boxd

whiskymac
Sep 25, 2012, 09:20 PM
Thanks for taking the time to post this advice, whiskymac. I just tried to safe boot my Mac *I have File Vault enabled, so I had to log in before the OS loaded. As the OS loaded, I got the spinning pin wheel as normal, only it remained on that screen for longer than normal. The system then restarted itself, without the OS progressing beyond the loading screen and displaying the desktop. Is this normal?

Hi EmpyreanUK

If at all possible - could you disable FV and then try a safe boot.

Mac

:apple:iMac-:apple:iPad-:apple:iPhone

flazcano
Sep 26, 2012, 11:53 AM
yesterday i reinstall ML, and after many hours, the problem is back:

Sep 26 13:50:09 flazcano mdworker[2093]: Unable to talk to lsboxd
Sep 26 13:50:09 flazcano sandboxd[2098] ([2093]): mdworker(2093) deny mach-lookup com.apple.ls.boxd
Sep 26 13:50:10 flazcano kernel[0]: Sandbox: sandboxd(2098) deny mach-lookup com.apple.coresymbolicationd

kbmb
Sep 26, 2012, 11:55 AM
So yesterday after my safe boot......I only had 1 instance of the Unable to talk to lsboxd message.

This morning it occurred again but just twice in the morning. None since.

So clearly something is still causing it....it's just not as frequent.

-Kevin

Joesg
Sep 26, 2012, 05:58 PM
I'll add my name to the list that this bug affects. I first noticed this when going through my console logs to figure out why it takes so long to wake from power nap. I'm not sure if this is part of the reason or not.

I get 100s of these every time I wake from power nap:
mdworker[2357]: Unable to talk to lsboxd
sandboxd[2359]: ([2357]) mdworker(2357) deny mach-lookup com.apple.ls.boxd

So I booted into safe mode, as was suggested, and these no longer show up in my console logs. I haven't seen a single instance since rebooting. Additionally, my wake times are much improved. I'll keep an eye out in case these return.

EmpyreanUK
Sep 27, 2012, 03:12 AM
Hi EmpyreanUK

If at all possible - could you disable FV and then try a safe boot.

Mac

:apple:iMac-:apple:iPad-:apple:iPhone
Hi Whiskymac, thank you very much for taking the time to reply!

I retried booting into safe mode, with File Vault still enabled, and the same thing happened: during boot up, while the pinwheel was spinning with the progress bar underneath, the system reset itself. After it had completed booting, I checked the system log, and there were lots of messages regarding safe boot. I didn't have time to try disabling FV and then safe booting at that time, so I left the computer. When I came back, the system log was still open, and I noticed that there were no lsboxd-related messages. After two days, there had only been a couple, so I think whatever was causing it to report these messages so persistently has been resolved by my presumably un- or half-successful safe boot.

At first I thought this had also resolved the issues I was having with the system not going to sleep correctly. However, over the past day or so I have been monitoring the logs and have concluded that the system is in fact still not sleeping, but is just not filling the logs with anything during this idle 'awake' time. I now suspect that the lsboxd issue was not causing the system to remain awake, but because it was anyway awake, the lsboxd problem was able to keep on repeating itself, thus filling the log with error messages.

Regarding the non-sleeping issue, I just used the pmset command in Terminal to review the power settings and to check the status of the so-called 'assertions'. pmset reported that there was one process with an assertion set to 'PreventUserIdleSystemSleep', which is what I presume to be happening with my Mac's sleep problems. Believe it or not, the process in question was iTunes. I've since quit iTunes, and the assertion is no longer reported by pmset.

I'll report back on whether this works or not, but in the meantime, should I make a new thread regarding this? I'm no-longer convinced that at the very least my sleep problems are being caused by lsboxd, which is after all the topic of this discussion.

cetesse
Sep 27, 2012, 07:35 PM
Also have the dreaded freeze daily.

I have disconnected USB external hard drive.
Removed SoundFlower extension
And today got the longest usage by not using Chrome

Last set of messages were:

(Any other solutions to try????)

9/27/12 6:51:07.000 PM kernel[0]: Sandbox: sandboxd(20612) deny mach-lookup com.apple.coresymbolicationd
9/27/12 6:51:07.657 PM sandboxd[20612]: ([20611]) mdworker(20611) deny mach-lookup com.apple.ls.boxd
9/27/12 6:51:12.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 890 wr: 890 q_size: 1024 flags: 0x1
9/27/12 6:51:16.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 635 wr: 635 q_size: 1024 flags: 0x1
9/27/12 6:51:17.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 380 wr: 380 q_size: 1024 flags: 0x1
9/27/12 6:51:22.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 125 wr: 125 q_size: 1024 flags: 0x1
9/27/12 6:51:22.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 894 wr: 894 q_size: 1024 flags: 0x1
9/27/12 6:51:32.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 639 wr: 639 q_size: 1024 flags: 0x1
9/27/12 6:51:34.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 384 wr: 384 q_size: 1024 flags: 0x1
9/27/12 6:51:34.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 129 wr: 129 q_size: 1024 flags: 0x1
9/27/12 6:51:38.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 898 wr: 898 q_size: 1024 flags: 0x1
9/27/12 6:51:39.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 643 wr: 643 q_size: 1024 flags: 0x1
9/27/12 6:51:45.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 388 wr: 388 q_size: 1024 flags: 0x1
9/27/12 6:51:49.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 133 wr: 133 q_size: 1024 flags: 0x1
9/27/12 6:51:49.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 902 wr: 902 q_size: 1024 flags: 0x1
9/27/12 6:51:54.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 647 wr: 647 q_size: 1024 flags: 0x1
9/27/12 6:51:54.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 392 wr: 392 q_size: 1024 flags: 0x1
9/27/12 6:51:59.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 137 wr: 137 q_size: 1024 flags: 0x1
9/27/12 6:52:07.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 906 wr: 906 q_size: 1024 flags: 0x1
9/27/12 6:52:08.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 651 wr: 651 q_size: 1024 flags: 0x1
9/27/12 6:52:11.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 396 wr: 396 q_size: 1024 flags: 0x1
9/27/12 6:52:12.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 141 wr: 141 q_size: 1024 flags: 0x1
9/27/12 6:52:16.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 910 wr: 910 q_size: 1024 flags: 0x1
9/27/12 6:52:21.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 655 wr: 655 q_size: 1024 flags: 0x1
9/27/12 6:52:21.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 400 wr: 400 q_size: 1024 flags: 0x1
9/27/12 6:52:26.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 145 wr: 145 q_size: 1024 flags: 0x1
9/27/12 6:52:28.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 914 wr: 914 q_size: 1024 flags: 0x1
9/27/12 6:52:32.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 659 wr: 659 q_size: 1024 flags: 0x1
9/27/12 6:52:36.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 404 wr: 404 q_size: 1024 flags: 0x1
9/27/12 6:52:36.000 PM kernel[0]: [ffffff807e272800][AppleMultitouchDevice::willTerminate] entered
9/27/12 6:52:36.000 PM kernel[0]: [ffffff807e272800][AppleMultitouchDevice::stop] entered
9/27/12 6:52:36.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 149 wr: 149 q_size: 1024 flags: 0x1
9/27/12 6:52:45.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 918 wr: 918 q_size: 1024 flags: 0x1
9/27/12 6:52:46.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 663 wr: 663 q_size: 1024 flags: 0x1
9/27/12 6:52:49.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 408 wr: 408 q_size: 1024 flags: 0x1
9/27/12 6:52:53.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 153 wr: 153 q_size: 1024 flags: 0x1
9/27/12 6:52:53.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 922 wr: 922 q_size: 1024 flags: 0x1
9/27/12 6:53:00.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 667 wr: 667 q_size: 1024 flags: 0x1
9/27/12 6:53:00.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 412 wr: 412 q_size: 1024 flags: 0x1
9/27/12 6:53:05.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 157 wr: 157 q_size: 1024 flags: 0x1
9/27/12 6:53:09.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 926 wr: 926 q_size: 1024 flags: 0x1
9/27/12 6:53:25.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 671 wr: 671 q_size: 1024 flags: 0x1
9/27/12 6:53:33.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 416 wr: 416 q_size: 1024 flags: 0x1
9/27/12 6:53:39.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 161 wr: 161 q_size: 1024 flags: 0x1
9/27/12 6:53:45.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 930 wr: 930 q_size: 1024 flags: 0x1
9/27/12 6:53:50.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 675 wr: 675 q_size: 1024 flags: 0x1
9/27/12 6:54:01.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 420 wr: 420 q_size: 1024 flags: 0x1
9/27/12 6:54:04.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 165 wr: 165 q_size: 1024 flags: 0x1
9/27/12 6:54:08.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 934 wr: 934 q_size: 1024 flags: 0x1
9/27/12 6:54:12.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 679 wr: 679 q_size: 1024 flags: 0x1
9/27/12 6:54:16.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 424 wr: 424 q_size: 1024 flags: 0x1
9/27/12 6:54:20.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 169 wr: 169 q_size: 1024 flags: 0x1
9/27/12 6:54:24.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 938 wr: 938 q_size: 1024 flags: 0x1
9/27/12 6:54:25.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 683 wr: 683 q_size: 1024 flags: 0x1
9/27/12 6:54:31.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 428 wr: 428 q_size: 1024 flags: 0x1
9/27/12 6:54:39.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 173 wr: 173 q_size: 1024 flags: 0x1
9/27/12 6:54:42.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 942 wr: 942 q_size: 1024 flags: 0x1
9/27/12 6:54:42.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 687 wr: 687 q_size: 1024 flags: 0x1
9/27/12 6:54:47.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 432 wr: 432 q_size: 1024 flags: 0x1
9/27/12 6:54:52.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 177 wr: 177 q_size: 1024 flags: 0x1
9/27/12 6:54:54.571 PM mdworker[20619]: Unable to talk to lsboxd
9/27/12 6:54:54.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 946 wr: 946 q_size: 1024 flags: 0x1
9/27/12 6:54:55.000 PM kernel[0]: Sandbox: sandboxd(20620) deny mach-lookup com.apple.coresymbolicationd
9/27/12 6:54:55.516 PM sandboxd[20620]: ([20619]) mdworker(20619) deny mach-lookup com.apple.ls.boxd
9/27/12 6:55:01.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 691 wr: 691 q_size: 1024 flags: 0x1
9/27/12 6:55:05.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 436 wr: 436 q_size: 1024 flags: 0x1
9/27/12 6:55:07.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 181 wr: 181 q_size: 1024 flags: 0x1
9/27/12 6:55:17.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 950 wr: 950 q_size: 1024 flags: 0x1
9/27/12 6:55:19.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 695 wr: 695 q_size: 1024 flags: 0x1
9/27/12 6:55:21.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 440 wr: 440 q_size: 1024 flags: 0x1
9/27/12 6:55:25.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 185 wr: 185 q_size: 1024 flags: 0x1
9/27/12 6:55:26.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 954 wr: 954 q_size: 1024 flags: 0x1
9/27/12 6:55:30.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 699 wr: 699 q_size: 1024 flags: 0x1
9/27/12 6:55:33.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 444 wr: 444 q_size: 1024 flags: 0x1
9/27/12 6:55:35.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 189 wr: 189 q_size: 1024 flags: 0x1
9/27/12 6:55:39.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 958 wr: 958 q_size: 1024 flags: 0x1
9/27/12 6:55:43.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 703 wr: 703 q_size: 1024 flags: 0x1
9/27/12 6:55:49.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 448 wr: 448 q_size: 1024 flags: 0x1
9/27/12 6:55:52.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 193 wr: 193 q_size: 1024 flags: 0x1
9/27/12 6:55:53.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 962 wr: 962 q_size: 1024 flags: 0x1
9/27/12 6:55:57.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 707 wr: 707 q_size: 1024 flags: 0x1
9/27/12 6:55:58.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 452 wr: 452 q_size: 1024 flags: 0x1
9/27/12 6:56:03.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 197 wr: 197 q_size: 1024 flags: 0x1
9/27/12 6:56:07.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 966 wr: 966 q_size: 1024 flags: 0x1
9/27/12 6:56:08.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 711 wr: 711 q_size: 1024 flags: 0x1
9/27/12 6:56:12.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 456 wr: 456 q_size: 1024 flags: 0x1
9/27/12 6:56:13.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 201 wr: 201 q_size: 1024 flags: 0x1
9/27/12 6:56:17.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 970 wr: 970 q_size: 1024 flags: 0x1
9/27/12 6:56:25.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 715 wr: 715 q_size: 1024 flags: 0x1
9/27/12 6:56:27.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 460 wr: 460 q_size: 1024 flags: 0x1
9/27/12 6:56:30.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 205 wr: 205 q_size: 1024 flags: 0x1
9/27/12 6:56:52.686 PM mdworker[20622]: Unable to talk to lsboxd
9/27/12 6:56:53.109 PM sandboxd[20623]: ([20622]) mdworker(20622) deny mach-lookup com.apple.ls.boxd
9/27/12 6:56:53.000 PM kernel[0]: Sandbox: sandboxd(20623) deny mach-lookup com.apple.coresymbolicationd

MacInMotion
Sep 28, 2012, 05:28 PM
I'm having similar problems with my Retina MBP (first edition).

Seeing stuff in the logs like:



sandboxd[9950]: ([9949]) mdworker(9949) deny mach-lookup com.apple.ls.boxd
mdworker[9960]: Unable to talk to lsboxd
kernel[0]: Sandbox: sandboxd(9985) deny mach-lookup com.apple.coresymbolicationd


Then when the screen saver tried to kick in:



9/26/12 4:49:48.236 PM WindowServer[83]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
9/26/12 4:49:48.237 PM loginwindow[57]: find_shared_window: WID -1
9/26/12 4:49:48.237 PM loginwindow[57]: CGSGetWindowTags: Invalid window 0xffffffff
9/26/12 4:49:48.237 PM loginwindow[57]: find_shared_window: WID -1
9/26/12 4:49:48.237 PM loginwindow[57]: CGSSetWindowTags: Invalid window 0xffffffff
9/26/12 4:49:48.241 PM coreservicesd[28]: Application App:"loginwindow" [ 0x0/0x1001] @ 0x0x7f8cd3d05860 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x6b66b6:) ), so denying.
9/26/12 4:49:48.241 PM WindowServer[83]: [cps/setfront] Failed setting the front application to loginwindow, psn 0x0-0x1001, securitySessionID=0x186a5, err=-13066
9/26/12 4:49:48.973 PM WindowServer[83]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x042803c0 device: 0x10e7e7320 isBackBuffered: 1 numComp: 3 numDisp: 3
9/26/12 4:49:49.000 PM kernel[0]: NVDA(OpenGL): Channel exception! exception type = 0xd = GR: SW Notify Error
9/26/12 4:49:49.000 PM kernel[0]: IOVendorGLContext::ReportGPURestart


And then the screensaver froze (just the background image came on) and the pointer turned into the spinning beach ball and there was nothing I could do but hard power-down.

I submitted a support request to AppleCare, they said it was "probably a corrupt screen saver plist" and had me delete it. Yeah, right.

Anyway, since then I've noticed spotlight is almost always re-indexing.

This all started immediately after updating to OS 10.8.2:

MyMac.local installd[25879]: PackageKit: packages=(
"PKLeopardPackage <file://localhost/Library/Updates/041-7512/OSXUpd10.8.2Patch.pkg>",
"PKLeopardPackage <file://localhost/Library/Updates/041-7512/RemoteDesktop.pkg>",
"PKLeopardPackage <file://localhost/Library/Updates/zzzz041-6901/MobileDevice.pkg>",
"PKLeopardPackage <file://localhost/Library/Updates/zzzz041-6901/iTunesX.pkg>",
"PKLeopardPackage <file://localhost/Library/Updates/zzzz041-6901/CoreFP.pkg>",
"PKLeopardPackage <file://localhost/Library/Updates/zzzz041-6901/iTunesAccess.pkg>",
"PKLeopardPackage <file://localhost/Library/Updates/zzzz041-6901/iTunesLibrary.pkg>"
)


I'll try removing


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

and see if that helps.

Shazaam!
Sep 28, 2012, 07:33 PM
I removed Cocktail 6 from 10.8.2 and ran DiskWarrior.
No More mdworker: Unable to talk to lsboxd.

MacInMotion
Sep 28, 2012, 08:23 PM
I'll try removing


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

and see if that helps.

Nope, that didn't help.

Shazaam!
Sep 28, 2012, 09:23 PM
Mak sure you use Cocktail's uninstaller.

kbmb
Sep 29, 2012, 06:33 AM
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

canhaz
Sep 29, 2012, 10:18 AM
I've been having massively annoying issues like these on ML.


10 minutes to login after typing my password
Black screen after wake (requires hard reset)
Plugging thunderbolt display freezes everything (requires hard reset)
lsboxd messages


FWIW I run FV enabled.

petsounds
Sep 29, 2012, 01:07 PM
If I filter system.log by 'lsboxd', I get the "unable to talk..." message basically every 2-4 minutes. Clearing caches, safe boot, none of that has worked. If anyone is on the OS X beta program, they might want to bring up the issue there to see if any engineers have input on this. Does anyone know what the lsboxd utility is responsible for?

ernani
Sep 29, 2012, 01:36 PM
Hi everyone,

I too have had most the problems mentioned in this forum, right after upgrading to ML 10.8.2, with the most prominent being the blank screen after wake, which occurred quite regularly. This made me start examining the Console log, where I found all those messages regarding lsboxd and coresymbolicationd.

I managed to make those messages disappear for about 5-6 days after performing a safe boot, as suggested here. Unfortunately, they did come back, but the system doesn't seem to be affected.

As for the "blank screen after wake" problem, I *may* have found a solution via the Hackintosh community. By a more thorough examination of the console log, you will notice that your mac wakes up more or less on a schedule to perform various "maintenance" chores, even if power nap is disabled or not supported, or simply because of power fluctuations or usb devices being (dis)connected. When this happens, it enters a "dark wake" state. The screen remains blank, the OS does what it is supposed to do, and then attempts to sleep again. All the affected systems remain in this "dark wake" state, not being able to either sleep or perform a regular wake.

What I did is to disable dark wakes all together, by editing /Library/Preferences/SystemConfiguration/com.apple.Boot.plist and entering the following kernel flag:


<key>Kernel Flags</key>
<string>darkwake=0</string>


Since then (almost a week), I found that my macbook did wake up a couple of times by its own, but it was a normal wake (the screen was on), so that I could easily put it back to sleep again, avoiding the hard reset.

Now my macbook never goes to sleep on its own (for instance when it is sleeping and I disconnect my iphone when it completes its charging cycle), which is somewhat inconvenient, but I don't have to do hard resets all the time.

If you guys try it, please let me know if it helps.

murphychris
Sep 29, 2012, 02:28 PM
re: Unable to talk to lsboxd

I'm seeing this on an index rebuild, on 10.7.5. And the estimate for the rebuild is 6 days for a paltry amount of data. So something is fakaked with Spotlight (yet again) :mad: I find spotlight beyond irritating. 6 days for a f'n index rebuild is insane.

MarshallVillage
Oct 1, 2012, 12:07 PM
Kevin

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

Mac

-:apple:iMac-:apple:iPad-:apple:iPhone


Experienced issues after upgrading to OS X 10.8.2 and Mail.app 6.1...Safe Boot fixed my Mail.app extreme slowness...THANKS whiskymac!

Checking the Console.app I see one notable difference. The following item is now gone. [TIMESTAMP] mdworker[17194]: Unable to talk to lsboxd

wprowe
Oct 1, 2012, 12:21 PM
This appears to be related.

http://apple.stackexchange.com/questions/65486/how-to-fix-slow-spotlight-and-time-machine-since-10-7-5/65667#65667

The Spotlight mdworker config files appears to be missing some entries. It does not eliminate the "Unable to talk to lsboxd" messages, but it does eliminate the ones associated with com.apple.ls.boxd.

I think Apple hasn't completely worked out all of the kinks with sandboxing and their own services getting the access they need (like Spotlight).

kbmb
Oct 2, 2012, 09:28 AM
Just to update.....after the safe boot, things were fine for about a week....now my console is littered with the Unable to talk to lsboxd messages.

I also notice that the /Library/Caches/com.apple.coresymbolicationd folder is back.

Guessing we have to wait for 10.8.3 to have Apple fix this mess.

-Kevin

murphychris
Oct 2, 2012, 12:33 PM
Yesterday, I posted a variation on the response below in the Apple Discussion Forums, where you can also read other user reports about this problem, and how well this "fix" I've come up with is working for others.
https://discussions.apple.com/thread/4322106?tstart=0

------

I might have a working "fix". Based on the constant stalling on sandbox-cache.db I decided to take a chance and delete all folders found in /var/folders. What I actually did, in order:

Quit all applications except Terminal, issued the following two commands:
sudo mdutil -i off /
sudo mdutil -E /
sudo rm -Rf /var/folders/*

Reboot.

sudo mdutil -i on /

There were no further stalls on sandbox-cache.db according to opensnoop, and no further lsboxd complaints in Console. mds and mdworker processes have been very busy, typically 40-100% CPU, unlike before. And now the index estimate is variably saying 6 to 19 minutes for completion instead of 3 days to 5 weeks. It ultimately completed indexing in 45 minutes, which is normal for my system. Previously it had been running for 3 days and was maybe 20% complete.

Now, blowing away the folders in /var/folders may have other consequences, possibly negative, for sandboxing. But the files therein appear to be recreated from scratch after reboot to no ill effect or complaints in Console. But let's just say, the suffering bleeding edgers may end up bleeding more by trying this. Any volunteers?

ubergeek72
Oct 3, 2012, 12:15 PM
Yesterday, I posted a variation on the response below in the Apple Discussion Forums, where you can also read other user reports about this problem, and how well this "fix" I've come up with is working for others.
https://discussions.apple.com/thread/4322106?tstart=0

------

I might have a working "fix". Based on the constant stalling on sandbox-cache.db I decided to take a chance and delete all folders found in /var/folders. What I actually did, in order:

Quit all applications except Terminal, issued the following two commands:
sudo mdutil -i off /
sudo mdutil -E /
sudo rm -Rf /var/folders/*

Reboot.

sudo mdutil -i on /

There were no further stalls on sandbox-cache.db according to opensnoop, and no further lsboxd complaints in Console. mds and mdworker processes have been very busy, typically 40-100% CPU, unlike before. And now the index estimate is variably saying 6 to 19 minutes for completion instead of 3 days to 5 weeks. It ultimately completed indexing in 45 minutes, which is normal for my system. Previously it had been running for 3 days and was maybe 20% complete.

Now, blowing away the folders in /var/folders may have other consequences, possibly negative, for sandboxing. But the files therein appear to be recreated from scratch after reboot to no ill effect or complaints in Console. But let's just say, the suffering bleeding edgers may end up bleeding more by trying this. Any volunteers?

Seems to have worked for me. Disk is now very busy and Spotlight says it can have the job done in 47 minutes.

gwang73
Oct 3, 2012, 06:45 PM
Just to update.....after the safe boot, things were fine for about a week....now my console is littered with the Unable to talk to lsboxd messages.

I also notice that the /Library/Caches/com.apple.coresymbolicationd folder is back.

Guessing we have to wait for 10.8.3 to have Apple fix this mess.

-Kevin

My system is the same as yours. I deleted the /Library/Caches/com.apple.coresymbolicationd folder again and restarted in safe-mode and it's temporarily fixed again. I may try modding the mdworker files as suggested in another post but I'm bit a hesitant modding system files at the moment.

murphychris
Oct 3, 2012, 11:14 PM
My system is the same as yours. I deleted the /Library/Caches/com.apple.coresymbolicationd folder again and restarted in safe-mode and it's temporarily fixed again. I may try modding the mdworker files as suggested in another post but I'm bit a hesitant modding system files at the moment.

#47 causes hidden cache files to be removed. They appear to be recreated upon restart. There are no modifications of files, just removal. So far there have been no negative consequences.

50548
Oct 4, 2012, 04:17 PM
Can anyone confirm if the supplemental update has fixed this?

mrapplegate
Oct 4, 2012, 04:26 PM
Can anyone confirm if the supplemental update has fixed this?

Nope, it is not fixed on my system.

razmarino
Oct 4, 2012, 04:27 PM
Can anyone confirm if the supplemental update has fixed this?
nope, it doesn't...:apple:

kbmb
Oct 4, 2012, 04:28 PM
Still getting the messages here after the update.

-Kevin

petsounds
Oct 4, 2012, 07:43 PM
Well, has anyone actually filed a bug on this?

gwang73
Oct 4, 2012, 08:33 PM
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.

----------

Well, has anyone actually filed a bug on this?

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

clayj
Oct 5, 2012, 05:05 PM
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
Oct 6, 2012, 10:22 AM
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
Oct 6, 2012, 11:18 AM
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

:apple:iMac:apple:iPad:apple:iPhone

phobox
Oct 6, 2012, 11:27 PM
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
Oct 7, 2012, 01:57 AM
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
Oct 7, 2012, 05:05 AM
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
Oct 7, 2012, 07:15 PM
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
Oct 8, 2012, 03:53 AM
But do you have your spotlight re-indexing indexed drives all the time?

phobox
Oct 8, 2012, 04:43 AM
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
Oct 9, 2012, 03:13 AM
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
Oct 10, 2012, 04:27 PM
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
Oct 11, 2012, 08:49 AM
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 :)


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
Oct 11, 2012, 11:01 AM
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
Oct 11, 2012, 11:54 AM
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. :mad: I am getting ready to start telling people NOT to buy Macs. I've never had this sort of problem with Windows.

clayj
Oct 11, 2012, 02:51 PM
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
Oct 12, 2012, 06:04 AM
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
Oct 12, 2012, 06:55 PM
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
Oct 15, 2012, 05:48 PM
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?

50548
Oct 16, 2012, 12:02 PM
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.

kbmb
Oct 16, 2012, 12:12 PM
Stupid question: how does one DISABLE the screen saver? I couldn't find any such option.

System Prefs -> Desktop & Screen Saver -> Screen Saver tab -> Start after set to Never.

-Kevin

clayj
Oct 16, 2012, 03:52 PM
Stupid question: how does one DISABLE the screen saver? I couldn't find any such option.Set the "Start after:" time on it to Never.

PS: I'm now 5+ days with no freezes or crashes since disabling my screen saver.

TwitchCity
Oct 18, 2012, 11:27 AM
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.

Thank you for this. I made this change and hopefully it will resolve some of my sandbox issues.

I am also seeing lots of these messages:

sandboxd: ([10305]) com.apple.qtkits deny file-write-create /Users/USERNAME/Library/Frameworks/TempEWSFile
and
sandboxd: ([10305]) com.apple.qtkits deny file-write-create /Library/Frameworks/TempEWSFile

Further, I have a ton of file-read-data deny issues when attempting to read some directories on my computer that contain video files. For instance:

sandboxd: ([7390]) com.apple.qtkits(7390) deny file-read-data /Users/USERNAME/Movies/New Movies/

Could I add a line to a sandbox file (maybe com.apple.qtkitserver.sb?) to stop these? I believe this sandbox issue might stem from the application I am using to stream media files from our iMac to our PS3 - Yazsort's Playback Media Server. I made a report on their forums - here (http://yazsoft.com/f/viewtopic.php?f=24&t=2189) - but the developer doesn't seem to have much of an idea about how to troubleshoot this issue.

Advice would be *really* appreciated!

murphychris
Oct 18, 2012, 02:45 PM
This is a crud hack, I don't recommend making modifications to sandboxd's policies.

If there's something an application won't let you do that you think you need to do, then you need to talk to the developer. Either they're not doing something correctly, or you're doing something unexpected.

clayj
Oct 18, 2012, 09:40 PM
Set the "Start after:" time on it to Never.

PS: I'm now 5+ days with no freezes or crashes since disabling my screen saver.Well, it finally did freeze yesterday. I've re-enabled my screen saver and have disconnected a USB drive that was plugged in to the machine -- monitoring to see what happens.

murphychris
Oct 18, 2012, 09:53 PM
Do you realize that this is totally off topic for this thread?

clayj
Oct 18, 2012, 10:12 PM
Do you realize that this is totally off topic for this thread?No, because I too was experiencing the lsboxd errors and there was speculation that they were causing machine freezes, of which I have had many. I've been trying to figure out what processes might be involved in the freezes so that people can possibly have a workaround for the issue until Apple fixes it.

phobox
Oct 21, 2012, 11:52 AM
Thank you for this. I made this change and hopefully it will resolve some of my sandbox issues.

I am also seeing lots of these messages:

sandboxd: ([10305]) com.apple.qtkits deny file-write-create /Users/USERNAME/Library/Frameworks/TempEWSFile
and
sandboxd: ([10305]) com.apple.qtkits deny file-write-create /Library/Frameworks/TempEWSFile

Further, I have a ton of file-read-data deny issues when attempting to read some directories on my computer that contain video files. For instance:

sandboxd: ([7390]) com.apple.qtkits(7390) deny file-read-data /Users/USERNAME/Movies/New Movies/

Could I add a line to a sandbox file (maybe com.apple.qtkitserver.sb?) to stop these? I believe this sandbox issue might stem from the application I am using to stream media files from our iMac to our PS3 - Yazsort's Playback Media Server. I made a report on their forums - here (http://yazsoft.com/f/viewtopic.php?f=24&t=2189) - but the developer doesn't seem to have much of an idea about how to troubleshoot this issue.

Advice would be *really* appreciated!


From doing some of my own research on how qtkit works, the files its referencing are temp files. I wouldnt worry too much about these errors unless you suspect they are killing performance or causing other issues, which they shouldnt be. The only reason I made the changes for mdworker was to troubleshoot Spotlight issues that many were experiencing.

dkgee
Oct 22, 2012, 07:44 PM
I applied Phobox's fix (Msg#60) to my MacBookPro and iMac. Now Console does not report the "Unable to talk to lsboxd" as often (maybe every two or three hours) but I get a regular line in Console on both machines that says:
lsboxd: @AE relay 61657674:72617070
or
lsboxd: @AE relay 4755524c:4755524c


Any idea what this is trying to tell me - and is it of any concern?

filippaulsen
Oct 24, 2012, 08:32 AM
I have some problems with RAM on my new rMBP, using only Safari, Mail and iTunes the 8 GB RAM is completely filled very quickly. It seems like Mail, iTunes, Safari web content and kernel task are using the most.

Anyway this morning I noticed that I had an unusually large amount free and I checked the logs, mostly for fun, to see if it could be explained. I noticed the same messages as described in this thread every 2 minutes.

Do you think that whatever is related to these messages is responsible for draining my RAM?

i.e. Did anyone of you experience RAM problems related to this sandboxing things?

50548
Oct 24, 2012, 11:49 AM
I have some problems with RAM on my new rMBP, using only Safari, Mail and iTunes the 8 GB RAM is completely filled very quickly. It seems like Mail, iTunes, Safari web content and kernel task are using the most.

Anyway this morning I noticed that I had an unusually large amount free and I checked the logs, mostly for fun, to see if it could be explained. I noticed the same messages as described in this thread every 2 minutes.

Do you think that whatever is related to these messages is responsible for draining my RAM?

i.e. Did anyone of you experience RAM problems related to this sandboxing things?

Actually yes - it happened ONCE that, upon turning my Mac on, I could see that the WHOLE RAM was being used (when this was never the case before, of course).

In any case, I got a reply today from Apple Developer (after having filed it as a bug), where they say my bug report was deemed as a duplicate, since there is already another bug report on the same issue.

I am absolutely sure this will be dealt with when 10.8.3 is released...let's just be patient for now.

filippaulsen
Oct 25, 2012, 12:30 PM
I am absolutely sure this will be dealt with when 10.8.3 is released...let's just be patient for now.

Oh, good. I sure hope this will be the case. I don't run heavy applications that often, but I worry about how it will perform the few times I do if the ram is completely eaten while surfing. Its an rMBP for good sake! I paid a lot for it, and there is no possibility to upgrade the memory...

apmu
Dec 7, 2012, 12:30 PM
Oh, good. I sure hope this will be the case. I don't run heavy applications that often, but I worry about how it will perform the few times I do if the ram is completely eaten while surfing. Its an rMBP for good sake! I paid a lot for it, and there is no possibility to upgrade the memory...

I hate to burst your bubble, but I have the latest 10.8.3 beta that Apple is pimping and I am still seeing these errors.

12/6/12 4:39:51.767 PM sandboxd[12457]: ([12456]) mdworker(12456) deny mach-lookup com.apple.ls.boxd

My company has an enterprise support contract with Apple and I'm escalating this issue via that channel.

Andrew

nyolc8
Dec 8, 2012, 07:51 AM
I'm running 10.8.2 on my standard PC (hackintosh), and I'm not getting these errors... funny... But I got similar errors with Lion if I remember correctly.

50548
Dec 9, 2012, 08:38 AM
I hate to burst your bubble, but I have the latest 10.8.3 beta that Apple is pimping and I am still seeing these errors.

12/6/12 4:39:51.767 PM sandboxd[12457]: ([12456]) mdworker(12456) deny mach-lookup com.apple.ls.boxd

My company has an enterprise support contract with Apple and I'm escalating this issue via that channel.

Andrew

That's absolutely freaking RIDICULOUS if they don't fix those issues - I reported them a while ago and they were marked as "duplicated", meaning that many others had already reported such a problem.

Another MAJOR problem is the loss of Ethernet connection after waking from sleep - only the ifconfig terminal command restores it afterwards.

I must say again: 10.8.2 is probably the WORST 10.x.x release ever from Apple...what a train wreck.

meme1255
Dec 9, 2012, 08:53 AM
I'll be really :mad::mad::mad: if they don't fix this and waking from sleep & wake over LAN in 10.8.3

wrldwzrd89
Dec 9, 2012, 11:53 AM
I'm having this same issue. Not sure what's causing it. I'm a developer so I find myself looking at logs an awful lot.

meme1255
Dec 9, 2012, 02:14 PM
I'm looking in logs too - But I can't figure out what's the problem :(

For example:

08.12.12 2:45:28,000 kernel[0]: Wake reason: RTC (Alarm) - And dark wake, shutdown -h over didn't work too ( I hadn't tried sudo halt) - I had to shutdown Mac by power button in morning &*fans were at 6000 RPM :/

No planned wake ups on that time (am) so probably dropped connection ( I tried it if it hadnt started working that night - it didn't :mad: )

wrldwzrd89
Dec 9, 2012, 03:19 PM
I'm looking in logs too - But I can't figure out what's the problem :(

For example:

08.12.12 2:45:28,000 kernel[0]: Wake reason: RTC (Alarm) - And dark wake, shutdown -h over didn't work too ( I hadn't tried sudo halt) - I had to shutdown Mac by power button in morning &*fans were at 6000 RPM :/

No planned wake ups on that time (am) so probably dropped connection ( I tried it if it hadnt started working that night - it didn't :mad: )
The lsboxd problem is surely caused by conflicts between defined sandbox rules and programs installed with OS X, given the nature of the log message. However, the exact cause is much harder for us to pin down, not having or knowing the source code.

JeffDM
Dec 10, 2012, 07:25 PM
My seeming "hang" on some apps cleared up within a few seconds of turning off "Wake for network access" in Energy Saver System Preferences. Hopefully I won't have the problem again, but we'll see.

edit: I think it was just a coincidence. I'm getting tired of this *****.

jfBLOOM22
Dec 12, 2012, 09:22 AM
I get these 5 console errors about every 3 minutes:


12/12/12 9:08:00.000 AM kernel[0]: Sandbox: sandboxd(5873) deny mach-lookup com.apple.coresymbolicationd
12/12/12 9:08:00.173 AM sandboxd[5873]: ([5872]) mdworker(5872) deny mach-lookup com.apple.ls.boxd
12/12/12 9:08:00.183 AM sandboxd[5873]: ([5871]) mdworker(5871) deny mach-lookup com.apple.ls.boxd
12/12/12 9:08:23.518 AM mdworker[5876]: Unable to talk to lsboxd
12/12/12 9:08:23.631 AM sandboxd[5877]: ([5876]) mdworker(5876) deny mach-lookup com.apple.ls.boxd (pre-ls-info fstype:hfs fsflag:4809000 flags:240000005E diag:0 uti:com.apple.property-list plugin:internalPlainTextImporter - find suspect file using: sudo mdutil -t 575679)


Not really noticeable issues. I am able to wake from sleep over LAN.

masteroflondon
Dec 12, 2012, 01:00 PM
I have one additional symptom no-one else here seems to mention. Time Machine (to a Time Capsule over ethernet, wifi is off) is running very slowly.

I had the problems of black screen when trying to wake from sleep, only a force shutdown with the power button would get it back, although, once only, connecting a MacBook Air over the Cinema Display cable woke it as an external monitor and unplugging took it back to a normal, working display where the iMac was fine.

I took the machine in for the 1TB Seagate HD replacement and upon it's return I did not restore backups. I just set up fresh. Everything ran fine until the first failure to wake finally occurred, since when, I think, the Time Machine has again been slow. Sometimes 20 minutes, sometimes a couple of hours for a few hundred MB's.

I now find the lsboxd messages and the others you've all been talking about.

Anyone else notice the Time Machine issue?

50548
Dec 12, 2012, 02:06 PM
I have one additional symptom no-one else here seems to mention. Time Machine (to a Time Capsule over ethernet, wifi is off) is running very slowly.

I had the problems of black screen when trying to wake from sleep, only a force shutdown with the power button would get it back, although, once only, connecting a MacBook Air over the Cinema Display cable woke it as an external monitor and unplugging took it back to a normal, working display where the iMac was fine.

I took the machine in for the 1TB Seagate HD replacement and upon it's return I did not restore backups. I just set up fresh. Everything ran fine until the first failure to wake finally occurred, since when, I think, the Time Machine has again been slow. Sometimes 20 minutes, sometimes a couple of hours for a few hundred MB's.

I now find the lsboxd messages and the others you've all been talking about.

Anyone else notice the Time Machine issue?

Nope, but mdworker Console messages are ALL over the place - as well as the odd Ethernet disconnection upon waking from sleep...10.8.2 is DEFINITELY the worst 10.x.x update EVER from Apple.

JeffDM
Dec 12, 2012, 03:22 PM
When I get software hangups, particularly with programs that have networked files open, I can get them going by restarting the network connection. I don't use ifconfig, I just switched between two different network files and back and that does the job.

I think I'll just shut down the computer at night for the time being.

mjrozner
Dec 23, 2012, 01:22 PM
Same mdworker errors in console but new symptom where MacPro WILL NOT SHUTDOWN. If select computer computer sleep 15 minutes every 15 minutes the computer will attempt to sleep, attempt a shutdown and just restart stopping at the logon screen. Leaving it alone at the logon screen results in the computer attempting a sleep cycle, attempting another shutdown and restarting again after 10 seconds returning to the logon screen. This problem started with 10.8.2 update. Hours with Apple Support has not solved this. I swapped memory, reset PRAM, Reset Power Management, used different power source (wall outlet vs APC UPS) to no avail. Apple engineers think I may have logic board or power supply failure causing fail to shutdown problem, but I believe it is 10.8.2 related. We've cleared all caches and I installed a clean Mtn Lion 10.8.2 on an empty hard drive with NO additional Applications or software of any kind installed. Same console errors and failure to shutdown!

thegattaca
Dec 30, 2012, 02:29 PM
Yes, I have the same errors showing in logs too. They seem to eventually eat up all 16GB of Ram on my late 2009 12" iMac... tried all hardware tests, tried changing ram, etc... this issue has been happening throughout all of 2012, even before upgrading to Mountain Lion. Have performed several fresh re-installs with out a time machine restore while being very conservative with what is installed. Still, the problems persist. Woke up this morning to find the computer was off, again. It seems to happen about every 24 hours. Not using any funky software... maybe its Microsoft Office? :P Oh, and after the lastest clean re-install, it went for about 2 weeks with no reboots, and then a few days ago it started again. Thinking I might drag this iMac to the apple store tomorrow and tell them to fix the problem.

Here is the "full report" from the sandboxd log...


mdworker(498) deny mach-lookup com.apple.ls.boxd

Process: mdworker [498]
Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Versions/A/Support/mdworker
Load Address: 0x102e6e000
Identifier: mdworker
Version: ??? (???)
Code Type: x86_64 (Native)
Parent Process: launchd [234]

Date/Time: 2012-12-30 14:18:08.057 -0600
OS Version: Mac OS X 10.8.2 (12C60)
Report Version: 8

Thread 0:
0 libsystem_kernel.dylib 0x00007fff86bef686 mach_msg_trap + 10
1 CoreFoundation 0x00007fff8baba803 __CFRunLoopServiceMachPort + 195
2 CoreFoundation 0x00007fff8babfee6 __CFRunLoopRun + 1078
3 CoreFoundation 0x00007fff8babf6b2 CFRunLoopRunSpecific + 290
4 CoreFoundation 0x00007fff8bace371 CFRunLoopRun + 97
5 mdworker 0x0000000102e76ba9
6 libdyld.dylib 0x00007fff899fc7e1 start + 0

Thread 1:
0 libsystem_kernel.dylib 0x00007fff86bf1d16 kevent + 10
1 libdispatch.dylib 0x00007fff8af439ee _dispatch_mgr_thread + 54

Thread 2:
0 libsystem_kernel.dylib 0x00007fff86bef686 mach_msg_trap + 10
1 liblaunch.dylib 0x00007fff8ef497c4
2 liblaunch.dylib 0x00007fff8ef484d9 bootstrap_look_up3 + 69
3 libxpc.dylib 0x00007fff863b1c21 _xpc_connection_bootstrap_look_up_slow + 371
4 libxpc.dylib 0x00007fff863b0c82 _xpc_connection_init + 1062
5 libdispatch.dylib 0x00007fff8af410b6 _dispatch_client_callout + 8
6 libdispatch.dylib 0x00007fff8af4247f _dispatch_queue_drain + 235
7 libdispatch.dylib 0x00007fff8af422f1 _dispatch_queue_invoke + 52
8 libdispatch.dylib 0x00007fff8af42448 _dispatch_queue_drain + 180
9 libdispatch.dylib 0x00007fff8af422f1 _dispatch_queue_invoke + 52
10 libdispatch.dylib 0x00007fff8af421c3 _dispatch_worker_thread2 + 249
11 libsystem_c.dylib 0x00007fff92242cab _pthread_wqthread + 404
12 libsystem_c.dylib 0x00007fff9222d171 start_wqthread + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fff86bf16d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff92242cb3 _pthread_wqthread + 412
2 libsystem_c.dylib 0x00007fff9222d171 start_wqthread + 13

Thread 4:
0 libsystem_kernel.dylib 0x00007fff86bef6c2 semaphore_wait_trap + 10
1 libxpc.dylib 0x00007fff863b3e1f xpc_connection_send_message_with_reply_sync + 127
2 LaunchServices 0x00007fff85ad33ce send(LSBoxMessage&, LSBoxMessage&) + 28
3 LaunchServices 0x00007fff85b53d4b lsbox_preflightAppLaunch + 84
4 LaunchServices 0x00007fff85ade341 _LSFindOrRegisterBundleNode + 857
5 LaunchServices 0x00007fff85b3ab02 _LSRegisterNode + 75
6 LaunchServices 0x00007fff85ae6a0f _LSBundleCopyOrCheckNode + 1047
7 LaunchServices 0x00007fff85ace5b6 _LSCopyLibraryItemURLs + 486
8 mdworker 0x0000000102e9e014
9 libdispatch.dylib 0x00007fff8af44f01 _dispatch_call_block_and_release + 15
10 libdispatch.dylib 0x00007fff8af410b6 _dispatch_client_callout + 8
11 libdispatch.dylib 0x00007fff8af4247f _dispatch_queue_drain + 235
12 libdispatch.dylib 0x00007fff8af422f1 _dispatch_queue_invoke + 52
13 libdispatch.dylib 0x00007fff8af421c3 _dispatch_worker_thread2 + 249
14 libsystem_c.dylib 0x00007fff92242cab _pthread_wqthread + 404
15 libsystem_c.dylib 0x00007fff9222d171 start_wqthread + 13

Thread 5:
0 libsystem_kernel.dylib 0x00007fff86bf16d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff92242cb3 _pthread_wqthread + 412
2 libsystem_c.dylib 0x00007fff9222d171 start_wqthread + 13

Binary Images:
0x102e6e000 - 0x102ec7ff7 mdworker (707.3) <105316D8-F5DF-3079-96EF-0EF0986EB053> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Versions/A/Support/mdworker
0x7fff85aca000 - 0x7fff85b7bfff com.apple.LaunchServices (539.7 - 539.7) <DA7C602E-5E01-31B8-925D-B45360CA089F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x7fff863a8000 - 0x7fff863caff7 libxpc.dylib (140.41) <FAC04D8B-680E-325F-8F0C-DD69859D0E01> /usr/lib/system/libxpc.dylib
0x7fff86bdf000 - 0x7fff86bfaff7 libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
0x7fff899fa000 - 0x7fff899fdff7 libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
0x7fff8af3f000 - 0x7fff8af54ff7 libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
0x7fff8ba8b000 - 0x7fff8bc74fff com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff8ef46000 - 0x7fff8ef4efff liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
0x7fff9222c000 - 0x7fff922f8fe7 libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib

wrldwzrd89
Dec 30, 2012, 06:05 PM
Tried the safe boot fix. 1 hour later, Mac's still spinning at the boot screen with the little progress bar. What's going on? :confused:

EDIT: 3 hours elapsed. Still nothing. Forcibly rebooted. Problem's still there. Oh well.

50548
Dec 30, 2012, 11:22 PM
Can anyone tell us if 10.8.3 FINALLY fixes those two issues (sandbox and Ethernet disconnects upon wake)?

teskor
Jan 1, 2013, 05:15 AM
Kevin

I had the same problem - Safe Boot is your friend. ;)
Mac
-:apple:iMac-:apple:iPad-:apple:iPhone

Thanks, this helped me a lot, because I always got audio dropouts during
these messages, too. Both gone after safe boot (for now).

srgz
Jan 18, 2013, 01:25 PM
Any updates on this?
I'm about to call apple tech support and open a case -- this is pissing me off.

bigcat
Jan 18, 2013, 02:07 PM
I formatted the drive and clean installed the OS about a month ago and haven't seen the problem again. I haven't installed yet all the applications I had before formatting. So it was either OS corruption or one of the applications I was using. I continue to monitor the log as I install new stuff.

50548
Jan 18, 2013, 04:26 PM
To the incredulous, this are the mdworker/sandboxing errors on my Console just in the last 20 min - HAS 10.8.3 FIXED THIS??? And NO, I do NOT want to clean install to fix the problem!


18/01/13 23:02:34,749 mdworker[24833]: Unable to talk to lsboxd
18/01/13 23:02:34,754 mdworker[24832]: Unable to talk to lsboxd
18/01/13 23:02:34,759 mdworker[24830]: Unable to talk to lsboxd
18/01/13 23:02:34,771 mdworker[24831]: Unable to talk to lsboxd
18/01/13 23:02:34,805 sandboxd[24836]: ([24833]) mdworker(24833) deny mach-lookup com.apple.ls.boxd
18/01/13 23:02:34,810 sandboxd[24836]: ([24832]) mdworker(24832) deny mach-lookup com.apple.ls.boxd
18/01/13 23:02:34,814 sandboxd[24836]: ([24830]) mdworker(24830) deny mach-lookup com.apple.ls.boxd
18/01/13 23:02:34,819 sandboxd[24836]: ([24831]) mdworker(24831) deny mach-lookup com.apple.ls.boxd
18/01/13 23:03:02,270 sandboxd[24842]: ([320]) tccd(320) deny mach-lookup com.apple.ls.boxd
18/01/13 23:05:02,917 mdworker[24850]: Unable to talk to lsboxd
18/01/13 23:05:02,921 mdworker[24852]: Unable to talk to lsboxd
18/01/13 23:05:02,942 mdworker[24851]: Unable to talk to lsboxd
18/01/13 23:05:02,967 mdworker[24849]: Unable to talk to lsboxd
18/01/13 23:05:02,976 sandboxd[24855]: ([24850]) mdworker(24850) deny mach-lookup com.apple.ls.boxd
18/01/13 23:05:02,980 sandboxd[24855]: ([24852]) mdworker(24852) deny mach-lookup com.apple.ls.boxd
18/01/13 23:05:02,983 sandboxd[24855]: ([24851]) mdworker(24851) deny mach-lookup com.apple.ls.boxd
18/01/13 23:05:02,986 sandboxd[24855]: ([24849]) mdworker(24849) deny mach-lookup com.apple.ls.boxd
18/01/13 23:07:03,644 mdworker[24872]: Unable to talk to lsboxd
18/01/13 23:07:03,647 mdworker[24871]: Unable to talk to lsboxd
18/01/13 23:07:03,665 mdworker[24869]: Unable to talk to lsboxd
18/01/13 23:07:03,696 mdworker[24870]: Unable to talk to lsboxd
18/01/13 23:07:03,699 sandboxd[24875]: ([24872]) mdworker(24872) deny mach-lookup com.apple.ls.boxd
18/01/13 23:07:03,702 sandboxd[24875]: ([24871]) mdworker(24871) deny mach-lookup com.apple.ls.boxd
18/01/13 23:07:03,707 sandboxd[24875]: ([24869]) mdworker(24869) deny mach-lookup com.apple.ls.boxd
18/01/13 23:07:03,711 sandboxd[24875]: ([24870]) mdworker(24870) deny mach-lookup com.apple.ls.boxd
18/01/13 23:11:50,554 mdworker[24905]: Unable to talk to lsboxd
18/01/13 23:11:50,559 mdworker[24903]: Unable to talk to lsboxd
18/01/13 23:11:50,564 mdworker[24904]: Unable to talk to lsboxd
18/01/13 23:11:50,580 mdworker[24902]: Unable to talk to lsboxd
18/01/13 23:11:50,613 sandboxd[24908]: ([24905]) mdworker(24905) deny mach-lookup com.apple.ls.boxd
18/01/13 23:11:50,617 sandboxd[24908]: ([24903]) mdworker(24903) deny mach-lookup com.apple.ls.boxd
18/01/13 23:11:50,621 sandboxd[24908]: ([24904]) mdworker(24904) deny mach-lookup com.apple.ls.boxd
18/01/13 23:11:50,625 sandboxd[24908]: ([24902]) mdworker(24902) deny mach-lookup com.apple.ls.boxd
18/01/13 23:18:01,771 mdworker[24946]: Unable to talk to lsboxd
18/01/13 23:18:01,775 mdworker[24948]: Unable to talk to lsboxd
18/01/13 23:18:01,780 mdworker[24945]: Unable to talk to lsboxd
18/01/13 23:18:01,785 mdworker[24947]: Unable to talk to lsboxd
18/01/13 23:18:01,826 sandboxd[24951]: ([24946]) mdworker(24946) deny mach-lookup com.apple.ls.boxd
18/01/13 23:18:01,830 sandboxd[24951]: ([24948]) mdworker(24948) deny mach-lookup com.apple.ls.boxd
18/01/13 23:18:01,833 sandboxd[24951]: ([24945]) mdworker(24945) deny mach-lookup com.apple.ls.boxd
18/01/13 23:18:01,838 sandboxd[24951]: ([24947]) mdworker(24947) deny mach-lookup com.apple.ls.boxd
18/01/13 23:23:30,418 mdworker[24976]: Unable to talk to lsboxd
18/01/13 23:23:30,422 mdworker[24977]: Unable to talk to lsboxd
18/01/13 23:23:30,431 mdworker[24974]: Unable to talk to lsboxd
18/01/13 23:23:30,439 mdworker[24975]: Unable to talk to lsboxd
18/01/13 23:23:30,472 sandboxd[24980]: ([24976]) mdworker(24976) deny mach-lookup com.apple.ls.boxd
18/01/13 23:23:30,477 sandboxd[24980]: ([24977]) mdworker(24977) deny mach-lookup com.apple.ls.boxd
18/01/13 23:23:30,482 sandboxd[24980]: ([24974]) mdworker(24974) deny mach-lookup com.apple.ls.boxd
18/01/13 23:23:30,485 sandboxd[24980]: ([24975]) mdworker(24975) deny mach-lookup com.apple.ls.boxd

Krazy Bill
Jan 18, 2013, 11:43 PM
Last 30 minutes of mine. It's been like this since 10.8.0.

1/18/13 11:06:26.769 PM mdworker[3521]: Unable to talk to lsboxd
1/18/13 11:06:26.882 PM sandboxd[3522]: ([3521]) mdworker(3521) deny mach-lookup com.apple.ls.boxd
1/18/13 11:06:27.000 PM kernel[0]: Sandbox: sandboxd(3522) deny mach-lookup com.apple.coresymbolicationd
1/18/13 11:10:27.701 PM mdworker[3537]: Unable to talk to lsboxd
1/18/13 11:10:27.803 PM sandboxd[3538]: ([3537]) mdworker(3537) deny mach-lookup com.apple.ls.boxd
1/18/13 11:10:28.000 PM kernel[0]: Sandbox: sandboxd(3538) deny mach-lookup com.apple.coresymbolicationd
1/18/13 11:12:28.957 PM mdworker[3542]: Unable to talk to lsboxd
1/18/13 11:12:29.108 PM sandboxd[3543]: ([3542]) mdworker(3542) deny mach-lookup com.apple.ls.boxd
1/18/13 11:12:29.000 PM kernel[0]: Sandbox: sandboxd(3543) deny mach-lookup com.apple.coresymbolicationd
1/18/13 11:16:29.938 PM mdworker[3555]: Unable to talk to lsboxd
1/18/13 11:16:30.052 PM sandboxd[3556]: ([3555]) mdworker(3555) deny mach-lookup com.apple.ls.boxd
1/18/13 11:16:30.000 PM kernel[0]: Sandbox: sandboxd(3556) deny mach-lookup com.apple.coresymbolicationd
1/18/13 11:19:30.722 PM com.apple.usbmuxd[44]: _handle_timer heartbeat detected detach for device 0x2d-192.168.0.6:0!
1/18/13 11:20:30.889 PM mdworker[3570]: Unable to talk to lsboxd
1/18/13 11:20:30.995 PM sandboxd[3571]: ([3570]) mdworker(3570) deny mach-lookup com.apple.ls.boxd
1/18/13 11:20:31.000 PM kernel[0]: Sandbox: sandboxd(3571) deny mach-lookup com.apple.coresymbolicationd
1/18/13 11:22:29.916 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44d8
1/18/13 11:22:29.916 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44d7
1/18/13 11:22:29.916 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44d6
1/18/13 11:22:29.916 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44d5
1/18/13 11:22:29.918 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44d4
1/18/13 11:22:29.918 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44d3
1/18/13 11:22:29.918 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44d2
1/18/13 11:22:29.918 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44d1
1/18/13 11:22:29.918 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44d0
1/18/13 11:22:29.919 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44cf
1/18/13 11:22:29.919 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44ce
1/18/13 11:22:29.919 PM Dock[266]: CGSGetWindowTags: Invalid window 0x44cd
1/18/13 11:22:31.840 PM mdworker[3581]: Unable to talk to lsboxd
1/18/13 11:22:31.960 PM sandboxd[3582]: ([3581]) mdworker(3581) deny mach-lookup com.apple.ls.boxd
1/18/13 11:22:32.000 PM kernel[0]: Sandbox: sandboxd(3582) deny mach-lookup com.apple.coresymbolicationd
1/18/13 11:26:33.483 PM mdworker[3595]: Unable to talk to lsboxd
1/18/13 11:26:33.000 PM kernel[0]: Sandbox: sandboxd(3596) deny mach-lookup com.apple.coresymbolicationd
1/18/13 11:26:34.036 PM sandboxd[3596]: ([3595]) mdworker(3595) deny mach-lookup com.apple.ls.boxd
1/18/13 11:28:35.407 PM Dock[266]: CGSGetWindowTags: Invalid window 0x455f
1/18/13 11:28:35.407 PM Dock[266]: CGSGetWindowTags: Invalid window 0x455e
1/18/13 11:28:35.407 PM Dock[266]: CGSGetWindowTags: Invalid window 0x455d
1/18/13 11:28:35.407 PM Dock[266]: CGSGetWindowTags: Invalid window 0x455c
1/18/13 11:28:35.407 PM Dock[266]: CGSGetWindowTags: Invalid window 0x455b
1/18/13 11:28:35.408 PM Dock[266]: CGSGetWindowTags: Invalid window 0x455a
1/18/13 11:28:35.408 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4559
1/18/13 11:28:35.408 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4558
1/18/13 11:28:35.408 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4557
1/18/13 11:28:35.408 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4556
1/18/13 11:28:35.408 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4555
1/18/13 11:28:35.409 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4554
1/18/13 11:30:04.500 PM Mail[311]: *** Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1499/Message/EWS/EWSConnection.m:472
Received an unknown SOAPWebServices error: Error Domain=SOAPWebServicesErrorDomain Code=-1 "The operation couldn’t be completed. (SOAPWebServicesErrorDomain error -1.)" UserInfo=0x7fc2933578a0 {SOAPErrorHTTPStatusKey=400}
(
0 CoreMessage 0x00007fff8b2f58d7 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 141
1 CoreMessage 0x00007fff8b2f5748 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 215
2 Message 0x00007fff8ec3a76e -[EWSConnection sendMessage:forRequest:] + 762
3 Message 0x00007fff8ec43793 -[EWSGateway sendMessage:forRequest:] + 69
4 Message 0x00007fff8ec5a11a -[EWSRequestOperation executeOperation] + 110
5 CoreMessage 0x00007fff8b310f10 -[MonitoredOperation main] + 219
6 Foundation 0x00007fff8cb6b986 -[__NSOperationInternal start] + 684
7 Foundation 0x00007fff8cb731a1 __block_global_6 + 129
8 libdispatch.dylib 0x00007fff8963ff01 _dispatch_call_block_and_release + 15
9 libdispatch.dylib 0x00007fff8963c0b6 _dispatch_client_callout + 8
10 libdispatch.dylib 0x00007fff8963d1fa _dispatch_worker_thread2 + 304
11 libsystem_c.dylib 0x00007fff8c858cab _pthread_wqthread + 404
12 libsystem_c.dylib 0x00007fff8c843171 start_wqthread + 13
)
1/18/13 11:30:04.503 PM Mail[311]: *** Assertion failure in -[EWSGateway fetchCopyOfSyncIssuesEntryID], /SourceCache/Message/Message-1499/Message/EWS/EWSGateway.m:1853
Didn't get a proper response for a GetFolder request on Inbox
(
0 CoreMessage 0x00007fff8b2f58d7 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 141
1 CoreMessage 0x00007fff8b2f5748 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 215
2 Message 0x00007fff8ec4e0d8 -[EWSGateway fetchCopyOfSyncIssuesEntryID] + 425
3 Message 0x00007fff8ec3327b -[EWSAccount _synchronizeMailboxListWithUserInput:] + 585
4 Message 0x00007fff8ec3283f -[EWSAccount synchronizeAllMailboxes] + 76
5 Message 0x00007fff8ec326fd -[EWSAccount fetchSynchronouslyIsAuto:] + 496
6 CoreFoundation 0x00007fff8686c63c __invoking___ + 140
7 CoreFoundation 0x00007fff8686c4d7 -[NSInvocation invoke] + 263
8 CoreMessage 0x00007fff8b310b67 -[MonitoredInvocation invoke] + 225
9 CoreMessage 0x00007fff8b3290c2 -[ThrowingInvocationOperation main] + 33
10 CoreMessage 0x00007fff8b2d5342 -[_MFInvocationOperation main] + 431
11 Foundation 0x00007fff8cb6b986 -[__NSOperationInternal start] + 684
12 Foundation 0x00007fff8cb731a1 __block_global_6 + 129
13 libdispatch.dylib 0x00007fff8963ff01 _dispatch_call_block_and_release + 15
14 libdispatch.dylib 0x00007fff8963c0b6 _dispatch_client_callout + 8
15 libdispatch.dylib 0x00007fff8963d1fa _dispatch_worker_thread2 + 304
16 libsystem_c.dylib 0x00007fff8c858cab _pthread_wqthread + 404
17 libsystem_c.dylib 0x00007fff8c843171 start_wqthread + 13
)
1/18/13 11:30:34.889 PM mdworker[3609]: Unable to talk to lsboxd
1/18/13 11:30:34.000 PM kernel[0]: Sandbox: sandboxd(3610) deny mach-lookup com.apple.coresymbolicationd
1/18/13 11:30:34.988 PM sandboxd[3610]: ([3609]) mdworker(3609) deny mach-lookup com.apple.ls.boxd
1/18/13 11:30:54.448 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45df
1/18/13 11:30:54.449 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45de
1/18/13 11:30:54.449 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45dd
1/18/13 11:30:54.449 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45dc
1/18/13 11:30:54.449 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45db
1/18/13 11:30:54.450 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45da
1/18/13 11:30:54.450 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45d9
1/18/13 11:30:54.450 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45d8
1/18/13 11:30:54.450 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45d7
1/18/13 11:30:54.450 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45d6
1/18/13 11:30:54.451 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45d5
1/18/13 11:30:54.451 PM Dock[266]: CGSGetWindowTags: Invalid window 0x45d4
1/18/13 11:32:36.176 PM mdworker[3620]: Unable to talk to lsboxd
1/18/13 11:32:36.301 PM sandboxd[3621]: ([3620]) mdworker(3620) deny mach-lookup com.apple.ls.boxd
1/18/13 11:32:36.000 PM kernel[0]: Sandbox: sandboxd(3621) deny mach-lookup com.apple.coresymbolicationd
1/18/13 11:35:06.308 PM Dock[266]: CGSGetWindowTags: Invalid window 0x466c
1/18/13 11:35:06.309 PM Dock[266]: CGSGetWindowTags: Invalid window 0x466b
1/18/13 11:35:06.309 PM Dock[266]: CGSGetWindowTags: Invalid window 0x466a
1/18/13 11:35:06.309 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4669
1/18/13 11:35:06.310 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4668
1/18/13 11:35:06.310 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4667
1/18/13 11:35:06.310 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4666
1/18/13 11:35:06.310 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4665
1/18/13 11:35:06.310 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4664
1/18/13 11:35:06.310 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4663
1/18/13 11:35:06.310 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4662
1/18/13 11:36:37.878 PM mdworker[3631]: Unable to talk to lsboxd
1/18/13 11:36:38.000 PM kernel[0]: Sandbox: sandboxd(3632) deny mach-lookup com.apple.coresymbolicationd
1/18/13 11:36:38.321 PM sandboxd[3632]: ([3631]) mdworker(3631) deny mach-lookup com.apple.ls.boxd
1/18/13 11:37:55.632 PM Dock[266]: CGSGetWindowTags: Invalid window 0x470a
1/18/13 11:37:55.633 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4709
1/18/13 11:37:55.633 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4708
1/18/13 11:37:55.634 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4707
1/18/13 11:37:55.634 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4706
1/18/13 11:37:55.634 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4705
1/18/13 11:37:55.634 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4704
1/18/13 11:37:55.634 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4703
1/18/13 11:37:55.635 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4702
1/18/13 11:37:55.635 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4701
1/18/13 11:37:55.635 PM Dock[266]: CGSGetWindowTags: Invalid window 0x4700
1/18/13 11:39:55.697 PM Console[3654]: Persistent UI failed to open file file://localhost/Users/Library/Saved%20Application%20State/com.apple.Console.savedState/window_1.data: No such file or directory (2)

oreocracker
Jan 30, 2013, 11:34 AM
I'm having the same log issues, only my cpu spontaneously shuts down and reboots just as fast. Thank goodness I'm used to saving my work every few secs or it would have been a disaster. Dislike this new OS and gateway very much. It's getting more PCish.

50548
Jan 30, 2013, 03:39 PM
Any hints on whether 10.8.3 FINALLY fixes this? Thanks a lot.

BlaqkAudio
Jan 30, 2013, 04:41 PM
Any hints on whether 10.8.3 FINALLY fixes this? Thanks a lot.
That's a negative. I'm led to believe the updating process somehow causes the issue. I performed a clean install (10.8.2) after having a repair done about a month ago. This solved the issue up until I updated to 10.8.3; back to constant mdworker messages.

----------

Hmm, just found this as a potential fix: http://blog.aitrus.com/2013/01/04/osx-unable-to-talk-to-lsboxd-and-other-console-errors/
Somewhere along the way, Mountain Lion started getting oodles of these errors in the console log… usually every 4 minutes or so. It’s been common enough that there are posts about it on quite a few sites. Surprisingly, the fix really is a simple as a safe boot. Apparently safe boot cleans out some cache files which were causing a problem.

I'm trying it out right now.

EDIT: Seems to have worked. No more messages so far.

dpetree
Feb 4, 2013, 01:48 PM
I can add my name to this list and say its still here on 10.8.3 (12D61)

Was searching for a fix and ran across this thread

bigcat
Feb 4, 2013, 03:18 PM
I installed MS Mac Office 2011 yesterday and the problem is now back for me.

I formatted the drive and clean installed the OS about a month ago and haven't seen the problem again. I haven't installed yet all the applications I had before formatting. So it was either OS corruption or one of the applications I was using. I continue to monitor the log as I install new stuff.

50548
Feb 4, 2013, 03:23 PM
I can add my name to this list and say its still here on 10.8.3 (12D61)

Was searching for a fix and ran across this thread

That's just amazing, really - what are those Apple engineers doing the whole day? This issue has been reported a gazillion times by users like me - Apple Bug Report even stopped accepting it as it is already marked as duplicate.

Bring back Serlet and Tevanian, please - the lack of focus on OS X nowadays is just pathetic.

And no, I don't want to hear about how Macs are "unimportant" to Apple's revenues - they are the ONLY device segment that can really go up as far as Apple's market share is concerned.

Will try the safe boot tip above and see if it works - not that I am expecting any miracles, of course.

legomanx51v
Feb 10, 2013, 12:17 PM
What IS "coresymbolicationd"???

I've tried searching all over and can't figure out what its supposed to do. I mean I understand that sandboxd is the sandbox process and mdworker is for spotlight, but what does coresymbolicationd DO?

Im wary of deleting the /library/caches/com.apple.coresymbolicationd folder before i know what its there for.
Anyone?

Mac32
Feb 10, 2013, 12:51 PM
I get mdworker hanging at 100% if I use Britannica Ultimate 2012 (which is coded in java), so I stopped using it... :confused: Only way to stop the process is to boot OSX in safe mode, which gets annoying after a while.. As far as these error messages, I also get them with my late 2012 iMac.

lotlorien
Feb 10, 2013, 01:14 PM
Hi All,

My logs are full with

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

PM sandboxd[5444]: ([5442]) mdworker(5442) deny mach-lookup com.apple.ls.boxd

However, all seems to work just fine, including spotlight.

I'm on a MBP Retina, bought in December 2012, with several fresh installs of 10.8.2 because I was playing around a lot before going productive. I had these messages ever since I remember on my Mac, so I never cared to much.

What I would also like to know: Is Apple still committed to OS X?

Best wishes,

lotlorien

50548
Feb 10, 2013, 02:41 PM
Hi All,

My logs are full with

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

PM sandboxd[5444]: ([5442]) mdworker(5442) deny mach-lookup com.apple.ls.boxd

However, all seems to work just fine, including spotlight.

I'm on a MBP Retina, bought in December 2012, with several fresh installs of 10.8.2 because I was playing around a lot before going productive. I had these messages ever since I remember on my Mac, so I never cared to much.

What I would also like to know: Is Apple still committed to OS X?

Best wishes,

lotlorien

Try doing a Safe Boot (rebooting with Shift pressed), and then rebooting normally again.

At least on my Console for now, the main sender(s) stopped being the ones linked to the sandboxing and coresymbolication messages above.

lotlorien
Feb 10, 2013, 04:36 PM
Try doing a Safe Boot (rebooting with Shift pressed), and then rebooting normally again.

At least on my Console for now, the main sender(s) stopped being the ones linked to the sandboxing and coresymbolication messages above.

How do I boot into Safe Mode with full disk encryption switched on? How do I check whether or not I'm in Safe Mode?

Thanks and best wishes,

lotlorien

50548
Feb 11, 2013, 03:20 AM
How do I boot into Safe Mode with full disk encryption switched on? How do I check whether or not I'm in Safe Mode?

Thanks and best wishes,

lotlorien

This should do the trick:

http://support.apple.com/kb/TS4235

ObeseSquirrel
Feb 11, 2013, 11:12 AM
Booting into Safe Mode will solve it for a few days, but after awhile it starts again.

lotlorien
Feb 11, 2013, 01:49 PM
Booting into Safe Mode will solve it for a few days, but after awhile it starts again.

Ok, I'm not going to do it. First, I don't want to decrypt all my data, and second it's just a temporary fix, so what's the point?

On top of that, apart from the messages in the console, what are the problems? On my Mac everything seems to work anyway.

Best wishes,

Urs

50548
Feb 11, 2013, 02:40 PM
Booting into Safe Mode will solve it for a few days, but after awhile it starts again.

It hasn't for me - it's been fine for at least a week now.

legomanx51v
Feb 13, 2013, 02:08 PM
What IS "coresymbolicationd"???

...

Im wary of deleting the /library/caches/com.apple.coresymbolicationd folder before i know what its there for

Nobody knows what this is??

poooooof
Feb 19, 2013, 04:58 AM
This might be totally unrelated to those report here, but I found the error Unable to talk to lsboxd generated every time I try to access the server using a Android 4.1 L2TP client. Of course the Login will fail after that, since it never gets to the VPN server.

darkgoob
Feb 26, 2013, 03:28 PM
This appears to be related.

http://apple.stackexchange.com/questions/65486/how-to-fix-slow-spotlight-and-time-machine-since-10-7-5/65667#65667

The Spotlight mdworker config files appears to be missing some entries. It does not eliminate the "Unable to talk to lsboxd" messages, but it does eliminate the ones associated with com.apple.ls.boxd.

I think Apple hasn't completely worked out all of the kinks with sandboxing and their own services getting the access they need (like Spotlight).

I told them NOT to do sandboxing in a bug report. Sandboxing is the stupidest, worst idea ever. It's purposeless. It's like forcing people to have safe sex. Look. When did personal responsibility go out the window? Let us have freedom. Overzealous security measures always backfire.

murphychris
Feb 26, 2013, 03:50 PM
Sandboxing is the stupidest, worst idea ever. It's purposeless.

It's neither purposeless nor stupid. It is a very aggressive, broad, and blunt means of dealing with malware that has essentially no user adjustable settings.

Let us have freedom. Overzealous security measures always backfire.

Umm, I think you're confused about the nature of Apple and the platform. If you want freedom, you need to go with OpenIndiana, FreeBSD or a Linux distribution. OS X is significantly restricted for user choice. iOS is totally restricted.

orionrush
Mar 9, 2013, 11:07 AM
So Im boord and am waiting until one of the solutions I found here finishes reindexing the drive. While I waited I did some more digging, and now know it wont help because I've just seem post #48. :mad:

So for the benefit of all us poor saps watching our older macs get crushed under the load of the runaway spotlight process, I've put together this synopsis. And here is what we've learned in this thread so far:

Possible solution 1:
#48 (http://forums.macrumors.com/showpost.php?p=15952376&postcount=48) Terminal solution which erases Spotlight cashses and forces a reindex

-- and it dosent work
<despair>

Possible solution 2:
#60 (http://forums.macrumors.com/showpost.php?p=15981689&postcount=60) calls for editing system.sb wich does reduces sandboxing issues ie:
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 seen in #62 (http://forums.macrumors.com/showpost.php?p=15982798&postcount=62)

Its unclear if this solves the continuous reindexing issue however. (anyone?)

Temporary solution 3:
Reboot the computer periodically in "Safe Boot Mode (http://support.apple.com/kb/ht1455)"
(hold down the shift key just after the chime)
cue twilight zone music (http://blog.aitrus.com/2013/01/04/osx-unable-to-talk-to-lsboxd-and-other-console-errors/)
This works but the problem seems to resurface for some after an unknown period of time (week).

Possible Solution 4:
Remove plugins in:
~/Library/Spotlight/
/Library/Spotlight/
Not from this forum (dont know where I read it) but it might work for some. I removed the bootcamp plugin as I dont have a bootcamp partition any longer - but it didn't help me. See also 6

Solution 5:
Disable Spotlight all together by adding the root drive to the "Privacy" list:
System Prefs > Spotlight > Privacy

-- Obvious disadvantages here - but hey no problems!

Possible Solution 6:
Add Dropbox/Google Drive/Boot Camp partition/ To the above mentioned privacy list. (Can't find where thats mentioned . . .)

-- Didn't work for me though it might help some

Possible solution 7:
delete: /System/Library/LaunchAgents/com.apple.afpstat.plist
#18 (http://forums.macrumors.com/showpost.php?p=15854740&postcount=18) -- Well that seems to really be about another problem (https://discussions.apple.com/thread/4213550?start=0&tstart=0) entirely.

Possible solution 8:
Reinstall ML -- Not going to try to track that one down - that's crazy talk! :eek:

Possible solution 9:
Shut off screen savers http://forums.macrumors.com/showpost.php?p=16048287&postcount=74 (74)
-- Also dosent seem to be related :rolleyes: ?

Possible solution 10:
Wait for ML 10.8.3 - or UHFO (http://acronyms.thefreedictionary.com/UHFO) 74 (http://forums.macrumors.com/showpost.php?p=16048287&postcount=74)

-- I for one cant wait on that :cool:chance :cool:

Possible solution 11:
Possible corrupt file in User Account. Not sure where I read that one, may not have been on this thread. See also 6 & 8

</despair>
<apathy>
Possible solution 12: Guinness method.

- Power Down Machine (hold down power switch and mutter swear words)
- Go have a Guinness, possibly three or more just to be sure.
- Go back to work

Solution 12 seems to midigate the urgency of the problem significantly. Source: We've been making alcohol from :apple:s about as long as we could walk its ancient wisdom! :)

Cheers!
</apathy >

50548
Mar 9, 2013, 11:44 AM
So Im boord and am waiting until one of the solutions I found here finishes reindexing the drive. While I waited I did some more digging, and now know it wont help because I've just seem post #48. :mad:

So for the benefit of all us poor saps watching our older macs get crushed under the load of the runaway spotlight process, I've put together this synopsis. And here is what we've learned in this thread so far:

Possible solution 1:
#48 (http://forums.macrumors.com/showpost.php?p=15952376&postcount=48) Terminal solution which erases Spotlight cashses and forces a reindex

-- and it dosent work
<despair>

Possible solution 2:
#60 (http://forums.macrumors.com/showpost.php?p=15981689&postcount=60) calls for editing system.sb wich does reduces sandboxing issues ie:
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 seen in #62 (http://forums.macrumors.com/showpost.php?p=15982798&postcount=62)

Its unclear if this solves the continuous reindexing issue however. (anyone?)

Temporary solution 3:
Reboot the computer periodically in "Safe Boot Mode (http://support.apple.com/kb/ht1455)"
(hold down the shift key just after the chime)
cue twilight zone music (http://blog.aitrus.com/2013/01/04/osx-unable-to-talk-to-lsboxd-and-other-console-errors/)
This works but the problem seems to resurface for some after an unknown period of time (week).

Possible Solution 4:
Remove plugins in:
~/Library/Spotlight/
/Library/Spotlight/
Not from this forum (dont know where I read it) but it might work for some. I removed the bootcamp plugin as I dont have a bootcamp partition any longer - but it didn't help me. See also 6

Solution 5:
Disable Spotlight all together by adding the root drive to the "Privacy" list:
System Prefs > Spotlight > Privacy

-- Obvious disadvantages here - but hey no problems!

Possible Solution 6:
Add Dropbox/Google Drive/Boot Camp partition/ To the above mentioned privacy list. (Can't find where thats mentioned . . .)

-- Didn't work for me though it might help some

Possible solution 7:
delete: /System/Library/LaunchAgents/com.apple.afpstat.plist
#18 (http://forums.macrumors.com/showpost.php?p=15854740&postcount=18) -- Well that seems to really be about another problem (https://discussions.apple.com/thread/4213550?start=0&tstart=0) entirely.

Possible solution 8:
Reinstall ML -- Not going to try to track that one down - that's crazy talk! :eek:

Possible solution 9:
Shut off screen savers http://forums.macrumors.com/showpost.php?p=16048287&postcount=74 (74)
-- Also dosent seem to be related :rolleyes: ?

Possible solution 10:
Wait for ML 10.8.3 - or UHFO (http://acronyms.thefreedictionary.com/UHFO) 74 (http://forums.macrumors.com/showpost.php?p=16048287&postcount=74)

-- I for one cant wait on that :cool:chance :cool:

Possible solution 11:
Possible corrupt file in User Account. Not sure where I read that one, may not have been on this thread. See also 6 & 8

</despair>
<apathy>
Possible solution 12: Guinness method.

- Power Down Machine (hold down power switch and mutter swear words)
- Go have a Guinness, possibly three or more just to be sure.
- Go back to work

Solution 12 seems to midigate the urgency of the problem significantly. Source: We've been making alcohol from :apple:s about as long as we could walk its ancient wisdom! :)

Cheers!
</apathy >

Well, I would just add "Possible solution 13":

Apple wakes up and fixes the problem once and for all in 10.8.3.

MacInMotion
Mar 9, 2013, 11:19 PM
Well, I would just add "Possible solution 13":

Apple wakes up and fixes the problem once and for all in 10.8.3.

Actually, that was solution #10

50548
Mar 10, 2013, 06:04 AM
Actually, that was solution #10

Oh right :D

BlaqkAudio
Mar 11, 2013, 06:28 AM
Possible solution 10:
Wait for ML 10.8.3 - or UHFO (http://acronyms.thefreedictionary.com/UHFO) 74 (http://forums.macrumors.com/showpost.php?p=16048287&postcount=74)

-- I for one cant wait on that :cool:chance :cool:
Not fixed in 10.8.3. In fact, I fixed the problem with a safe boot, but then it comes back every time I install a new beta. My guess is that the update process messes with sandboxing, since clean installing to 10.8.2 resulted in no mdworker messages.

tblrsa
Mar 12, 2013, 03:20 AM
This is outrageous. I have reinstalled ML Core Files with a fresh copy from the App Store (without erasing user data) and the problem of Spotlight constant reindexing bogging down my Macs performance still persists. Before reinstalling ML Ive even experienced some Kernel Panics. No System is perfect, but come on: There is something seriously messed up here, Apple.

Applied Solution #7 right now which seems to have prompted Spotlight to do a full reindex. Also disabled "Wake Up on Network Access" and created a new user account. I will let the System do its thing and if it does not work I will try the "Safe Boot" fix next.

Apple needs to address this, it really made me and I bet a lot of other users dislike OSX. Gosh, Ive never had this issues with Snow Leopard. Im not one who rants easily, but this is really p*ssing me off.

Thanks for all the help given in this thread, folks.

Update:

Some of the fixes Ive tried have rendered my machine to be unable to boot. :( Glad I was able to roll back the last TM Backup.

MacInMotion
Mar 13, 2013, 04:29 PM
How many people on this thread are using Evernote?

I bought a new computer and it was working fine (OS X 10.8.2) until I installed Evernote. After I installed it I started seeing the lsboxd errors. Then I deleted Evernote and the errors went away. Then I installed it again and they came back.

Details:

Installed Evernote 5.0.6 by downloading from Evernote site.
Immediately installed update to 5.0.7 via in-app update.
Deleted Evernote by dragging application to trash and emptying trash.
Installed Evernote 5.0.7 by downloading from Evernote site.


Based on other stuff I've read I think these errors are from third-party spotlight importers (https://developer.apple.com/library/mac/#documentation/Carbon/Conceptual/MDImporters/MDImporters.html) so it may be that just removing those importers will solve the problem (although it will keep the custom documents out of Spotlight).

wrldwzrd89
Mar 13, 2013, 06:33 PM
How many people on this thread are using Evernote?

I bought a new computer and it was working fine (OS X 10.8.2) until I installed Evernote. After I installed it I started seeing the lsboxd errors. Then I deleted Evernote and the errors went away. Then I installed it again and they came back.

Details:

Installed Evernote 5.0.6 by downloading from Evernote site.
Immediately installed update to 5.0.7 via in-app update.
Deleted Evernote by dragging application to trash and emptying trash.
Installed Evernote 5.0.7 by downloading from Evernote site.


Based on other stuff I've read I think these errors are from third-party spotlight importers (https://developer.apple.com/library/mac/#documentation/Carbon/Conceptual/MDImporters/MDImporters.html) so it may be that just removing those importers will solve the problem (although it will keep the custom documents out of Spotlight).
I'm using an application that has a 3rd-party Spotlight importer. Thanks for the info!

50548
Mar 14, 2013, 01:20 PM
How many people on this thread are using Evernote?

I bought a new computer and it was working fine (OS X 10.8.2) until I installed Evernote. After I installed it I started seeing the lsboxd errors. Then I deleted Evernote and the errors went away. Then I installed it again and they came back.

Details:

Installed Evernote 5.0.6 by downloading from Evernote site.
Immediately installed update to 5.0.7 via in-app update.
Deleted Evernote by dragging application to trash and emptying trash.
Installed Evernote 5.0.7 by downloading from Evernote site.


Based on other stuff I've read I think these errors are from third-party spotlight importers (https://developer.apple.com/library/mac/#documentation/Carbon/Conceptual/MDImporters/MDImporters.html) so it may be that just removing those importers will solve the problem (although it will keep the custom documents out of Spotlight).

Never used Evernote but have always had these issues (with 10.8.2) - will check the spotlight importers, though.

whiskymac
Mar 14, 2013, 04:17 PM
Has the ML 10.8.3 update sorted out the mdworker problems?

I'm away from home at the moment.

Hope the fix is there :D

Mac

:apple:iMac :apple:iPad :apple:iPhone :apple:iPod

50548
Mar 14, 2013, 05:27 PM
Has the ML 10.8.3 update sorted out the mdworker problems?

I'm away from home at the moment.

Hope the fix is there :D

Mac

:apple:iMac :apple:iPad :apple:iPhone :apple:iPod

Nope, mdworker and sandboxd Console messages STILL THERE. Although they do seem to occur less often now.

petsounds
Mar 14, 2013, 11:25 PM
Has the ML 10.8.3 update sorted out the mdworker problems?


Nope. I did the combo update, and they're still spamming my log at the same clip.

Apple obviously doesn't give a **** about making their operating system stable. :mad:

tkermit
Mar 15, 2013, 05:53 AM
Apple obviously doesn't give a **** about making their operating system stable. :mad:

Do the console messages in any way affect the system's stability?

razmarino
Mar 15, 2013, 05:56 AM
Do the console messages in any way affect the system's stability?

no

petsounds
Mar 16, 2013, 03:07 AM
Do the console messages in any way affect the system's stability?

The fact that mdworker is being barred from completing certain tasks due to sandboxing issues is a 'stability' issue, even if it doesn't result in something like a kernel panic.

50548
Mar 16, 2013, 06:36 AM
The fact that mdworker is being barred from completing certain tasks due to sandboxing issues is a 'stability' issue, even if it doesn't result in something like a kernel panic.

Exactly. Not to mention that this issue was widely reported to Apple through its bug report form - and my own report was already flagged as "duplicate" since there were so many people doing the same.

This is the problem when you have two guys working on OS X, as opposed to 2000 on iOS.

tblrsa
Mar 16, 2013, 08:25 AM
Yes, Ive been using Evernote and the mdworker Errors seem to be related with this Application somehow. Have now updated to latest version of Evernote.

OSX 10.8.3 is still giving me

16.03.13 14:23:34,033 mdworker[1381]: Unable to talk to lsboxd

though, even without Evernote running.

I'm using an application that has a 3rd-party Spotlight importer. Thanks for the info!

How does one remove this importers?

wrldwzrd89
Mar 16, 2013, 08:42 AM
<snip>
How does one remove this importers?
Depends on where the importer files live. Normally they'll be inside the application bundle, or in one of the Library folders.

murphychris
Mar 16, 2013, 12:13 PM
Clearly there's a problem, too many people are reporting it. Apple released Lion and Mountain Lion Supplemental updates that fixed this problem for many, but didn't fix it for many others. So duh yes there is a problem, I find it annoying when some people try to apologize for Apple at the expense of the user experience.

I suspect it's a sandboxing related problem, but that doesn't mean it's sandboxing itself that's the problem, largely due to what I found in this thread (https://discussions.apple.com/thread/4322106?start=60&tstart=0). Whether an Apple or 3rd party induced bug, short of actual malware being thwarted, the behavior people are experiencing is a bug and it's not OK.

MacInMotion
Mar 16, 2013, 01:17 PM
Do the console messages in any way affect the system's stability?

Of course the console messages do not affect the system's stability. They're just string written into a text file or database. The cause of the console messages also causes Spotlight indexing to crash, causing Spotlight to eat up CPU and disk I/O while not providing a full index of the disk. Since Time Machine relies on Spotlight for proper functioning, Spotlight's crashes also affect Time Machine's performance.

Since both Spotlight and Time Machine are system agents, I would say that the problems discussed on this thread are a source of system instability. Given the functional problems and resource-wasting problems, it is very disappointing that Apple has let this go on for so long.

bingefeller
Mar 22, 2013, 04:08 PM
I have this entry in my Console logs too. My MBP seems to be running fine, although I've only had it for 4 days now.

I'm also using 10.8.3.

Maybe 10.8.4 will fix it....

TonyK
Mar 23, 2013, 07:10 AM
Don't know why but my spam seems to have stopped. Have not updated to 10.8.3 yet (have it downloaded, just not installed).

How does one find out if there is a 3rd party Spotlight indexer installed?

25ghosts
Apr 14, 2013, 09:48 AM
It's neither purposeless nor stupid. It is a very aggressive, broad, and blunt means of dealing with malware that has essentially no user adjustable settings.
.

OK... Say you are right -- we all get a safe computer... Which is great...

But @ which cost ???

In this case (sandboxing) performance is the cost.. Not so bad for folks using the computer to do emailing and non-high-performance applications. But -- for those who rely on the computer to perform... Like when using NLEs, DAWs etc.. Sandboxing is a killer.

Even Apples own apps pro apps are suffering under sandboxing...


Look -- there is NO such think as 100% secure in word full of code. There just isnt.. If someone is persistent enough, he can reverse-engineer any software..

Remember this : if the computer can read the CODE --- So can a hacker !!!

xianshell
Apr 19, 2013, 03:56 PM
Symptoms:
- extremely slow spotlight indexing and frequent reindexing
- extremely slow Time Machine backups

4.19.13 1:53:57.289 PM mdworker[5305]: Unable to talk to lsboxd
4.19.13 1:53:57.295 PM mdworker[5304]: Unable to talk to lsboxd
4.19.13 1:53:57.302 PM mdworker[5303]: Unable to talk to lsboxd
4.19.13 1:53:58.376 PM sandboxd[5309]: ([5305]) mdworker(5305) deny mach-lookup com.apple.ls.boxd
4.19.13 1:53:59.209 PM sandboxd[5309]: ([5304]) mdworker(5304) deny mach-lookup com.apple.ls.boxd
4.19.13 1:54:00.046 PM sandboxd[5309]: ([5303]) mdworker(5303) deny mach-lookup com.apple.ls.boxd

tigres
May 10, 2013, 08:02 AM
I find this thread.

Wake from sleep (that never happens) battery drain, and a console log plagued with every error in this thread.

3 Genius bar appts, and no effect. Battery dies in 5 days or less (lid closed in my briefcase).

Calling apple again this afternoon.

Edit/Add:
Replaced unit @ local store. Bad SSD- genius actually looked at the console this time.

MagnusVonMagnum
May 28, 2013, 10:51 PM
If I filter system.log by 'lsboxd', I get the "unable to talk..." message basically every 2-4 minutes.

I've been trying to figure out what is causing various games to stutter/pause every couple of minutes and after finding this in my console system log every couple of minutes, I'm suspecting it MIGHT just have something to do with it. The problem with the Safe Mode reboot suggestions is that Safe Mode apparently doesn't work right on machines that have gone to software RAID0 arrays to increase speed (e.g. I RAID0 my two internal hard drives on my Mac Mini and use a bootable external backup instead of recovery partition, but trying to boot to Safe Mode results in a kernel panic. Just lovely. Apple's own software that supports RAID0 results in a broken Safe Mode on top of the known lack of support for a recovery partition.

Even so, it seems like the reboot still did something since the log spamming has stopped for the past hour at least. I still need to see if gaming has improved at all. But like people have been saying, WTF isn't Apple actually fixing reported bugs? They force sandboxing on people and they can't even get their own programs to work right with it...sad. Just sad. It's like depreciating Carbon all those years and yammering on about Cocoa, but not supporting it in their own programs like iTunes for years on end. They have their priorities all screwed up since the iPhone came out and frankly, I think it's been a BAD thing.

Sure iOS and the iPhone/iPad made Steve Jobs rich as hell before he died and made Apple stock sore to an all-time-high beyond anyone's wildest dreams, but that dream has been dropping like a stone for some time now and there is no way they can deliver that level of hype again unless they invent mind control computing or something equally wild. It's unsustainable and has created completely unrealistic expectations for the future. This hurts Apple's long term image and drives them even further off into the iOS oblivion they've created. Some of us still prefer traditional computing BY FAR and this tablet/smart phone craze is all but ruining the traditional computer market which despite all the hype for mobile, still blow the freaking doors off any POS phone or tablet out there. But good luck getting proper support for them. Companies are too busy trying to catch the latest FAD instead of moving forward properly with a stable OS. Apple is so quick to drop support for OLDER STABLE OS versions, but they replace it with UNSTABLE CRAP THEY WON'T FIX. This is unacceptable. The problem is there aren't many other solutions since Microsoft now can't move fast enough to drive Windows into a new Oblivion as well. They took a relatively ugly, but STABLE Windows7 and made the patch-quilt NIGHTMARE that is Windows8. Horrible. Just Horrible looking. There is NO up-to-date STABLE modern Windows operating system out there (don't even mention Linux; it's god-awful and always will be; I've been toying with it for over a decade and it STILL SUCKS for software installation, forcing groups to maintain software archives everywhere for their particular flavor and making things like Steam ONLY work for ONE system...Ubuntu which has sucked to high hell ever since the newest Gnome came out and ruined its own GUI. You get half-baked support for KDE there, but other flavors of Linux don't get supported by this and that company like Steam. It's a mess).

petsounds
May 31, 2013, 03:59 PM
Sure iOS and the iPhone/iPad made Steve Jobs rich as hell before he died and made Apple stock sore to an all-time-high beyond anyone's wildest dreams, but that dream has been dropping like a stone for some time now...

I've tried the Safe Reboot thing and the gremlins always return after a short time.

As for your rant, while I agree with much of it, you'll have a better chance of changing things by sending a more composed e-mail with your thoughts to Tim Cook (tcook@apple), as AFAIK he doesn't browse the MacRumors forum. I sent an e-mail to him suggesting he put Ive in charge of both hardware and software design a few months before he actually did so, and while I doubt my e-mail had a big impact on that decision, I'd like to hope it had some impact.

MagnusVonMagnum
Jun 1, 2013, 03:49 PM
I've tried the Safe Reboot thing and the gremlins always return after a short time.


Actually, since my "failed" Safe Reboot, the lsboxd error has disappeared (I guess Safe Mode doesn't have to successfully fully load in order to do whatever it does to get rid of that error). I still get the "deny mach-lookup com.apple.coresymbolicationd" in the log, but it only happens every few hours, not every 20 seconds to 1 minute like it was doing before.

In any case, it had no impact on pause/stutters in Call of Duty 2. Booting from my external backup USB3 drive instead and playing it off that drive resulted in a big improvement in that regard (still pauses but so short that you'd likely miss it if you weren't specifically looking for it constantly whereas with the RAID0 configuration, the pause is anywhere from 1/8 to 1/2 second and can be very noticeable during the game. Clearly, there's something going on with software RAID that impacts the game (on the plus side, the missions, etc. load over twice as fast). I seem to recall something similar happening during The Force Unleashed, but I don't recall it being as noticeable. I was playing Monkey Island 4 (Escape From Monkey Island) in a virtual WinXP environment and Curse of Monkey Island with ScummVM and they would both also pause for a split second so I'm thinking something pretty nasty is happening in the background to affect games like that. With everyday Internet and server functions, it's unnoticeable and the boot time and other copy operations, etc. are massively faster with RAID0 (2.5x on average) than with the regular single drive operation using the stock 5200 RPM drives (they top out about 100MB/sec whereas with RAID0 they top out at 250MB/sec).

As for e-mailing Tim Cook, I seriously doubt he reads his outside e-mails. They're most likely filtered by a secretary or something first. Otherwise, he'd probably be overwhelmed with every form of begging, pleading, lecturing and insults known to man. Given his personal lack of interest in Macs (he commented he hardly ever uses them anymore in preference to the iPad), I doubt he'd even have a clue what was being said anyway. I'd rather e-mail someone in the OSX development department. Of course, bug reports, etc. are supposed to go there, but I think they get filtered by tech people that don't know squat (kind of like Apple Store "geniuses" that typically give a bad meaning to the word).

petsounds
Jun 5, 2013, 07:29 PM
I've had 10.8.4 running for about eight hours now (installed via combo update), and it appears to have have partially fixed my issues. I no longer am getting sandboxd[296] ([299]): mdworker(299) deny mach-lookup com.apple.ls.boxd and kernel[0]: Sandbox: sandboxd(314) deny mach-lookup com.apple.coresymbolicationd messages.

I've only gotten one mdworker[299]: Unable to talk to lsboxd message during that time.

Krazy Bill
Jun 5, 2013, 10:02 PM
I've only gotten one mdworker[299]: Unable to talk to lsboxd message during that time.Similar results here with 10.8.4. Let's hope the crap has been finally neutered.

MagnusVonMagnum
Jun 6, 2013, 04:20 PM
I've concluded this issue (which has not come back since my "failed" boot into Safe Mode) has nothing to do with stuttering in games, etc. That seems to be a result purely of the hard drive controller driver somehow interrupting things in a very bad way (less pervasive but still present when I boot from an external USB3 drive than my internal RAID 0 SATA setup).

However, using a trick I read about on some Diablo III forum, I bought a USB3 32GB memory stick and now when I want to play a game that has a hard drive related stuttering issue, I just copy the game directory over to the USB3 drive and run it from there (e.g. Call of Duty keeps its save files in my home directory, not in the game install directory so it doesn't interfere at all to just copy it to the USB stick and run from there). It plays 100% smooth as ice from the USB drive with zero stuttering.

So whatever this error is caused by, it appears to be a minor thing here. It wasn't causing any of my stutter issues and I have not seen it return since the boot into Safe Mode that resulted in a kernel panic (seemed to fix it anyway).

tookitogo
Jun 8, 2013, 08:01 AM
For what it's worth, on my 10.8.4, I made the observation that all the
[0]: Sandbox: mdworker(1298) deny file-read-data
messages are for legacy files such as old PPC-only apps or files with resource forks (like old fonts).

That said, Spotlight has no need to search inside obsolete application bundles -- and it can still find them, even after receiving the sandbox deny.

TonyK
Jun 8, 2013, 08:38 AM
Just completed the 10.8.4 combo update and have only 2 recent errors

6/8/13 9:26:42.118 AM mds[41]: Unable to talk to lsboxd
6/8/13 9:28:50.894 AM mdworker[372]: Unable to talk to lsboxd

That is it. Not sure what I did but on earlier inspections my log files were littered with these types of messages.

Hoping this silliness has ended for all of us.

falco
Jun 21, 2013, 10:54 AM
OSX 10.8.4, late 2011 MBP 8GB

Jun 21 17:38:52 macbook-pro mdworker[2350]: Unable to talk to lsboxd
Jun 21 17:40:53 macbook-pro mdworker[2362]: Unable to talk to lsboxd
Jun 21 17:44:54 macbook-pro mdworker[2366]: Unable to talk to lsboxd
Jun 21 17:48:55 macbook-pro mdworker[2378]: Unable to talk to lsboxd

/var/log/system.log is 1.2 GB (!)

From https://discussions.apple.com/thread/4313832?start=45&tstart=0 I tried now this one:

In
/System/Library/Sandbox/Profiles/system.sb

Add 2 lines in bold:

;;; Allow IPC to standard system agents.
(allow mach-lookup
(global-name "com.apple.bsd.dirhelper")
(global-name "com.apple.system.logger")
(global-name "com.apple.system.notification_center")
(global-name "com.apple.system.opendirectoryd.libinfo")
(global-name "com.apple.system.DirectoryService.libinfo_v1")
(global-name "com.apple.system.opendirectoryd.membership")
(local-name "com.apple.ls.boxd")
(global-name "com.apple.ls.boxd")
(global-name "com.apple.xpcd"))


Let's see.