Quote:
Originally Posted by UK Jimbo
Is the cronjob that's running the indexer creating any output?
Do you see any output if you run the indexer from the command line?
Can you copy/paste the command line you're using along with any output back here?
|
Here is the command line I use (within cron):
Code:
/usr/home/xxxx/sphinx/bin/indexer --config /usr/home/xxxx/sphinx/bin/sphinx_rr.conf --rotate postdelta threaddelta
I just ran it with this output:
Code:
Sphinx 0.9.8-rc2 (r1234)
Copyright (c) 2001-2008, Andrew Aksyonoff
using config file '/usr/home/xxxx/sphinx/bin/sphinx_rr.conf'...
indexing index 'postdelta'...
collected 10 docs, 0.0 MB
collected 10903 attr values
sorted 0.0 Mvalues, 100.0% done
sorted 0.0 Mhits, 100.0% done
total 10 docs, 2932 bytes
total 0.019 sec, 152923.38 bytes/sec, 521.57 docs/sec
indexing index 'threaddelta'...
collected 2 docs, 0.0 MB
collected 100 attr values
sorted 0.0 Mvalues, 100.0% done
sorted 0.0 Mhits, 100.0% done
total 2 docs, 40 bytes
total 0.010 sec, 4000.00 bytes/sec, 200.00 docs/sec
rotating indices: succesfully sent SIGHUP to searchd (pid=605).
It's frustrating because it is an intermittent error--I kept trying to reproduce it but had no luck.
The output looks OK. But, it's updating the threaddelta.new.* files, not the threaddelta.* files (which remain at zero bytes, dated 5/29/09).
It's not a huge deal, since I can dump and regenerate all the indexes, but I just don't want this to happen if we put this on our "production" forum, and was curious to know how it happened.