I activated the full text indexing under Ubuntu 16.04 (request-tracker4
4.2.12-5) and (mysql-server 5.7.13-0ubuntu0.16.04.2). Both the initial
indexing and subsequent calls to rt-fulltext-indexer have the same error:
----- Begin quote -----
[3159] [Fri Aug 26 03:03:08 2016] [warning]: DBD::mysql::st execute failed: MySQL server has gone away at /usr/sbin/rt-fulltext-indexer line 216. (/usr/sbin/rt-fulltext-indexer:216)
[3159] [Fri Aug 26 03:03:08 2016] [warning]: DBD::mysql::st execute failed: MySQL server has gone away at /usr/sbin/rt-fulltext-indexer line 222. (/usr/sbin/rt-fulltext-indexer:222)
[3159] [Fri Aug 26 03:03:08 2016] [critical]: Attachment 125007 cannot be indexed: MySQL server has gone away at /usr/sbin/rt-fulltext-indexer line 254. (/usr/share/request-tracker4/lib/RT.pm:389)
Attachment 125007 cannot be indexed: MySQL server has gone away at /usr/sbin/rt-fulltext-indexer line 254.
----- End quote -----
I saw a similar email back in January and one of the comments asked about
disk space. The disk has plenty of space (only 10% full) and systemctl status mysql shows the mysql process is still running. Entering RT
and doing searches works too, so the error is misleading or wrong.
how long after you start do you get that error?> On Aug 25, 2016, at 9:49 PM, Omen Wild omen@ucdavis.edu wrote:
I activated the full text indexing under Ubuntu 16.04 (request-tracker4
4.2.12-5) and (mysql-server 5.7.13-0ubuntu0.16.04.2). Both the initial
indexing and subsequent calls to rt-fulltext-indexer have the same error:
----- Begin quote -----
[3159] [Fri Aug 26 03:03:08 2016] [warning]: DBD::mysql::st execute failed: MySQL server has gone away at /usr/sbin/rt-fulltext-indexer line 216. (/usr/sbin/rt-fulltext-indexer:216)
[3159] [Fri Aug 26 03:03:08 2016] [warning]: DBD::mysql::st execute failed: MySQL server has gone away at /usr/sbin/rt-fulltext-indexer line 222. (/usr/sbin/rt-fulltext-indexer:222)
[3159] [Fri Aug 26 03:03:08 2016] [critical]: Attachment 125007 cannot be indexed: MySQL server has gone away at /usr/sbin/rt-fulltext-indexer line 254. (/usr/share/request-tracker4/lib/RT.pm:389)
Attachment 125007 cannot be indexed: MySQL server has gone away at /usr/sbin/rt-fulltext-indexer line 254.
----- End quote -----
I saw a similar email back in January and one of the comments asked about
disk space. The disk has plenty of space (only 10% full) and systemctl status mysql shows the mysql process is still running. Entering RT
and doing searches works too, so the error is misleading or wrong.
I activated the full text indexing under Ubuntu 16.04 (request-tracker4
4.2.12-5) and (mysql-server 5.7.13-0ubuntu0.16.04.2). Both the initial
indexing and subsequent calls to rt-fulltext-indexer have the same error:
----- Begin quote -----
[3159] [Fri Aug 26 03:03:08 2016] [warning]: DBD::mysql::st execute failed: MySQL server has gone away
That error is almost always that RT tried to do an insert or update
of data larger that the MySQL server’s max_allowed_packet. Try
increasing that setting, restarting MySQL, and indexing again.
Quoting Alex Vandiver alex@chmrr.net on Thu, Aug 25 22:39:
I activated the full text indexing under Ubuntu 16.04 (request-tracker4
4.2.12-5) and (mysql-server 5.7.13-0ubuntu0.16.04.2). Both the initial
indexing and subsequent calls to rt-fulltext-indexer have the same error:
----- Begin quote -----
[3159] [Fri Aug 26 03:03:08 2016] [warning]: DBD::mysql::st execute failed: MySQL server has gone away
That error is almost always that RT tried to do an insert or update
of data larger that the MySQL server’s max_allowed_packet. Try
increasing that setting, restarting MySQL, and indexing again.
And indeed that was the problem. Bumped it from 16M to 64M and all is
well. And now that I check the MySQL error logs I see it complaining
there. Thanks for the tip!