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.

Similar Messages

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?

Macbook pro late 2011 is on Mac OS X v10.7 Lion and it is using lot of RAM

Macbook pro late 2011 is on Mac OS X v10.7 Lion and it is using lot of RAM...when I turn on after 2minutes it freezes and do not repond and system prefrences also not working...plz help me....I don,t have mac os disc
I have tried safe mode boot, NVRAM and PRAM reset but no luck...

First, try a Safe Mode boot.
Startup your Mac in Safe Mode
A Safe Mode boot takes a longer than a normal boot so be patient.
Once you are in Safe Mode, click Restart from your Apple () menu.
If that didn't help, reintall OS X..
Restart your Mac while holding down the Command + R keys so you can access the built-in utilities in OS X Recovery
message edited by: cs

Dock uses lots of CPU time

I find Dock uses ~140% CPU time sometimes, I can't see a cause for it to do so. It usually stops of its own accord after a random amount of time. Killing it doesn't help, launchd restarts it and it goes back to using lots of CPU.
I have parallels install and I have the version which has the fix (6.0.12106) and I have also tried the work around (no luck obviously).

Never mind, I figured it out by myself. On this particular machine I had a 3rd party plug-in installed (SRS iWow 1.1.8). Removing that brought the CPU usage down to 0.1%. Usually I don't install 3rd party add-ons. This would seem to be a good policy.
Steve

Syslogd process uses all available cpu & console app won't run.

I have a Mac Mini (G4 power PC) running 10.5.5. Just recently after several minutes the system never wakes. It just shows the SBBOD. All I can do is hold down the power button and reboot. When the system reboots, using the activity monitor, I see that the process named syslogd uses all available cpu. I can still do things, but the cpu is saturated.
I took a snapshot of the syslogd process, and I can post it here if anyone thinks it might help.
If I activate the console application, the window comes up then hangs with the SBBOD.
The syslogd process uses all available cpu right after reboot, and does so regardless of which user (including root) is logged in. Attempting to kill the syslogd process with the activity monitor does nothing

Thanks! It took a long time for the disk utility to fix the permissions, but as soon as it did, the logger process calmed down. Looking at the log file now, I see it was my McAfee virus scan causing the logger to flip-out.
I'm now looking for a new MAC anti-virus program.

Spotlight constantly indexing and Time Machine endlessly preparing backup

Hi,
I have a Macbook Pro 5,5 and Mac OS X 10.8.4
Lately I noticed that Spotlight was pretty much constantly indexing, so I went to "System Preferences/Spotlight/Privacy" and I dragged my HD there to prevent Spotlight from indexing it. Then rebooted my laptop and removed my HD again, which caused my Spolight to start indexing again.
After a night of indexing, everything seemed to be working fine. Nevertheless, today Spotlight is once again constantly indexing my computer, and the bar just won't go beyond "Estimating Indexing Time". What could I do to solve this issue?
Related to this, I assume, is my inability to backup through Time Machine. I feel like Time Machine is waiting for Spotlight to complete its indexing in order to start its backup-job, is that correct?
Thanks for your help,
Sander

If you have more than one user account, these instructions must be carried out as an administrator.
Triple-click anywhere in the line below on this page to select it:
syslog -k Sender mdworker -o -k Sender mds | grep -v boxd | tail | open -f -a TextEdit
Copy the selected text to the Clipboard (command-C).
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V).
The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. The title of the window doesn't matter, and you don't need to post that.

Cannot disable spotlight - endlessly indexing

Hello all,
I cannot disable spotlight - it is endlessly indexing. I have dropped the main drive into Provacy under Spotlight. I have dropped my other 3 drives there as well. I have taken them out and reurned them many times - no change. I repaired disk permissions many times - no change. I downloaded and installed the 10.6.8 Combo update - no change. It keeps indexing and says: Indexing _____________'s Mac Pro. And the estimated time is not there - just that barber pole. And I believe it is affecting my applications - I am having major problems with Avid's Pro Tools 9.0.6.
Is there anything else that I can try? I do own Spotless but I stopped using it over a year ago - it didn't seem to do anything more than what I could do using the Privacy option. It it possible that Spotless might be able to do something that I cannot?
Any ideas would be welcome.

Maybe some file is corrupt in such a way to hang up spotlight. Is it possible for you to run with just your boot drive with the other 3 drives physically removed from the machine? See if it loops that way. If so something may be going on with the boot drive. If not, start adding the removed drives back one-by-one until it gets caught in the loop again.
If this method works at least you can narrow it down to a specific drive. Of course that won't tell you what the problem is on that drive but you at least have a single drive to concentrate on as opposed to 4 of them.
Since you already tried adding these drives to privacy I am not going to suggest the mdutil command to erase the indices (-E) or flag for no indices (-i). I don't think it will change anything and of course won't resolve why it is looping.
Also note that this problem is not unique. Look at the right side of this page for More Like This.
Related articles:
Turning Off Spotlight
The X Lab: Spotlight Tips

Screen Sharing and WindowServer processes using 35-45% of CPU!!

I have recently relocated and reconfigured my Apple network and computers in the house :1) MacBook Air dual display MBA with 20" cinema screen in the office, and 2) and Mac Mini connected to a large LCD TV in the living room.
The plan now is to use the MBA as a primary computer and connect via wireless screen sharing to the MM so that I can monitor that system, run more intensive apps, watch EyeTV, file server tasks, etc.
But now this has increased CPU and fan activity on the MBA beyond what I would expect. The activity monitor indicates that the Screen Sharing and WindowServer processes are using combined between 35-45% of the CPU (screen share process is a constant 25%!!).
This is not good, and I wonder if it will be fixed in a future release. Any ideas or suggestions on how to limit the impact of screen sharing on CPU?

It seems to be running better with system update, and use of a faster computer (now using the higher end mac book air)

Spotlight endlessly indexing

I recently defragmented my hard drive, and since I did that, Spotlight has not been working properly. When I start up my computer, Spotlight runs fine, but after about 30 minutes, it only says "Indexing Hard Drive." I figured, fair enough. But I left it going for over 14 hours, and it still hasn't even started. It has looked like the link for the past 14 hours, and won't go past this stage. I've rebooted in safe mode, and done everything I can to get Spotlight to work, but to no avail. I have Mac OSX 10.6.4. My hard drive is 500 GB at 5400 RPM. Any suggestions?
Screenshot: http://dl.dropbox.com/u/7739498/Screen%20shot%202010-06-28%20at%201.46.24%20PM.p ng

You are a lifesaver. Fixed it perfectly.
For those who might be having this problem, here's exactly what I did.
1. Opened "System Preferences" and went to "Spotlight"
2. Went to the "Privacy" tab
3. Clicked the plus sign at the bottom of the list (Add)
4. Added "Macintosh HD" to the list
5. Quit System Preferences and pressed +Space to see if the problem was fixed (it wasn't)
6. Restarted my computer and logged in
7. Pressed +Space to see if Spotlight was indexing (It wasn't, but that's normal: it usually work for about 20 minutes before starting to try to index)
8. Went to System Preferences-->Spotlight-->Privacy, selected Macintoish HD and pressed the minus sign
9. Pressed +Space to see if Spotlight worked (It was giving me the same message it was before)
10. Closed Spotlight and waited about 40 seconds
11. Pressed +Space again, and Spotlight was about a tenth of the way through indexing
12. Waited about 10 minutes
And voilá, Spotlight has been working ever since. Thank you so much.

Airport process using 90%+ of CPU

I have a MacBook and for some reason, using the activity monitor I see Airport is using up almost one full core. I've tried rebooting and such and airport is always using a lot of CPU time. Its very annoying since all this processor usage is causing my fan in my Macbook to run at full throttle all of the time. I'm on a wireless G network with WPA.

I have a MacBook Pro and I am experiencing the same problem. After each reboot or wakeup a process called airport (probably /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/air port) takes up a lot of CPU.
I just kill the process. After a reboot, killing needs administrator rights, but then almost immediately the process starts again. Killing it again makes it go away till the next wakeup or reboot.
It seems that wakeup in the neighborhood of a WiFi base guarantees this problem. However, on the road out of reach of any base, I can usually wake up the machine without a problem.
Killing the process does not seem to interfere with correct functioning of airport in any way.
As said before: it eats away battery life and makes the machine uncomfortably hot. Apart from that, because a lot of CPU is being used by this process, it is very hard to resume your work after a wake up because the machine becomes very unresponsive.
As a temporary measurement, I launch activity monitor automatically. The amount of clicks to kill the process is then minimal. Still, it is annoying and makes me look clumpsy if I am rewaking my machine for a presentation or meeting.
PowerMac Cube/450 Mac OS X (10.4.8)

Concurrent manager using lots of cpu & memory

In the last few days, I have noticed the load on the production server as follows:
load averages: 4.66, 4.86, 4.92 14:34:16
333 processes: 327 sleeping, 6 on cpu
CPU states: % idle, % user, % kernel, % iowait, % swap
Memory: 32G real, 7591M free, 23G swap in use, 14G swap free
PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND
20045 appsdapo 1 0 0 4073M 4029M cpu/2 165.0H 12.49% f60webmx
1854 appsdapo 1 10 0 4082M 4060M cpu/0 240.0H 12.48% FNDLIBR
2504 appsdapo 1 10 0 1872M 1869M cpu/19 1980.2 12.46% FNDLIBR
2496 appsdapo 1 0 0 1876M 1873M cpu/1 1957.5 11.68% FNDLIBR
18641 appsdapo 1 10 0 1512M 1509M cpu/16 1080.3 8.64% FNDLIBR
I have come across Metalink note ID 114380.1 which says identify the C.M but how do I relate the FNDLIBR processes above with the specific C.Managers.
Thanks

Hello,
Thanks for the Post. This post helped me to solve my production issue.
My production application started hanging suddenly and no clue why it is behaving like this.
The symptom was FNDLIBR processes were on top cpu consumer on application server.
The database server also experienced heavy system i/o and cpu usage.
The database base log switches every minutes (500 MB) and there are no concurrent requests running.
No concurrent request errors. No OS errors (Cleaned the GNOME and restarted). No database errors.
But in sql area i saw lot of fnd service requests keep coming.
At the end the application server hangs because of high cpu and it caused the production down.
The problem was one of Our System Administrator disabled one responsibility with scheduled request.
One interesting thing we noticed, even you put the request in question Hold, it will start running while you restart the concurrent request.
You have to cancel the concurrent request and restart the concurrent manager can solve the issue.
Thx
Pouler

Possible to stop TREX indexing and restart later using queue?

Hi all, has anyone stopped an RSTIRIDX indexing job and then restarted it to continue indexing on TREX using a queue? When I restart the RSTIRIDX job the queue is invalid and cannot resume indexing.
Thanks.

Unfortunately, we have 800-1000 hard drives to churn out in a small period of time with limited space to do so and based on the math.....the only way to achieve that goal is via hard drive replication.
I don't think that's entirely true. You can get an OSD to perform pretty quickly as well. Especially if it's a POS system and not loaded down with tons of "standard" apps like normal desktops are. Not to mention you can implement things like Offline
Servicing and everything to ensure the machine is ready with the latest updates upon completion.
In the short term I was hoping to build a task sequence with the base image, apply drivers and the shutdown. Upon powering on, (post drive replication)I want the task sequence to resume, join the domain, and apply my customizations.
This is essentially what a task sequence does only automated. What are "my customizations"? and why couldn't those just be replicated through a TS?
Is it feasible to insert a command to shutdown during the task sequence and then reasonably expect that when it is turned back on the task sequence will resume?
Regards,
Doesn't work. When a machine begins a Task Sequence it has a unique ID that SCCM monitors. You can't have 50 come online and have SCCM think they should all run the same "second half" of a Task Sequence.
Honestly, a TS exists to simplify and automate and speed up an already arduous and timely task. I don't see how you could speed it up manually copying hard drives using a driver replicator and call it "faster". You are basically talking about how
they used to "image" machines in the 90's :-P
Dustin Estes - MCP | www.dustinestes.com

Can VLOOKUP, OFFSET, INDEX and MATCH be used to SUM the value of cells from multiple tables?

I have a problem thats needs a sulution. I have a Spreadsheet with multiple sheets and tables. The (Truck ) Sheets each represent a "Site" and the tables within from 1-31 show inventory counts for each day of the month.
Shown below are Edited example's of a "Site" sheet and the Day tables contained within it.
The Spreadsheet expands as a new "Site" (Truck ) is added regularly. Currently there are 30 "Sites" (Trucks).
Also within the spreadsheet is a sheet (Checkpoint) which contains tables used to show summary data for each "Site" sheet. There is one table used to review one site, so currently there are 30 tables identical in format and structure reviewing 30 sites.
An edited example of the summary table for Truck 1 is shown below.
The table's in CP reference data within cells from other sheets. A LEN INDIRECT formula
=IF(LEN(INDIRECT("Truck 1::Day "&COLUMN(cell)−3&"::K53",addr-style))<1,"",INDIRECT("Truck 1::Day "&COLUMN(cell)−3&"::k53",addr-style))
was used to retrieve the values within certain cells. This formula works perfectly because when I add another "Site" I simply need to Dupicate a "Site" Template Sheet and then Copy Paste the LEN INDIRECT formula in to the newly created Summary table.
There is another sheet (Command Central) which contains a Master summary table. The Master Summary sheet is identical in structure to the CP Summary Tables. Its purpose is to show the combined data from the tables within Checkpoint (Truck 1-30). for instance MS::D5=Checkpoint::Truck 1:Truck 30::D5. I realize that Numbers cannot calculate cells within a range of table so I am hoping for a workaround.
Could someone please help me with a formula something like the LEN INDIRECT formula mentioned above or possible a something else that could work beside
D5=Truck 1::D5,Truck 2::D5,Truck 3::D5...?
When I use that formula type I will have to edit the formula every time I add a new site.
Anothe issue Im having is getting D3:AH3 to show the correct count of names. I am using the following formula:
D3=SUM(COUNTA(Truck 1::D3,Truck 2::D3,Truck 3::D3,Truck 4::D3))−SUM(COUNT(UNION.RANGES(Truck 1::D3,Truck 2::D3,Truck 3::D3,Truck 4::D3)))
The cells it is counting are either blank (the refenced cell contains a LEN INDIRECT formula that places "" if needed) or contain a name. This formula works when I and addressing cells without the LEN INDIRECT formula. What am I doing wrong?

Hello Wayne,
Here are screenshots of the tables in question. The first on is the Master summary table.
Cell D5 shows the value pulled from Checkpoint::Truck 1::D5
Cell E5 shows the value pulled from Checkpoint::Truck 2::D5
Cell F5 shows the value pulled from Checkpoint::Truck 3::D5
Cell G5 shows the value pulled from Checkpoint::Truck 4::D5

Apple tv and home sharing using lots of data??

Just purchased apple tv and turned on home sharing to listen to songs in my iTunes library through my home theater. I am not streaming video or listening through iCloud. My satellite data usage went through the roof. About 350MB in alittle over an hour. I unplugged the apple tv and still had usage. About 50 MB the next hour. I turned off home sharing and the bleeding stopped. That type of continuous datat usage would consume my monthly data allowance in no time.
Without a solution I will have to return my apple tv. :( Please help. Thanks

Is some broadband use to be expected. I would not have thought so but perhaps I am wrong. Any help, insight or information would be greatly appreciated.
Thanks in advance

Spotlight endlessly indexing and mdworker process using lot of cpu

Similar Messages

Maybe you are looking for