Paused? I don't have no stinking time for pausing!

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Greg D. Moore \(Strider\) - 11 May 2005 05:06 GMT

Ok, why are my indices all paused?

Ran out of diskspace the other day. Stopped the Service, moved the indices
to another drive (had a little problem with 1-2 of them which I believe I've
fixed.)

Have restarted, and every full text index on the machine, including one in a
different DB is in a paused state.

They have data and a search on them returns data.

But select fultextcatalogproperty('foo','populatestatus') returns 2.

What's up with that?

(This is on SQL 2000. Thankfully finally I'm moving off of SQL 7.0).

Signature

--
Greg D. Moore
President Green Mountain Software
Personal: http://stratton.greenms.com

Reply to this Message

Hilary Cotter - 11 May 2005 16:07 GMT

MSSearch will pause for several reasons; low disk space; memory pressures,
or if you are running on battery power.

Use the gatherlog utility to see if it gives any more hints as to why they
are paused. You can find it in C:\Program Files\Common Files\MSSearch\Bin
and it is called gthrlog.vbs. Copy this file to %windir%\system32

Then open a command prompt and navigate to the C:\Program Files\Microsoft
SQL Server\MSSQL\FTData\SQLServer\Gatherlogs

then do a dir /od locate a recent log and do this

cscript.exe gthrlog.vbs SQL0000600005.1.gthr

Replacing SQL0000600005.1.gthr with the name of your log.

This should reveal more details as to why MSSearch is pausing.

Signature

Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

> Ok, why are my indices all paused?
>
[quoted text clipped - 12 lines]
>
> (This is on SQL 2000. Thankfully finally I'm moving off of SQL 7.0).

Reply to this Message

Greg D. Moore \(Strider\) - 11 May 2005 23:08 GMT

> MSSearch will pause for several reasons; low disk space; memory pressures,
> or if you are running on battery power.
[quoted text clipped - 11 lines]
>
> Replacing SQL0000600005.1.gthr with the name of your log.

Ok, to reduce the number of variables, I did this on the full text index in
a different database that I did not touch: (i.e. it's not due to me moving
stuff, etc...)

Results are:

Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

5/10/2005 11:22:04 AM Add The gatherer has started
5/10/2005 11:22:12 AM Add The recovery has completed
5/10/2005 11:38:52 AM Add The gatherer has started
5/10/2005 11:39:04 AM Add The recovery has completed
5/10/2005 12:13:52 PM Add The gatherer has started
5/10/2005 12:14:02 PM Add The recovery has completed
5/10/2005 1:28:02 PM Add The gatherer has started
5/10/2005 1:28:10 PM Add The recovery has completed
5/10/2005 2:03:02 PM Add The gatherer has started
5/10/2005 2:03:12 PM Add The recovery has completed

Yet, the index is still paused.

Just tried to STOP the population on this paused index.

The tail of the new gather file shows:

5/11/2005 5:59:14 PM mssql75://sqlserver/2dffd964/00004418 Add
Error fe
tching URL, (80040d54 - The filtering has been aborted because of a user
action,
such as stopping the crawl. )
5/11/2005 5:59:14 PM mssql75://sqlserver/2dffd964/00004c9a Add
Error fe
tching URL, (80040d54 - The filtering has been aborted because of a user
action,
such as stopping the crawl. )
5/11/2005 5:59:14 PM mssql75://sqlserver/2dffd964/000043e6 Add
Error fe
tching URL, (80040d54 - The filtering has been aborted because of a user
action,
such as stopping the crawl. )
5/11/2005 5:59:14 PM Add Completed Incremental crawl

And the index still shows itself as paused.

Looking at a gather file on the index (which I did move) in the original DB:

Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

5/10/2005 11:22:04 AM Add The gatherer has started
5/10/2005 11:22:10 AM Add The initialization has completed
5/10/2005 11:38:52 AM Add The gatherer has started
5/10/2005 11:39:00 AM Add The initialization has completed
5/10/2005 12:13:52 PM Add The gatherer has started
5/10/2005 12:13:58 PM Add The initialization has completed
5/10/2005 1:28:02 PM Add The gatherer has started
5/10/2005 1:28:08 PM Add The initialization has completed
5/10/2005 2:03:02 PM Add The gatherer has started
5/10/2005 2:03:08 PM Add The initialization has completed

And

select fulltextcatalogproperty('foo_bar_1998','populatestatus') as
populatestatus , count(*) as '1998',
fulltextcatalogproperty('foo_bar_1998','itemcount') as itemcount,
fulltextcatalogproperty('foo_bar_1998','IndexSize') as IndexSize,
fulltextcatalogproperty('foo_bar_1998','UniqueKeyCount') as
UniqueKeycount,fulltextcatalogproperty('foo_bar_1998','Logsize') as
LogSize,fulltextcatalogproperty('foo_bar_1998','PopulateCompletionAge') as
PopulateCompletionAge from foo_bar_1998 (nolock)

returns:
Populate status 1998 itemcount, indexssize, uniquekeycount,
logsize populatecompletionage
2 441 442 2
72004 328 482772780

Now, this index had been fully populated before any of these problems
happened, so it should be fine. (i.e. no reason to pause, etc.)

I'm bewildered at this point.

Any other thoughts. (I mean worse comes to worse I'll simply destroy the
indices and rebuild them, but then I'll lose a week or two of time waiting
for the larger ones.)

> This should reveal more details as to why MSSearch is pausing.
>
[quoted text clipped - 17 lines]
> >
> > (This is on SQL 2000. Thankfully finally I'm moving off of SQL 7.0).

Reply to this Message

Hilary Cotter - 13 May 2005 03:05 GMT

I am not sure what you mean by restarted in your original post? Do you mean
a reboot? If not, I would reboot your server to see if this clears the
condition. It is baffling.

Signature

Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

> > MSSearch will pause for several reasons; low disk space; memory pressures,
> > or if you are running on battery power.
[quoted text clipped - 123 lines]
> > >
> > > (This is on SQL 2000. Thankfully finally I'm moving off of SQL 7.0).

Reply to this Message

Greg D. Moore \(Strider\) - 17 May 2005 22:39 GMT

> I am not sure what you mean by restarted in your original post? Do you mean
> a reboot? If not, I would reboot your server to see if this clears the
> condition. It is baffling.

Well, restarted means just that, stopping and restarting all the services in
question.

No joy.

So today I rebooted the box, and still no joy.

So I completely removed one index, including the catalog and recreated it
from scratch.

Now at least the status is 1 - population in progress.

Yet after 4 hours, nothing has been indexed.

Very strange.

> > > MSSearch will pause for several reasons; low disk space; memory
> pressures,
[quoted text clipped - 131 lines]
> > > >
> > > > (This is on SQL 2000. Thankfully finally I'm moving off of SQL 7.0).

Reply to this Message

Hilary Cotter - 18 May 2005 02:33 GMT

when you run profiler does it show lots of activity from PKM, specifically
calls to sp_fulltext_getdata.

Signature

Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

> > I am not sure what you mean by restarted in your original post? Do you
> mean
[quoted text clipped - 112 lines]
> > > fulltextcatalogproperty('foo_bar_1998','UniqueKeyCount') as
> > > UniqueKeycount,fulltextcatalogproperty('foo_bar_1998','Logsize') as

LogSize,fulltextcatalogproperty('foo_bar_1998','PopulateCompletionAge')

> as
> > > PopulateCompletionAge from foo_bar_1998 (nolock)
[quoted text clipped - 42 lines]
> > > > > (This is on SQL 2000. Thankfully finally I'm moving off of SQL
> 7.0).

Reply to this Message

Greg D. Moore \(Strider\) - 21 May 2005 02:19 GMT

> when you run profiler does it show lots of activity from PKM, specifically
> calls to sp_fulltext_getdata.

Well, I sorta "gave in"

I had a suspicion that a 4-5 of the full-text indices I moved may have been
the source of the problem (because I ended up having to hand edit their
registry entries.)

Removing those and the remaining ones started to work.

So now just running an incremental build on the ones that are behind.

Thanks for the help Hilary.

> > > I am not sure what you mean by restarted in your original post? Do you
> > mean
[quoted text clipped - 176 lines]
> > > > > > (This is on SQL 2000. Thankfully finally I'm moving off of SQL
> > 7.0).

Reply to this Message