[rt-users] supplying database credentials to rt-fulltext-indexer

[Alex Hall]

FTS is enabled and working, but it seems to be working only on tickets that
were set up when the setup tool was run. According to the docs
(rt4/docs/full_text_indexing.pod):

To keep the index up-to-date, you will need to run:

    /opt/rt4/sbin/rt-fulltext-indexer

...at regular intervals.  By default, this will only tokenize up to 200
tickets at a time; you can adjust this upwards by passing C<--limit
500>.  Larger batch sizes will take longer and consume more memory.


What this file never says is how to tell the indexer tool how to connect to
the database. It clearly isn't pulling from the RT configuration, nor from
/home/www-data/rtrc.

On Fri, Dec 9, 2016 at 5:12 PM, Landon Stewart <lstewart at internap.com>
wrote:

> On Dec 9, 2016, at 2:06 PM, Alex Hall <ahall at autodist.com> wrote:
>
>
> I thought the tool I had to run periodically was /opt/rt4/sbin/rt-fulltext-indexer.
> That's the one guides tell me to run; the setup tool seems to be the
> initial database adjustment tool, but once it runs once, I thought I had to
> run the indexer every so often. The indexer is the tool that refuses
> database credentials. Unless the guides on this are wrong, and the setup
> one is the one I have to run with cron?
>
>
> I haven't enabled Full Text searching in RT before but I have set it up in
> MySQL for other uses.  From my experiences with MySQL I believe you setup
> the indexes once only with the setup tool for RT and once they are setup
> there's no need to 're-index' anything regularly with any crontab or
> anything.
>
> Above all though - do this on a copy of your RT installation/database and
> make sure it works before you potentially interrupt the flow of business in
> production.
>
> --
> Landon Stewart
> Lead Analyst - Abuse and Security Management
> INTERNAP ®
> 📧 lstewart at internap.com
> 🌍 www.internap.com
>
>


-- 
Alex Hall
Automatic Distributors, IT department
ahall at autodist.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20161209/eb8d844d/attachment.htm>