Fixing Fulltext Indexing in Request Tracker RT

If you have Fulltext search enabled and users start reporting that the queries are not retrieving the expected results, you might want to perform a full reindex of it. Follow the steps below to fix the fulltext indexing.

Step 1: Disable Fulltext-Indexer Cron Job

Temporarily disable the fulltext-indexer cron job to prevent any interference during the re-indexing process.

Step 2: Disable Fulltext Search in RT Configuration

Temporarily disable fulltext search in your RT configuration to avoid conflicts while reindexing.

Step 3: Restart Web Server

Restart your web server to apply the changes made in the RT configuration.

Step 4: Partially Re-enable Fulltext Search

Partially re-enable fulltext search in your RT configuration. Set the "Enable" option to 1, but set "Indexed" to 0.

    Set(%FullTextSearch,
        Enable  => 1,
        Indexed => 0,
    );

Execute the following command in a tmux or screen session because the reindexing process may take a considerable amount of time:

$RTHOME/sbin/rt-setup-fulltext-index

The command will prompt you with various options. If the defaults are suitable for your needs, you can simply press Enter for each option. Note that rt-setup-fulltext-index will drop the existing index information and recreate it. By default, it will also index all existing data, which may take a while.

Step 6: Completely Re-enable Fulltext Search

Fully re-enable fulltext search in your RT configuration.

Step 7: Restart Web Server

Restart your web server once again to ensure the changes take effect.

Step 8: Re-enable Fulltext-Indexer Cron Job

Finally, re-enable the fulltext-indexer cron job to resume regular indexing.

By following these steps, you should be able to fix the fulltext indexing issue in your Request Tracker software.

Remember to test the search functionality after completing the steps to ensure that the indexing is working correctly.