Verify Indexer is actually working?

i think there was a way to see this on the windows version. is there a way on Mac to see if the indexer is actually working? It's been showing 3 hours left for like 6 hours.

I should mention that this isn't an initial index either. This was an additional addon of about 46MB's from last night.

Find more posts tagged with

Comments

Kevin Becker

The indexer's ability to forecast how long it will take is pretty poor.

The best clue to the indexer running/not running is to look at the system monitor to see if the processor is being utilized heavily, if not then it's possible the indexer is hung on something.

T Gerold Castle

https://community.logos.com/discussion/comment/200096#Comment_200096

I ran activity monitor and got this... There was a way to look at the index file though to see it working.... i just can't remember how. Maybe it was on Mac but I know I did it.

Here is the activity monitor results... Thoughts?

John Fidel

https://community.logos.com/discussion/comment/200103#Comment_200103

Tom,

The latest beta will rebuild your index. This can be a long, ie many hours, process. Logos4 indexer is right on the list using 1.56 gigs of virtual memory.. I suggest you let it complete without interruption.

Jack Caviness

https://community.logos.com/discussion/comment/200103#Comment_200103

Here is the activity monitor results... Thoughts?

Looks like the Indexer is really busy 132% CPU with 1.56GB of virtual memory. Virtual Memory is 3 times larger than Real Memory. How much RAM do you have installed? You may need more.

T Gerold Castle

https://community.logos.com/discussion/comment/200106#Comment_200106

Here is the activity monitor results... Thoughts?

Looks like the Indexer is really busy 132% CPU with 1.56GB of virtual memory. Virtual Memory is 3 times larger than Real Memory. How much RAM do you have installed? You may need more.

Yes... I am maxed out at 2GB on this 4 year old MBP. I am hoping to be able to purchase a new one in the middle of January so I'm muddling through

To the point about the new beta... It had already completed the indexing on the new beta install yesterday morning. I used it all day yesterday. Last night, some new downloads came in. Its been indexing ever since.

John Fidel

https://community.logos.com/discussion/comment/200133#Comment_200133

It was the additional downloads that caused the rebuild of my indexes. Sorry that I was not more clear. Hopefully this is not a bug that causes a complete rebuild each time a new resources is added. Perhaps a comment should be added to the beta forum...

Jack Caviness

https://community.logos.com/discussion/comment/200133#Comment_200133

Yes... I am maxed out at 2GB on this 4 year old MBP

The progress of technology is good in many respects, but it does make equipment obsolete too soon. I remember wondering what I would ever do with a whopping 5MB (that is megabyte) HD.

T Gerold Castle

https://community.logos.com/discussion/comment/200145#Comment_200145

The progress of technology is good in many respects, but it does make equipment obsolete too soon. I remember wondering what I would ever do with a whopping 5MB (that is megabyte) HD.

No doubt... And Logos NEEDS those other 2 GB of Ram. When I first bought Logos back in October, I wanted to use it on my Mac. On 'MY' machine, it just wasn't usable at that point. The new beta has made it 'at least' usable. Well, it was yesterday [:)]

I believe with a new machine (i'm getting a 17" with 4GB Ram and 7200 RPM hard drive) that it'll cruise along just fine.

T Gerold Castle

https://community.logos.com/discussion/comment/200153#Comment_200153

Oh no...

The indexer finished about 10 minutes ago. I restarted my computer (habit) and the indexer has started back up again.... Oh my!

T Gerold Castle

https://community.logos.com/discussion/comment/200166#Comment_200166

Ok.. This is getting frustrating.

T Gerold Castle

https://community.logos.com/discussion/comment/200168#Comment_200168

BTW - I remember the answer to my original question. You can actually double click on indexer.log and Console opens up and allows you to see what is going on in real time with the log.

T Gerold Castle

https://community.logos.com/discussion/comment/200251#Comment_200251

If anyone is interested, I've posted logs here so that someone can tell me what is going on. Indexer is clearly not getting all the way through.