On Wed, 11 Jan 2017 15:17:53 -0500
Fran├žois Meehan <fmee...@vuwall.com> wrote:
> We are using RT 4.2.12. We noticed that the indexation stopped working.
> When trying to run the indexer manually, I would get:
> 
> [11238] [Wed Jan 11 19:53:56 2017] [warning]: DBD::mysql::st execute
> failed: MySQL server has gone away at /opt/rt4/sbin/rt-fulltext-indexer
> line 216. (/opt/rt4/sbin/rt-fulltext-indexer:216)
> [11238] [Wed Jan 11 19:53:56 2017] [warning]: DBD::mysql::st execute
> failed: MySQL server has gone away at /opt/rt4/sbin/rt-fulltext-indexer
> line 222. (/opt/rt4/sbin/rt-fulltext-indexer:222)
> [11238] [Wed Jan 11 19:53:56 2017] [critical]: Attachment 32267 cannot be
> indexed: MySQL server has gone away at /opt/rt4/sbin/rt-fulltext-indexer
> line 254. (/opt/rt4/sbin/../lib/RT.pm:389)
> Attachment 32267 cannot be indexed: MySQL server has gone away at
> /opt/rt4/sbin/rt-fulltext-indexer line 254.

This is likely due to a too-low `max_allowed_packet` in your MySQL
configuration.  Try bumping it higher and re-running the indexer.
 - Alex

Reply via email to