Hello,
I recently inherited an old RT 4.0.23 installation and upgraded it to 4.4.1 with some problems on the route that the forum and google mostly sorted out.
However, when I dig into the fulltext index creation, I am unable to create a working index.
It seems to me that it indexes through all tickets until it finds a ticket where it catches an exception and does not continue forward.
Output from the rt-setup-fulltext-index:
[critical]: UTF-32BE:Unicode character 8926ffff is illegal at /usr/lib/x86_64-linux-gnu/perl/5.24/Encode.pm line 197, line 755. (/usr/share/request-tracker4/lib/RT.pm:394)
UTF-32BE:Unicode character 8926ffff is illegal at /usr/lib/x86_64-linux-gnu/perl/5.24/Encode.pm line 197, line 755.
Going to run the following in the DB:
CREATE INDEX ContentIndex_idx ON Attachments USING gin(ContentIndex)
Output from rt.log (debug):
[debug]: Encode::Guess guessed encoding: UTF-32BE (/usr/share/request-tracker4/lib/RT/I18N.pm:569)
[critical]: UTF-32BE:Unicode character 8926ffff is illegal at /usr/lib/x86_64-linux-gnu/perl/5.24/Encode.pm line 197, line 755. (/usr/share/request-tracker4/lib/RT.pm:394)
As the database is pretty old and contains about 130’000 tickets with attachments, I wonder if someone could point me in the right direction of how to find the ticket or data in the database that triggers this exception? " Line 755" is a bit hard to look for 
Debian Stretch
Postgresql 9.6
RT 4.4.1-3+deb9u2
Best regards,