[rt-users] fulltext index update failure (RT 4.2.12)

Jim Brandt jbrandt at bestpractical.com
Fri Jan 22 10:44:48 EST 2016


How much free disk space do you have? You can often get the "server gone 
away" message when MySQL runs out of disk space.

On 1/22/16 5:22 AM, elifree at free.fr wrote:
> Good morning,
>
> This is a follow-up of my problem :
>
> This morning I decided to shred the attachment 602620.
> But after execution of rt-fulltext-indexer it fails again at the next 
> number of attachment : 602621 !
>
> So this was clearly not the solution. But now I have not idea of what 
> is the problem.
>
> Any clue or help is greatly appreciated.
> Thanks and have a good day,
> Elisabeth
>
> ------------------------------------------------------------------------
>
>     *De: *elifree at free.fr
>     *À: *rt-users at lists.bestpractical.com
>     *Envoyé: *Jeudi 21 Janvier 2016 15:57:08
>     *Objet: *fulltext index update failure (RT 4.2.12)
>
>     Hello,
>
>     We have juste upgraded our RT this morning to version 4.2.12 (from
>     4.2.6) and MySQL to 5.6 (from 5.5) in order to implement the full
>     text indexing.
>
>     It works, but when running /appli/rt4/sbin/rt-fulltext-indexer to
>     update the table AttachmentsIndex, it stops with an error :
>
>     extract from the log file :
>
>     Jan 21 14:50:01 helpdesk.inria.fr CRON[9668]: (root) CMD
>     (/appli/rt4/sbin/rt-fulltext-indexer --quiet)
>
>     Jan 21 14:50:03 helpdesk.inria.fr RT: [9669] DBD::mysql::st
>     execute failed: MySQL server has gone away at
>     /appli/rt4/sbin/rt-fulltext-indexer line 216.
>     Jan 21 14:50:03 helpdesk.inria.fr RT: [9669] DBD::mysql::st
>     execute failed: MySQL server has gone away at
>     /appli/rt4/sbin/rt-fulltext-indexer line 222.
>     Jan 21 14:50:03 helpdesk.inria.fr RT: [9669] Attachment 602620
>     cannot be indexed: MySQL server has gone away at
>     /appli/rt4/sbin/rt-fulltext-indexer line 254.
>
>     The result is that new attachments are not indexed.
>
>     I don't know what to do : should I just shred the attachment
>     602620 ? Is this at risk ?
>
>     Thanks a lot for your help,
>     Elisabeth
>
>
>
>
>
>
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20160122/7ebd616a/attachment.html>


More information about the rt-users mailing list