Search not searching

Dubber Dan - January 16, 2006 - 17:04

I've activated the search for my website here but when I try to search it finds nothing. If I look in Admin>Settings>Search it states that

Indexing status

0% of the site has been indexed. There are 59 items left to index.

But doesn't say how to index the site.

Can anyone help?

CRON will do the job.

Raggart - January 16, 2006 - 17:08

Simply put your browser to http://yoursite.com/cron.php where yoursite.com, obviously, is replaced by the address to your site.

At a guess, you missed step

sepeck - January 16, 2006 - 17:09

At a guess, you missed step 6 of the install.txt
http://drupal.org/handbook/modules/search

You must be running cron.php on your site for it to index.

-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

Help

Steven - January 16, 2006 - 17:22

It does say so, on that very page.

The search engine works by maintaining an index of the words in your site's content. You can adjust the settings below to tweak the indexing behaviour. Note that the search requires cron to be set up correctly.

Ironically, you could've also just searched this site for the answer.

Site not fully indexed

ZoneV - March 7, 2006 - 15:49

I did search the site.

I have cron set up correctly. It runs fine without errors and watchdog is capturing the output...

cron 2006-03-07 10:37 Cron run completed

...but then when I go to Administer | Settings | Search, the indexing status says...

41% of the site has been indexed. There are 27 items left to index.

Subsequently running cron.php doesn't get the site to 100% indexed.

What am I missing?
Thanks!
ZoneV

More on "Site not fully indexed"

ZoneV - March 7, 2006 - 18:30

Decided to clean up the search tables (search_index and search_total) and reindex, but that didn't fix the problem.

Then I went to Administer | Settings | Search and changed the indexing settings to force the index to rebuild and saved the settings. Everything changed back to 0% indexed. Changed indexing settings (word length to index and word length to search for) back to three and re-indexed, but reindexing stops at 47% (there are still 27 items left to index).

Please help!
ZoneV

Still More on "Site Not Fully Indexed"

ZoneV - March 8, 2006 - 19:08

Well, I never got any kind of reply; perhaps I'm not phrasing my posts correctly.

Anyway, try as I might, nothing made the current content index fully to 100%. However, I discovered that if you add new content, the non-indexed content then got indexed along with the new. Don't know if this is by mistake or by design.

Anyway, the site is now up to 100%.

Thought I'd share in case anyone else runs into this. Now that having cron.php working correctly is no guarantee that your site's search index will build correctly.

ZoneV

Back to the same (site not fully indexed)

ZoneV - March 9, 2006 - 12:55

Came in this morning to find out that the index came back down to 49% indexed. Running cron.php manually will not complete indexing. I must be missing some configuration, or else this feature still has bugs that have not been addressed.

ZoneV

The search requires cron

zaja - January 16, 2006 - 17:27

The search module requires cron to be set up correctly, for example:

0   *   *   *   *   wget -O - -q http://www.boahc.co.uk/cron.php

More info: http://drupal.org/node/23714

------------------

Try Poormanscron module

atticus - January 16, 2006 - 17:59

Not being totally unix conversant, I rely on the Poormanscron module:

http://drupal.org/project/poormanscron

It has setting that runs your cron.php file automatically in a given time period.

Does anyone know of a disadvantage of using this?

Best,
Brent
My Drupal Experiment

Is there a way to update the index from the reindex button?

peterx - April 2, 2006 - 19:09

Can the reindex button be changed to perform the reindex instead of setting up then waiting for cron or poormanscron?

petermoulding.com/web_architect

Never got my search to

wickus - April 25, 2006 - 19:27

Never got my search to run.
Have poormanscron running. Probably the stuff to search and to index is too big for a cron run. So I set down the search run to 10 pages and limited words to at least 5 letters. When I run cron.php I get a script error from the server. But cron is working, I disabled search and it finished its run.
Can I empty the node_revisions table and fill it line by line or every 5 lines from the sql backup for example and try to run cron.php after each filling without harming any other entries in the whole database?
Are there any other solutions?

---
Join the virtual march to stop global warming.
http://www.stopglobalwarming.org/marchers/?142067

After I emptied my

wickus - May 21, 2006 - 02:48

After I emptied my node_revisions table and adding 5 lines every time and running cron I got my search to go. And it was working a while with poormanscron, now I don't know why, the search index was empty and it seems to run a bit, had it set to 10 pages it worked till it got to 22%, I set the page rate to 20 I got a server error on cron run. When I switch of the search module, cron works properly. I went into the search module and put a 1 instead of 10 pages per time and I still have the problem with the server error.
Any idea, somebody had a similar problem?

I got it done now....just emptied the index and set the 10 value to 1 page and let it run now every minute...

Beside this,
1. is it possible to add more values in this $items array in the search.module file
2. can I exclude content types from the search? I have the documentation in a book on this site, and secured it with node_privacy_byrole but it would be nice if normal user won't find the pages, looks maybe a bit better when they don't find this pages avoiding them getting the not allowed message.
---
Join the virtual march to stop global warming.
http://www.stopglobalwarming.org/marchers/?142067

I hoped its done, but it

wickus - May 21, 2006 - 14:35

I hoped its done, but it messes around again, now on 21% I am getting server script errors again like yesterday, it was around 22%
---
Join the virtual march to stop global warming.
http://www.stopglobalwarming.org/marchers/?142067

I have a 100% indexed. Cron

hip - May 22, 2006 - 10:50

I have a 100% indexed. Cron seems to work ok. But searchs for terms I DO HAVE in posts show a 'no-result' answer!

I'm on Drupal 4.6 and have locale.module activated (for spanish).

Where should I look for the error / a solution?

Thanx in advance,
hip

Having the same problem

kowalke - June 19, 2006 - 17:02

I'm having the same problem. What's weird is that I have several other installations seemingly setup the same way that don't have this problem, so I'm wondering if there is a module conflict I'm experiencing. New articles just aren't being indexed any longer, even though cron.

Any tips or links to other forums that solve this problem would be GREATLY appreciated.

PoormansAjax

peterx - May 22, 2006 - 12:07

Poormanscron runs some indexing when you look at a page. If that process was linked to Ajax on an administration page then you could have a real time administrator page for rebuilding the index.

The page would submit poormanscron via Ajax to index a small number of pages. On completion, the page would submit the process again for another small step. The Web page would have a button to start the rebuild, a display to show the progress, and a button to stop the process after the current activity.

The administrator could click the rebuild button then eat a pizza, drink a bottle of Jack Daniels, and do all those other typical web site administrator activities while the progress display ticks over. If the rebuild is still running when you want to play with the site then click the halt button. You should be able to return to the rebuild at any time.

A single long running rebuild could hog the Web site but lots of little index tasks separated by gaps could work comfortably even on busy sites. The Web page could leave a small delay between each Ajax request so that other Web site activity gets a chance.

If someone wants to tackle the task, I can help them with the code. Drupal 4.7 has bits of Ajax build in ready to make the task easier.

petermoulding.com/web_architect

In my case I guess search is

wickus - May 23, 2006 - 14:15

In my case I guess search is running you also will find some stuff stored in the database search table, but after 20% and 155 pages left occurs this server script error (500). I run an update of 4.7 because before I had 4.7 beta 5 but unfortunately the mistake still comes up.
Can it be that there is a script error in one of my pages, interfering the run of cron and if yes any idea, how I can find it out or saying it the other way how can I find out which is the next indexed page which will cause this error?

Maybe I should add this error is no php error, so I can't provide you with any error line. Seem to be an error like you get when the server times out but it's no timeout because it comes up after 2 seconds

---
Join the virtual march to stop global warming.
http://www.stopglobalwarming.org/marchers/?142067

Cronline

peterx - June 20, 2006 - 08:08

I made a start on Cronline, the online cron. It is easier to see what is happening and control execution with Cronline. My current version does not use Ajax or have an automatic repeat or make a great espresso.

If someone wants to use Cronline beta 0.0001 for testing search or other cronable activities then send me a note, preferably of a large denomination or visit http://drupal.org/node/65282.

petermoulding.com/web_architect

I´ve setted the cron,a nd

Rosamunda - July 1, 2006 - 02:41

I´ve setted the cron,a nd activate it manually mysite.com/cron.php
Wen I enter the admin/search area it says that the site has been indexed 16%.
Then I tell to do it again, and then appears that the site has been indexed 0%
I run the cron.php again and then the site seems to locate several stuff in the search process (not all the stuff), but the indexed pages are again in 0%...!

Am I doing something wrong here?

Thanks in advance guys!

Rosamunda

Have you tried ...?

hip - July 5, 2006 - 19:03

Hi (again) ;-)

I solved my problem a while ago. Have you tried the following:
http://drupal.org/node/65093#comment-128359
or any combination of its steps?

Hope it helps,
hip

 
 

Drupal is a registered trademark of Dries Buytaert.