Cannot index search
Hi all.
on my site, I cannot seem to build the search index. If I run cron (or set up a cron job), it times out. (If I disable the search module, it succeeds.)
I have changed search settings to only index 10 nodes at a time (and gone as a hight as 5 letters minimum), but I consistently fail at node 3.
What is node 3? A forum topic with 126 pages of comments.
I also tried commandline (php -q cron.php) but this also ran out of memory and looking at the database, only the first two nodes are indexed.
I am on a VPS with 1and1 and the php memory limit is 32MB - I have tried searching for a way to increase this, but I doubt I can.
(ftr, I do not think this is not due to negligence - I imported the site from phpBB)
I have tried the reindex module, but it also gives an error. Poormanscron seems to freeze everything using 100% CPU but without actually adding anything to the search index.
I have searched the site and none of the other cases seems to be of help.
(Is there a way to partially index a node?)
Any ideas?
bump?
bump?
php error log; it may
php error log; it may indicate what is failing. other than memory, the thing that my installs trip on have been max_execution_time (time-out). try incrementing that up, get php.ini to load (restart the web server/instance?), verify that the setting took in phpinfo(), and try running cron again.
Any particular way to get
Any particular way to get the log? (I am on a VPS - do not know too much about these things yet)
The Drupal log says it times out. in common.inc, I tried changing the value of the ini_set to something higher (from 240 to 2400), but that made no difference. I think there is somewhere else which gives the max process time too. (php is not in safemode)
If I run php -q cron.php via SSH, it says:
(the VPS allocates a max of 32MB for php processes... no idea where to change this. I tried in the .htaccess file as I cannot find a php.ini but that did not work. The VPS is with 1and1.)
for the memory error, i
for the memory error, i think the doc page still applies: http://drupal.org/node/76156/. i do not know if this will help you if you are unable to allocate more memory. wonder if you ask nicely, maybe they could give you a temporary 'bump' in memory to get you past your issue, then revert. otherwise, i would seriously considering (temporarily) disabling as many modules that you safely get away with, chunk the indexes and run cron manually to reindex.
don't know how you might get to the log on your service, but it seems you have answered your question with the timeouts. if you are running out of memory though, the timeout is moot. max_execution and max_process are both in php.ini, or wherever your hosting service is setting it. sorry, can't help you with hosting configs; i build my own servers. maybe http://drupal.org/node/34022 can give you some hints.
good luck!
Thanks for those links.
Thanks for those links. Looking through them
Another question - Is it possible to run the indexing on another server (like my PC, where I can change both those things) and upload just the changes to the live server?
dunno
...but it is an interesting idea. backup, backup, backup, whatever you do!