7 Replies Latest reply: Dec 1, 2011 7:03 AM by netnothing
Allison Sheridan Level 1 Level 1

I've been having periodic system hangs (hangs until I force a shut down).  when I check the console log I find a zillion entries saying:

11/27/11 9:02:02.645 AM mdworker: (Normal) Import:  exceeded time/resource use limits after 12003 milliseconds, reason:1 - find suspect file using: sudo mdutil -t 441183

 

ruing the mdutil command tells me the suspect file is Aperture Library.aplibrary

 

My Aperture library is 118GB (every photo I've taken since 2001) so perhaps when spotlight indexes it it just takes a REALLY long time?  I'm hoping that's not it because I really don't want to go to the work of splitting up the library.  I did repair permissions on the Aperture library but I didn't yet repair or rebuild the database.  I did that not more than a month ago because of another problem.

 

any ideas?

 

Allison Sheridan

NosillaCast Podcast <edited by host>

A technology geek podcast with an EVER so slight Macintosh bias!

<edited by host>


Aperture 3, Mac OS X (10.7.2), MacBook Pro 2011
Reply by Kirby Krieger on Nov 27, 2011 11:41 AM Helpful

Do you need Spotlight to index your Library?  I'd put it in Spotlight's "Privacy" list (i.e.: "ignore these"), then reboot and then repair your Library (using the usual trouble-shooting tools) and then reboot again.

 

Once that settles down, you can add your Library back, but you should set it up so that Spotlight can run uninterrupted at least overnight.  The initial indexing is the problem (or was for me, under Snow Leopard).  Once it was finished I had no further problems.

All replies

  • Kirby Krieger Level 6 Level 6

    Do you need Spotlight to index your Library?  I'd put it in Spotlight's "Privacy" list (i.e.: "ignore these"), then reboot and then repair your Library (using the usual trouble-shooting tools) and then reboot again.

     

    Once that settles down, you can add your Library back, but you should set it up so that Spotlight can run uninterrupted at least overnight.  The initial indexing is the problem (or was for me, under Snow Leopard).  Once it was finished I had no further problems.

  • Allison Sheridan Level 1 Level 1

    I was thinking about that - I don't ever use spotlight to search for a photo - I'm super anal about my project names (date and event in the name) and I actually name every photo too so using Aperture search works fine.

     

    I'll give this a try, thanks Kirby!

     

    Allison

     

     

    < Edited by Host >

  • netnothing Level 1 Level 1

    Same here Allison.  Ever since Lion I've had these error message for my Aperture library.  I haven't had the slowdows you talk about......but the messages are still there.

     

    My Aperture Library is 207GB.

     

    Let me know if you figure anything out.

     

    -Kevin

  • Allison Sheridan Level 1 Level 1

    I wish I could change Kirby's answer from Helpful to Correct, because putting the aperture library in the Spotlight's Privacy list fixed the indexing problem.  Now if I could figure out what the NEXT thing crashing my system is...but that's a subject for the USB forum, not Aperture...

     

    Allison Sheridan

    NosillaCast Podcast

    A technology geek podcast with an EVER so slight Macintosh bias!

     

    <Edited by Host>

  • Kirby Krieger Level 6 Level 6

    Glad it worked 

     

    Good luck with the USB issue -- I had a USB mouse that caused kernal panics on one machine only.  A very willing technician and I spent a week trying to debug it, and then gave up.  (Fwiw, that was on -- iirc -- Tiger.)

     

    (PS:  I think links such as in your signiture are prohibited by the User Agreement.  Our Host edits them out.)

  • Allison Sheridan Level 1 Level 1

    thanks for the tip - I didn't know that, it always looked like it worked on my end.

     

    Allison Sheridan

    NosillaCast Mac Podcast

  • netnothing Level 1 Level 1

    So does anyone know what features you may lose by not having your Aperture Library in the Spotlight index?

     

    Does it limit searching in Aperture?

     

    Think I'll submit a bug with Apple to see if I can get someone to realize that this exists.  Wonder if people get the same error with large iPhoto libraries?

     

    -Kevin