auditor search is empty

Issue #763 invalid
Uwe created an issue

Hi there, i have permanent Problems with indexing new mails for auditor.

i have a fresh install piler + spinxsearch on a copy of my debian for first test OS = Debian 7 Spinxsearch = 2.2.11 Piler = 1.2.0 b 952 in /etc/spinxsearch start=no

in admin statusmonitor i see round 52.000 Mails (pilerimport -i ...) the auditor sees them all in an search but If i do an indexer --all --rotate the auditor have 0 items in all search result i need to reindex -a

so i tried a script without --rotate

service rc.searchd stop indexer --all service rc.searchd start

This worked fine yesterday but today i get also 0 items as auditor i always have to reindex -a and this takes a real long time... i cannot find the reason. Is this a bug or i am doing something wrong ?

a second problem is about one config-file on 2 locations

indexer --all using config file '/etc/sphinxsearch/sphinx.conf'...

service rc.searchd start using config file '/usr/local/etc/piler/sphinx.conf'...

i made both files the same (copy) but dont know why they use two different locations

On piler-install i chosed the original location /usr/local/etc/piler/sphinx.conf

Comments (3)

  1. Janos SUTO repo owner

    Yes, you are doing it very wrong, and keep shooting yourself on the foot. I don't fully understand why on Earth you run indexer --all at all. You should NOT run it, because it's meant to run once in a lifetime: at installation time. Indexer --all resets, empties the sphinx db. So this is what you are doing: reset the archive, reindex, reset again, reindex again, reset again, ...

    Regarding the 2 sphinx configs: debian/ubuntu users keep stumbling on the stupid debian behaviour that it runs indexer --all every day which practically destroys the sphinx indices. I've also decided that it makes sense to keep all piler related configs at one place. So you did it wrong when you copied the piler shipped sphinx config to the sphinx package config file.

    So there's no bug at all, merely some confusion...

  2. Log in to comment