By azoho on

Hi
I have searched the Drupal site and persued the suggestions but no joy.

I am having trouble getting the search to build an index.
It is not my own server so I need to work with what it offers.

It is running on PHP 4.4.4 and MySQL 5.0.20a

It probably can run CRON from the control panel but I have installed POORMANSCRON so I can control from within the website anyway.

I have a huge amount of content that I have inputted. 50 documents consisting of 100 pages each document (they are video transcripts). So the search option is very necessary.

The Indexing throttle is set to 10, and the minimum word length is 5.
POORMANSCRON is set to run once every 60 mins

The logs show that CRON completes via POORMANSCRON fairly regularly, but the search index shows 0%. And no results come back when I try a search.

Anyone able to help? I am not Unix literate, but guess it is setup correctly and it is the sheer amount of words that is causing the problems?

Thanks

⋅ Categories: Drupal 4.7.x

Comments

azoho’s picture

azoho commented

Anyone has some thoughts on this? I have tried setting: ini_set('memory_limit', '64M'); in sites/default/settings.php and there doesn't seem to be any effect.

Indexing status is still showing after many days:

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

Each item has roughly 35000 words so I would understand it taking a long time to index, but to not show any progress after days?

vm’s picture

vm commented

what happens if you run cron manually ? www.yoursite.com/cron.php

trying the above may diagnose something wrong with poormans cron with in your configuration.

azoho’s picture

azoho commented

Thanks v.misunderstood,
I have tried running cron.php manually a few times and I get a blank page. The logs say that cron has completed and the search index is staying at 0%

Vaughan’s picture

Vaughan commented

I am having a similar problem. I have a site that has indexed 100% in the search settings, and a sub-site on the same server (in a sub-folder) that has indexed 0%, I have installed PoorMansCron and that has run a number of times with no effect.

I have also tried the www.domain.com/cron.php but simply get a blank page with no errors or confirmation.

The data is mainly a directory, and we are currently unable to search the entries other than the start of the name (or the full name, but not part-way through)

Any help would be greatly appreciated.

Vaughan Harris

vm’s picture

vm commented

cron wont leave a message anywhere other the the logs. that being said a blank page is a good page when you run cron.php manually. the only thing I can think of after inspecting my set up, is that you have to tell drupal to index your site by click on the index submit button in administer -> settings -> search
this then tells drupal the next time cron is run its ok to ghead and index the site.
then cron runs, or is manually run and administer -> settings -> search will show site is 100% indexed. ithout clickin the index button, nothing is supposed to happen as drupal hasnt been told its ok to ghead and index.

hope this makes more sense.

step #1
administer -> settings -> search click re-index site
step #2 run cron.php

the search indexing isnt 100% done by cron.php without anyone manually telling drupall its ok to index the new content, cron wont.

azoho’s picture

azoho commented

I have clicked on Re-index button a few times, and run cron.php afterwards. Also have tried with POORMANSCRON running successfully in the background, and still index is staying 0%

Is my cron setup correctly or do I need to go into the SQL database and clear the search tables? My site was originally building the index okay but I clicked ReIndex as I thought I didn't have CRON setup correctly and it went back to 0% and is not increasing at all since.

vm’s picture

vm commented

its worth a shot to drop the already existing index.

I don't use poormans cron so I find it hard to comment on how it works, I set up cron jobs right on my server.

azoho’s picture

azoho commented

I tried clearing search_index and search_total tables, not dropping them, and clicked reindex site.. no luck still, index stays at 0% 129 items left

10 items per cron run, 5 character words minimum.

I have cron running every hour through webcron.org and the logs show cron successfully completes.

The search_index is 827,392 Bytes in size, and increases with each cron run about 100 Bytes each time.

Should I drop the tables and then try reindex site option? What would dropping the table do?

I really need to get this working as I have a lot of large documents on my site.