Atsserver and mdworker

Ive had 5 clean installs so far. (whew) However on my c2d 17" mbpro atsserver and mdworker have now been running at ~20-40% cpu for 5 hours. Ive killed them etc etc. I know its usually a font cache problem, But Ive yet to find any font caches in the normal areas. Anyone else having this problem?? Thanks
Codeslave

cbd2 wrote:
I just got smart and checked Software Update and there is are two updates - "Login & Keychain Update" and "Remote Desktop Client" - one of which seems to solve the problem. There is one other update as well, "Backup", but I suspect "Login & Keychain Update" to be the problem solver.
Reply to myself yet again...
No, those updates didn't really 'fix' the problem at all... just delays it somewhat. Having three apps open and doing nothing the processors were again maxing out at 100% usage each. Just now I'm at 100% and 16% and it's Atsserver and mdworker that are hogging the load. Anyone else find a solution yet?

Similar Messages

  • ATSServer and MDWorker High CPU Usage

    Lately, Activity Monitor shows 'ATSServer' and 'MDWorker' as using an unusually high cpu usage. I tried to google the issue and all that I found out is that ATSServer and MDWorker deal with Spotlight indexing.
    Currently, Spotlight isn't indexing my drive. I've tried to force quit both processes. They relaunch and take up the CPU again. I've restarted the machine to no avail.
    Help?

    Thanks for posting! I've been in the same boat for the last few days, with my MacBook's fan howling at me as it indexed a giant zip file. *shakes fist at MacBook designers* It needs TWO fans, you lugnuts!
    Never once did I consider simply adding my downloads drive to the "ignore" list. You've saved my sanity!

  • Libdispatch and MDWorker - errors galore!

    Hello,
    I have had the following errors in Lion installed in a brand new earlly 2011 15 inch MBP. From time to time it seems like my MBP is doing some heavy processing, the fans go wild, it gets hot and I went to look into Activity Monitor and it shows that mdworker (AKA: SpotLight) takes about 22 to 45%+ of the CPU. 
    mdworker: (Error) ImportPluginLoading: Couldn't load plugin '/Library/Spotlight/iWeb.mdimporter/'
    when I go to the "/Library/Spotlight/" the folder "iWeb.mdimporter" is not there but spotlight wants to find it there every 2-5 minutes
    quicklookd: BUG in libdispatch: 11A511 - 1813 - 0x4
    After that I also get the following:
    System Preferences: **** DesktopPref error: DSKiPhotoRootSource -loadData TIME OUT!!! There something wrong with iLife Media Browser
    Does anybody have an idea of what to do?
    thx

    Hi Sonicray,
    I also get the
    mdworker: (Error) IMportPluginLoading: .....
    message a lot in console.
    I have two of them:
    mdworker: (Error) ImportPluginLoading: Couldn't load plugin '/Library/Spotlight/iWeb.mdimporter/'
    and
    mdworker: (Error) ImportPluginLoading: Couldn't load plugin 'Spotlight/Google Earth.mdimporter/ -- /Library/Internet Plug-Ins/Google Earth Web Plug-in.plugin/Contents/MacOS/Google Earth for Plugin.app/Contents/Library/'
    The iWeb.mdimporter plugin in /Library/Spotlight/ is broken in my case.
    It exists, but has 1KB instead of several hundreds, and has no version shown in finder.
    I compared it with the version I have on my old MBP, and it seems the same, even thought it used to have 4KB.
    On my old Mac, it did not give me any console error messages.
    The Google Earth error was not solved by reinstalling Google Earth as a newer version, unfortunately.
    It still remains.
    Even though, when checking, the GE.mdimporter plugin within the GE internet plugin seems to be "OK".
    So, unfortunately, no solution so far.
    Lion brought me a lot of more console messages than Snow Leopard.
    It seems that Apple changed a lot more things not to the eye within Lion that break old compatibilites.
    SyncServer messages I had also a lot, and cleared old items via Syncrospector.
    All the best, did you find a solution?
    Martin

  • MDS and mdworker processes gone wild

    Ever since I upgraded to Lion on my Macbook Pro I am getting intermittant periods where the MDS and MDWORKER processes completely take over the CPU and all apparent activity for minutes at a time. It's now been a week, so I'm quite sure Spotlight is done indexing the drive. What are my options?

    I'm having the same problem you are, and I'm exploring options.
    First I noticed that Backblaze (backup service) was causing the problem, but I fixed that by including the /library/backblaze folder in Spotlight's privacy area. The complete lockup that was causing is now no longer a problem.
    However, I'm noticing that most of the cycles are going to indexing my Time Machine backups, which Spotlight will not allow in the privacy area. It looks like it's indexing many of my old mailbox files from mail.app that are backed up on the Time Machine (Time Capsule) disk. I really don't see the logic to this. I've had the computer on and idling with full access to Time Machine for many days now and this is still going on, with MacBook Pro fans running at full gun and CPU not quite maxing out, but frolicking between 5% and 65% or so on a regular basis with no other apps present. Activity monitor doesn't show anything else hogging cycles -- it's all mds and mdworker.
    Something isn't right with this. I hope that the next update from Apple will fix this, or someone on the intertubes will come up with a quick solution.
    All the above is on a MacBook Pro (late 2008). I do note that I have a MacBook Air (late 2010) that backs up to the same Time Machine but does NOT have Backblaze installed. (I put everything important on the MacBook Pro.) This machine does not seem to have these problems. Both computers are running Lion and have much of the same software. Backups are doing fine on both machines.
    My temporary solution is to turn OFF Time Machine on the MacBook Pro. This does seem to make things much better -- although even at 5% CPU use the fan runs somewhat higher revs than I was used to with Snow Leopard. I then run a manual Time Machine cycle just before I turn in for the night. When I'm back to using the machine again, I make sure the Time Capsule is not mounted. I'm backing up any working files continually to Backblaze still, as well as to Dropbox, so cutting the Time Machine frequency down to once or twice a day is not too bad for now. I do not want this to continue, however.
    Also, I have done the following: Repaired disk permissions, reset the SMC and PRAM, and started the computer up in safe mode fully, and then restarted in regular mode.
    If anyone has any possible fixes, I'm listening and thanks!

  • MDS and MDWORKER processes not running

    Spotlight stopped working about two weeks ago. I noticed that the mds and mdworker processes are not running. Something corrupted maybe???
    Any ideas?

    Spotlight stopped working about two weeks ago. I noticed that the mds and mdworker processes are not running. Something corrupted maybe???
    Any ideas?

  • What are hiutil and mdworker? - they're maxing out the CPU!!

    So I upgraded this afternoon to Lion on my 13" macbook air from the App Store; first of all the reboot crashed, then a hard off and back on sorted that out.
    Now hiutil (and sometimes mdworker) are trashing the CPU constantly at 90-100% (and making the fan go crazy with it)
    Anyone have any idea what these threads are?
    My MBA is now unusable because of these!!
    Cheers, Simmo

    mdworker is the Spotlight indexer. Spotlight is a bit wonky in Lion (as it was in SL 10.6.0)…be patient; it might not be fixed until 10.7.2 or so. If you don't use Spotlight, consider turning it off in SysPrefs. It'll cut that process.
    hiutil seems to be a low-level process for Help pages. It's probably indexing those (to get the snappy search results from the Help menu).
    hiutil(1) Mac OS X Manual Page

  • Spotlight endlessly indexing and mdworker process using lot of cpu

    Hi, I just did Archive&Install from Tiger to Leopard, applied 10.5.1 and now...
    ...since THREE DAYS Spotlight is indexing giving strange values for time remaining (2.134.545.673 hours).
    Like I found in other threads, I have the mdworked process absorbing a lot of cpu power and, from Console, maybe it's crashing repeatedly. I made private of lots of folders but the problem is still there.
    Any other idea?
    How can I find which file/application is freezing mdworker and making Spotlight so unuseful?
    Thanks in advance
    Tampano

    I don't know. How much data is on your HD? Simplest thing to do is use the Terminal command mdutil to erase the current indexes and rebuild them. This should do it:
    *sudo mdutil -E /Volumes/(asterisk)*
    Launch the Terminal.app in /Applications/Utilities/, copy & paste that command into the window, hit the return key, enter your admin password at the Password: prompt (carefully because nothing shows up on the screen), and hit the return key again. That should erase the indexes and rebuild them.

  • Slow time machine, console messages: mdworker: unable to talk to lsboxd, and mdworker 32:kCGErrorFailure:set a breakpoint@CGErrorBreakpoint()

    iMac: model indentifier: iMac11,3
    processor: 3.2GHz intel core i3
    Software: OSX lion 10.7.5
    Current problem: Time machine running extremely slowly as is computer. When time machine is "preparing to update" if I attempt to open any drive, that function freezes the computer. 
    I followed web advice to check for console message:  mdworker: unable to talk to lsboxd.  Found that to be present.  As recommended, I turned off computer, restarted in safe mode, logged in and restarted computer.  checked console, I see this same message and another message that may be problematic: mdworker: 32: kCGErrorFailure: set a breakpoint@CGErrorBreakpoint() to catch srrors as they are logged.
    Both these messages being recorded every few minutes in the console log.
    Any support would be greatly appreciated.
    thank you,

    Hello Mr Davis,
    Thanks for your willingness to help I really appreciate your assistance.
    I decided to watch what was happening a bit more to see if I could discern a pattern to the problem so that I could pose a more refined question.
    This am, after the computer was left on all night, I noticed time machine (TM) was running.  I opened the console window, and noted after entering "starting" in the search field corresponding to "all messages"  that hourly, there is a notation:
    date, time, then "starting standard backu" followed by date, time and starting post backup thinning". 
    However, then there is the entry below at 12:25:46am referring to "starting standard backup" and there is no subsequent entry in the log referring to thinning having occured.  I wonder if this corresponds to TM running now and I am guessing, ever since 12:25:46 am?
    Once again, it seems that the problem is that when TM is running in this fashion, the computer slows down tremendously and operating particular programs such as photo processing lightroom that require more power, become very slow in particular.
    I copied and pasted a section of the log as it seems to repeat the same sequence of information over and over all night long.  I did not copy and paste the entire log since 12:25:46 am, as I wanted to not paste an excessive amount of lines here, but can do that if you like.
    I hope I followed your directions correctly. thanks again, Jeff
    Console log:
    8/2/13 12:25:46.540 AM com.apple.backupd: Starting standard backup
    8/2/13 12:25:46.823 AM com.apple.backupd: Backing up to: /Volumes/LaCie 2 TB Backup for Mac/Backups.backupdb
    8/2/13 12:25:47.938 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11610]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:25:47.938 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11610]) Exited with code: 1
    8/2/13 12:25:47.938 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:27:27.000 AM kernel: IOSCSIPeripheralDeviceType00::setPowerState(0xffffff800b0c8200, 1 -> 4) timed out after 100721 ms
    8/2/13 12:27:28.015 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11620]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:27:28.016 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11620]) Exited with code: 1
    8/2/13 12:27:28.016 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:29:08.092 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11630]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:29:08.093 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11630]) Exited with code: 1
    8/2/13 12:29:08.093 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:29:08.000 AM kernel: IOSCSIPeripheralDeviceType00::setPowerState(0xffffff800b0c8200, 4 -> 3) timed out after 100746 ms
    8/2/13 12:29:19.346 AM applepushserviced: <APSCourier: 0x7fe44b908430>: Stream error occurred for <APSTCPStream: 0x7fe44b810ab0>: The operation couldn’t be completed. Connection reset by peer
    8/2/13 12:30:30.000 AM kernel: add_fsevent: unable to get path for vp 0xffffff8017720930 (system.log; ret 22; type 4)
    8/2/13 12:30:30.000 AM kernel: add_fsevent: unabled to get a path for vp 0xffffff8017720930.  dropping the event.
    8/2/13 12:30:48.171 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11642]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:30:48.171 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11642]) Exited with code: 1
    8/2/13 12:30:48.172 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:31:10.000 AM kernel: IOSCSIPeripheralDeviceType00::setPowerState(0xffffff800b0c8200, 3 -> 2) timed out after 100738 ms
    8/2/13 12:32:28.263 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11652]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:32:28.263 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11652]) Exited with code: 1
    8/2/13 12:32:28.264 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:33:11.000 AM kernel: IOSCSIPeripheralDeviceType00::setPowerState(0xffffff800b0c8200, 2 -> 1) timed out after 100738 ms
    8/2/13 12:34:08.343 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11662]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:34:08.344 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11662]) Exited with code: 1
    8/2/13 12:34:08.344 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:35:48.420 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11672]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:35:48.420 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11672]) Exited with code: 1
    8/2/13 12:35:48.421 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:37:28.498 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11682]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:37:28.498 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11682]) Exited with code: 1
    8/2/13 12:37:28.498 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:39:08.577 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11692]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:39:08.577 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11692]) Exited with code: 1
    8/2/13 12:39:08.577 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:39:19.976 AM applepushserviced: <APSCourier: 0x7fe44b908430>: Stream error occurred for <APSTCPStream: 0x7fe44a444230>: The operation couldn’t be completed. Connection reset by peer
    8/2/13 12:40:48.654 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11702]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:40:48.655 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11702]) Exited with code: 1
    8/2/13 12:40:48.655 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:42:28.731 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11712]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:42:28.731 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11712]) Exited with code: 1
    8/2/13 12:42:28.731 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:42:54.000 AM kernel: CODE SIGNING: cs_invalid_page(0x1000): p=11715[GoogleSoftwareUp] clearing CS_VALID
    8/2/13 12:44:08.810 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11723]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory

  • Mds and mdworker are constantly using 10%-40% of my CPU since partitioning.

    2 days ago I partitioned approximately 80GB of my 500GB 7200rpm macbook pro drive to be used for Windows 7. There was 430GB of free space on my HDD at the time so I know that there was no overwrite issue. It has successfully been installed and runs very well. However, since I did this the mds and mdsworker processes on the Mac side are constantly using large amounts of my CPU and are bogging down my computer. I understand that these services help create the Spotlight database. Is anyone aware of this issue?

    After two days I'd say it's time to start over. Go to the System Preferences application- you can get to it by clicking on the Apple in the upper right corner, System Preferences is about a third of the way down the menu. When it's open, select Spotlight from the list of preferences. Under "Search Results" in Spotlight you will see the order in which results will be displayed. If you want to change the order, now would be a good time.
    Uncheck all the boxes, this will remove them from the consideration of Spotlight. Then re-check the ones you wish to be available in Spotlight, this will force them to be re-indexed. My arithmetic says your files should occupy not much more than 50 GB, this should not take long to index.
    You could try just Applications, or just System Preferences first to see if it is able to complete the task. If it takes longer than a few minutes, there's likely something else going on, perhaps related to your partitioning.
    Good luck! Joel.

  • Mdwrite and mdworker errors etc

    i seem to have a clutch of problems on the macbook pro which includes safari not working and prompt to enter my password when i copy data or rename files.
    does anyone know what these two errors are and if they are part and parcel of any of this?
    i am wiping the drive and doing a re-install but i'd be interested in knowing what these two gremlins are all about.
    thanks.

    adboehm,
    Here are some error codes for you:
    Quote
    Bug Check 0x0A IRQL_NOT_LESS_OR_EQUAL, which is defined as 0x0A, indicates that the driver accessed paged memory at DISPATCH_LEVEL or higher.
    Bug Check 0xBE ATTEMPTED_WRITE_TO_READONLY_MEMORY, which is defined as 0xBE, indicates that the driver tried to write to a read-only memory segment.
    Bug Check 0xC1 SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION, which is defined as 0xC1, indicates that the driver wrote to an invalid section of the special memory pool. Typically, the current thread's backtrace reveals the source of the error.
    Bug Check 0xC4 DRIVER_VERIFIER_DETECTED_VIOLATION, which is defined as 0xC4, is the general bug check code for fatal errors that Driver Verifier finds. The accompanying parameters are the parameters that are passed to KeBugCheckEx and displayed on a blue screen.
    Bug Check 0xC5 DRIVER_CORRUPTED_EXPOOL, which is defined as 0xC5, indicates that the driver tried to access invalid memory at a process IRQL that was too high.
    Bug Check 0xC6 DRIVER_CAUGHT_MODIFYING_FREED_POOL, which is defined as 0xC6, indicates that the driver tried to gain access to a freed memory pool.
    Bug Check 0xC7 TIMER_OR_DPC_INVALID, which is defined as 0xC7, indicates that a kernel timer or DPC was found somewhere in memory where the kernel timer or DPC is not permitted. This condition is usually caused by a driver's not canceling the timer or the Delayed Procedure Call (DPC) before freeing the memory in which the timer or DPC resides.
    Bug Check 0xC9 DRIVER_VERIFIER_IOMANAGER_VIOLATION, which is defined as 0xC9, is the bug check code for all I/O Driver Verifier violations.
    Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA, which is defined as 0x50, is issued if invalid system memory is referenced.
    Take Care,
    Richard

  • Errors with Time Machine (not completing backup, and needing to erase the ".inProgress" package)

    I have in a previous discussion been talking about errors with my Time Machine backup.  The errors were with a problem with Indexing a file, it fails and stops the whole backup.  Each time it attemps another backup, it fills my ".inProgress" package with a (nearly) whole backup, filling my Time Machine hard drive, and thus errasing my previous good backups.  The error occurs after about 95% completion.
    In my last post of a similar disscussion, the problem was indexing the Preference Pane files and this caused the whole backup to fail.  This was my last post there:  (below in some additional info of my situation)
    I did exclude the MobileMe.prefPane.  And I got:
    12/16/11 9:24:50.468 PM com.apple.backupd: Starting standard backup
    12/16/11 9:24:50.556 PM com.apple.backupd: Backing up to: /Volumes/3 TB GoFlex Drive/Backups.backupdb
    12/16/11 9:25:14.418 PM com.apple.backupd: Waiting for index to be ready (101)
    12/16/11 9:27:02.366 PM com.apple.backupd: Deep event scan at path:/ reason:must scan subdirs|
    12/16/11 9:27:02.366 PM com.apple.backupd: Finished scan
    12/16/11 9:33:37.119 PM com.apple.backupd: Deep event scan at path:/Volumes/Mac OS Lion GM reason:must scan subdirs|
    12/16/11 9:33:37.119 PM com.apple.backupd: Finished scan
    12/16/11 9:36:15.650 PM com.apple.backupd: 758.92 GB required (including padding), 830.32 GB available
    12/16/11 10:25:14.873 PM com.apple.backupd: Copied 22.8 GB of 630.5 GB, 782749 of 2357620 items
    12/16/11 11:25:15.335 PM com.apple.backupd: Copied 86.6 GB of 630.5 GB, 1167675 of 2357620 items
    12/17/11 12:25:16.227 AM com.apple.backupd: Copied 152.2 GB of 630.5 GB, 1393795 of 2357620 items
    Dec 17 01:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 305.2 GB of 630.5 GB, 1413946 of 2357620 items
    Dec 17 02:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 457.1 GB of 630.5 GB, 1419190 of 2357620 items
    Dec 17 03:19:07 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 1736865 files (568.3 GB) from volume Macintosh HD.
    Dec 17 03:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 572.1 GB of 630.5 GB, 1848939 of 2357620 items
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Indexing a file failed. Returned 200 for: /Volumes/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane, /Volumes/3 TB GoFlex Drive/Backups.backupdb/Tom iMac/2011-12-14-171406.inProgress/7DB524DD-EFB9-42A6-8A21-0A2A312EDA6D/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Aborting backup because indexing a file failed.
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Stopping backup.
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 2164998 files (581.1 GB) from volume Mac OS Lion GM.
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copy stage failed with error:11
    Dec 17 03:40:50 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Backup failed with error: 11
    This time it was the Mouse.prefPane that caused the error.  I'd like to exclude the entire PreferencePanes directory.
    This was my error message this time:
    I just realized this was on my small Developers partition.  Perhaps there is an error with the build, OR an error with the initial restore.  I'd like to perhaps exclude the entire /Volumes/Mac OS Lion GM.  I expect that Time Machine is working fine with my main partition and the error happens when it's almost done with the Mac OS Lion GM partition.
    The problem now is that I only have 265 GB of 3 TB available on my Time Machine HDD.  If attempt another backup, it'll surely erase about 410 GB of my past saved backups.  I've already lost 6 months, and I only have two months left of backups.  I need to erase the ".inProgress" package again.  That'll take time, and it's impossible to do from this main partition, even at root access.  This ".inProgress" has a total of two (nearly) full backups; it didn't cleanup the first full backup attempt while starting the second,perhaps it would have had it finished.  But I fear even if I exclude the whole "Mac OS Lion GM" partition,  It'll create a third full backup before cleanup and erase ~400 GB of previous good backups.  Then, I'll have a total of 4 (nearly) full backups!  3 TB is just enough without any past backups.
    Maybe I'll just copy my documentations of my 'errasing the ".inProgress" package'  last time (from the Mac OS Lion GM partition) and do a full restore of just that partition.  Thus erasing the errors all together.  If it doesn't fix the errors then this could be a bug in the build that doesn't allow Time Machine to work.  I've always included this partition in Time Machine before, even with other Lion builds, so I suspect that it was an error in the initial restore.  (I may be answering my own questions, and that the inital restore (of the small partition) is the problem, and I just need to re-restore the small partition)
    Again, I'm going to have to erase the ".inProgress" file to regain 1.53 TB of space before proceeding.
    Also, I gave myself permission to read the ".Backup.345781513.887697.log", the log that was created last night when I first started Time Machine this last time.  It was interesting, but didn't show the error I could see from the console.
    Right now, mds and mdworker appear to be going crazy even after I just now turned off Time Machine.  I think I'll let it go for the rest of the night.  Then I'll work on erasing the ".inProgress" package from the other partition boot up.
    That was my entire last post.  To add some information, I have two OS X partitons, both Mac OS X Lion.  One is my large main partition, the other is one I don't mind testing with.  I recently replaced my internal hard drive in my iMac and restored from Time Machine both partitions.  This appeared to go smoothly.  But I have yet to create a single successful Time Machine backup since.  At first it was doing a Full Backup, which I didn't like, but now it just aborts around 95% completion.  Each, time, it tries it fills the Time Machine hard drive with duplicate (nearly) full backups errasing my older good backups.  I would like to erase the ".inProgress" file to save space.
    My main question in this new discussion is does anyone know of a good way of erasing the ".inProgress" file? This is so I can preseerve my previous backups.  ACLs and other permissions seem to make it impossible to erase from this startup partition, the one I'm running Time Machine from.  Even at root level, if I give myself permission to change permissions or delete a file, it'll say Operation not Permitted instead of Permission Denied.  I have been able to delete this ".inProgress" package before when booting from the other  partition, but with great difficulty.  I have had much help from another Member in this Support Community when it comes to solving my Time Machine problems.  I think I have found the problem (indexing files in my small OS X partition), as stated in my copy& pasted post above, but I really need to delete this inProgress package first to save space before continuing!

    Pondini wrote:
    Gator TPK wrote:
    Now I'll have to fix the small partition?  How's the best way to do this?  There could be thousands of files that won't index fine.
    See if there's anything you haven't done, that applies, in the pink box of #C3 in Time Machine - Troubleshooting
    Otherwise, since most (or all?) of the indexing errors are in OSX, you might want to just reinstall it.  Something may have gone wrong sometime, that damaged those files.
    I reviewed #C3 in Time Machine - Troubleshooting and I have already done most of those things.  I have just learned something new though:
    When I included my Main OS X partition again, I got an indexing error for the first time for that partition.  I might be interesting to note that the _spotlight process was running, and it's running again (the magnifying glass has a dot and it generically says "Indexing Tom's iMac").  mdworker, mds and backupd processes really are working hard, one moment they used over 500% of my CPU.  It's nice to know for once quad core is good for something other than video encoding.  (Now if they could just get the Finder to do more than 100.1%, only 1 thread is doing 100%, I'd like to see file size calculations 8 times quicker!)
    I never got an indexing error once in the past 2 weeks for that large Mac OS X v10.7.2 main volume, and it had appeared to finish that partition backup before running into problems with my smaller test partition.  Also, I had just updated the smaller test partition with a later build of Mac OS X.  But It appears that the beta builds are clearly not the problem.  I thought I could just restore again (from the December 4th backup) the small partition and both would be fine.
    I'll finish reviewing all the suggestions on Time Machine - Troubleshooting and go from there.  Hopefully, the _spotlight indexing simutaniously was the only problem.  It's strange that the indexing hasn't happened since the original restore last week untill I finally got a good clean complete partial Time Machine backup.  Why would the first Time Machine backup trigger indexing again?
    For now, I'm going to exclude the Main Partition again, and let another good backup run.  And try your suggestions.  (And wait till mds, mdworker, etc. to finish!)
    I have the logs of the first two sucsessful backups and the last two failed backups from the last 3 hours, if that would help.?

  • 10.5.6 and Disk Warrior

    After upgrading my Core 2 Duo MacBook to 10.5.6 with Combo Updater, I have had kernel panic when I try to run Disk Warrior (version 4.1.1) after rebooting from external firewire hard drive (with OS X 10.5.5 on external drive). Disk Warrior crashes during step 5 of rebuilding directory file. This is reproducible, occuring three times in a row.
    When I restart the MacBook on internal hard drive, the following error message about kernel panic is generated:
    Mon Dec 15 21:03:54 2008
    panic(cpu 1 caller 0x001A8CEC): Kernel trap at 0x0019807c, type 14=page fault, registers:
    CR0: 0x80010033, CR2: 0x23c23000, CR3: 0x01040000, CR4: 0x00000660
    EAX: 0x23c19000, EBX: 0x00003ff8, ECX: 0x00000006, EDX: 0x00003ff8
    CR2: 0x23c23000, EBP: 0x3de5bc68, ESI: 0x23c23000, EDI: 0x23c1cfe0
    EFL: 0x00010212, EIP: 0x0019807c, CS: 0x00000008, DS: 0x00000010
    Error code: 0x00000000
    Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
    0x3de5ba58 : 0x12b0fa (0x459234 0x3de5ba8c 0x133243 0x0)
    0x3de5baa8 : 0x1a8cec (0x4627a0 0x19807c 0xe 0x461f50)
    0x3de5bb88 : 0x19eed5 (0x3de5bba0 0x3de5bbec 0x3de5bc68 0x19807c)
    0x3de5bb98 : 0x19807c (0xe 0x1950048 0x10 0x34460010)
    0x3de5bc68 : 0x3edb50 (0x3d567a0 0x23c1f020 0x3ff8 0x3d63340)
    0x3de5bc88 : 0x34456aaa (0x23c1f020 0x3ff8 0x195d600 0x2)
    0x3de5bcf8 : 0x34456f39 (0x3fb3d00 0x3d63340 0x0 0x34463000)
    0x3de5bd28 : 0x43abd3 (0x3fb3d00 0x3d63340 0x5566 0x11e42c)
    0x3de5bd78 : 0x18a4f7 (0x3fb3d00 0x4054f48 0x5566 0x4184bc0)
    0x3de5bdb8 : 0x12d17e (0x44fba90 0x4184b9c 0x3de5bdf8 0x11ee14)
    0x3de5bdf8 : 0x126257 (0x44fba00 0x3c679e0 0x16a64b0 0x0)
    0x3de5bf08 : 0x1974c2 (0x3de5bf44 0x0 0x0 0x0)
    0x3de5bfc8 : 0x19f4a3 (0x440d2a0 0x0 0x1a20b5 0x4516128)
    No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xbfffe2a8
    Kernel loadable modules in backtrace (with dependencies):
    com.alsoft.Preview(4.1.1)@0x34455000->0x3445cfff
    dependency: com.apple.iokit.IOStorageFamily(1.5.2)@0x824000
    BSD process name corresponding to current thread: DiskWarrior
    Mac OS version:
    9F33
    Kernel version:
    Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT 2008; root:xnu-1228.7.58~1/RELEASE_I386
    System model name: MacBook2,1 (Mac-F4208CA9)
    Model: MacBook2,1, BootROM MB21.00A5.B07, 2 processors, Intel Core 2 Duo, 2 GHz, 2 GB
    Graphics: kHW_IntelGMA950Item, GMA 950, spdisplays_builtin, spdisplaysintegratedvram
    Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
    Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
    AirPort: spairportwireless_card_type_airportextreme, 1.4.8.0
    Bluetooth: Version 2.1.3f8, 2 service, 0 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: TOSHIBA MK8034GSX, 74.53 GB
    Parallel ATA Device: MATSHITADVD-R UJ-857D
    USB Device: Built-in iSight, (null) mA
    USB Device: hub_device, (null) mA
    USB Device: Generic USB Audio Device, (null) mA
    USB Device: Back-UPS ES 550 FW:840.B2.D USB FW:B2, (null) mA
    USB Device: IR Receiver, (null) mA
    USB Device: Apple Internal Keyboard / Trackpad, (null) mA
    USB Device: Bluetooth USB Host Controller, (null) mA
    FireWire Device: elephantdrive, Elephant Storage, 400mbit_speed

    Problem solved (I hope). For reasons (present since 10.5.0 and not fixed in 10.5.6), Leopard has a problem sometimes with Spotlight (and other programs) taking over the CPU (see MacOsxHints 10.5: One fix for a runaway syslogd process <http://www.macosxhints.com/article.php?story=20071030233438149>). This creates problems with restarting and shutting down as well as difficulty doing much of anything.
    The ATSserver and Syslogd processes were consuming 60-110% of the CPU at times, according to Activity Monitor. This has been a recurrent problem with Leopard and obviously still persists with 10.5.6.
    I re-installed Leopard from the Leopard DVD and upgraded to 10.5.5. I will wait until the dust settles with all the many complaints about 10.5.6 before upgrading. Meanwhile, Disk Warrior works fine with the reinstalled hard drive with Spotlight turned off.

  • Mingler for Entourage Sync with iCal using up CPU and slowing down iMac

    Why has this topic about mingler and ical external sync and mdworker eating up tons of CPU been archived when it was not solved?
    http://discussions.apple.com/message.jspa?messageID=11414905#11414905

    Threads are archived when there is no activity. Iyt has nothing to with them being solved or not.
    Allan

  • EncoderServer and Thumbnail not responding

    I just opened up my iDVD for the first time (bought computer in March). Software update asked if I wanted to update things... I did. Now my computer is getting super hot and loud. When I bring up activity monitor it shows EncoderServer and Thumbnail(something) not responding. It stops when I close iDVD.
    Can I still successfully use iDVD? How do I fix this problem?
    On a sidenote... since the updates I'm getting mds and mdworker taking up lots of CPU also (when nothing is open). What's going on?

    Here's what I'd do...
    Go to your project's info/settings and change the encoding setting from Best Performance to Professional Quality. Best Performance is a con basically. It encodes your video in the background to a very low standard and this fools you into thinking you're getting better performance... but it's at a huge cost. When finalising your project, save it as a disk image instead of direct burning (not recommended if your project requires a Double Layer DVD). Later you can use Disk Utility to burn the image. You can give the image file to anyone else with a Mac and they can produce their own copies without needing iDVD or other DVD duplication method.
    Your Spotlight (md = metadata) index may be corrupt. Go to the Privacy tab of the Spotlight pane in System Preferences and drag in your HD icon. This should delete your Spotlight index. I tend to close System Preferences to ensure that takes effect. Now go back again and remove your HD from the Privacy listing. This will allow Spotlight to set up a new index. This will take some time so only do this when you dont mind the re-indexing process. It should finish and mds and mdworker should leave you alone.

  • Mdworker : Unable to talk to lsboxd ?

    Hello,
    Bonjour,
    My recent problem : here is the messages that I can see in my console.
    Voici le problème que j'ai actuellement, vous trouverez ici les messages d'erreur que je peux lire dans la console:
    Nov  8 12:38:08 MacBook-Pro-de-Sebastien.local mdworker[278]: Unable to talk to lsboxd
    Nov  8 12:38:08 MacBook-Pro-de-Sebastien.local mdworker[279]: Unable to talk to lsboxd
    Nov  8 12:38:08 MacBook-Pro-de-Sebastien.local sandboxd[280] ([278]): mdworker(278) deny mach-lookup com.apple.ls.boxd
    Nov  8 12:38:08 MacBook-Pro-de-Sebastien.local sandboxd[280] ([279]): mdworker(279) deny mach-lookup com.apple.ls.boxd
    Nov  8 12:38:09 MacBook-Pro-de-Sebastien kernel[0]: Sandbox: sandboxd(280) deny mach-lookup com.apple.coresymbolicationd
    Nov  8 12:38:42 MacBook-Pro-de-Sebastien.local com.apple.SecurityServer[15]: Session 100016 created
    Nov  8 12:40:09 MacBook-Pro-de-Sebastien.local mdworker[290]: Unable to talk to lsboxd
    Nov  8 12:40:09 MacBook-Pro-de-Sebastien.local mdworker[289]: Unable to talk to lsboxd
    Nov  8 12:40:09 MacBook-Pro-de-Sebastien.local sandboxd[291] ([290]): mdworker(290) deny mach-lookup com.apple.ls.boxd
    Nov  8 12:40:09 MacBook-Pro-de-Sebastien.local sandboxd[291] ([289]): mdworker(289) deny mach-lookup com.apple.ls.boxd
    Nov  8 12:40:10 MacBook-Pro-de-Sebastien kernel[0]: Sandbox: sandboxd(291) deny mach-lookup com.apple.coresymbolicationd
    Nov  8 12:44:10 MacBook-Pro-de-Sebastien.local mdworker[297]: Unable to talk to lsboxd
    Nov  8 12:44:10 MacBook-Pro-de-Sebastien.local mdworker[296]: Unable to talk to lsboxd
    Nov  8 12:44:10 MacBook-Pro-de-Sebastien.local sandboxd[298] ([297]): mdworker(297) deny mach-lookup com.apple.ls.boxd
    Nov  8 12:44:10 MacBook-Pro-de-Sebastien.local sandboxd[298] ([296]): mdworker(296) deny mach-lookup com.apple.ls.boxd
    Nov  8 12:44:11 MacBook-Pro-de-Sebastien kernel[0]: Sandbox: sandboxd(298) deny mach-lookup com.apple.coresymbolicationd
    Why and how can I resolve thos problem?
    Pourquoi ces erreurs et comment les réparer?
    Thanks :-)
    merci :-)
    (my english is very bad...)
    (mon français est nettement meilleur...)

    I just posted this question: slow time machine, console messages: mdworker unable to talk to lsboxd, and mdworker 32: etc......   Then I saw this thread.  could you comment further on this being a known apple problem and they have to fix it.  makes sense apple needs to fix this but are you saying there is no way for me to fix this?Not sure if my second console message is related?  thanks

Maybe you are looking for