Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By BradM on
Been seeing this message for weeks: 73% of the site has been indexed. There are 2000 items left to index.
From what I understand, this is a known problem.
http://drupal.org/node/146466
This patch implements the node link tracker changes in the search indexer.
http://drupal.org/node/192348
A second patch to fix an upgrade problem resulting from using the above patch.
I guess I'm trying to figure out what to do, it's hard for us non-techie types to decipher all the messages. Currently I'm running Drupal 5.1. Will an upgrade to 5.2 solve the site indexing problem? Or do I have to add both these patches?
Thanks for any help.
Comments
no, no
The issues you link above are for 6.x - applying such a patch would be very likely to break your system.
I have seen previous forum posts with a similar problem - do a search. If I recall, the problem turned out to be a node in PHP format that contain a drupal_goto() or other such redirect. Any possibility you have such a thing?
---
Work: BioRAFT
still stuck
Well actually I did a search prior which is where I found the other threads. Searching deeper indicated a couple of other things, but I see that my story is the same as others. I run poormanscron. I tried running cron.php manually, but like others, it just fails. The index used to always be at 100% until recently.
I've never used the drupal_goto() code, so I can't see it ending up in a node...tried searching for it anyway but nothing came up. Is there any way to look at the database tables to see the last item indexed? If I can find the problematic node, then I can fix it.
another thing
now that I think of it - nodes set with dates in the future can bork the search process too.
look in the {variable} table at node_cron_last - this should correspond to the date of the last node indexed: search the `changed` column of the {node} table for a matching value.
---
Work: BioRAFT
thanks for the
thanks for the suggestions... I don't seem to have a node_cron_last table or anything related. Also just noticed that my site search returns no results, no matter the term. So it appears that something much bigger is wrong. :-(
wipe index
Is there a way to wipe the entire index and start from scratch? I am under the impression that if you re-index, it keeps the original but then builds on it.
So far my index gets stuck, and the search doesn't work at all, returning zero results. I'm hoping there's a way to fix this.
still stuck
I did manage to find node_cron_last and via the search it also shows node_cron_last_nid which is the last node that was indexed.
I've been trying since to look at these nodes, delete, re-add and re-index, yet the search still fails around 71%, and it's at a different node each time.
There's got to be some solution to this, it's driving me crazy!
^^ bump ^^ still no
^^ bump ^^
still no solution...
I'm also having the same
I'm also having the same problem - my site index is stuck on 72%.