Loading...
 
Documentation

Documentation


Can't rebuild the search index

posts: 4 Colombia

Good afternoon,

I have a problem repairing the search index of a Tikiwiki version 17.2.

I have tried to repair the search index with the following command:

php -dmemory_limit=15G -dmax_execution_time=1000 /opt/bitnami/apps/tiki/htdocs/console.php index:rebuild --log

And I get this error:

2023-01-05T07:10:01-08:00 ERR (3): Indexing failed while processing “155” (type forum post) with the error “Could not perform index modification: Data too long for column ‘contents’ at row 1” No value assigned bytes

2023-01-05T07:10:01-08:00 INFO (6): addDocument forum post 48 {"memoryUsage":136202608} No value assigned bytes

2023-01-05T07:10:03-08:00 ERR (3): Indexing failed while processing “48” (type forum post) with the error “Could not perform index modification: Data too long for column ‘contents’ at row 1” No value assigned bytes

2023-01-05T07:10:03-08:00 INFO (6): addDocument forum post 127 {"memoryUsage":136226576} No value assigned bytes

2023-01-05T07:10:05-08:00 ERR (3): Indexing failed while processing “127” (type forum post) with the error “Could not perform index modification: Data too long for column ‘contents’ at row 1” No value assigned bytes

2023-01-05T07:10:05-08:00 INFO (6): addDocument forum post 26 {"memoryUsage":136239656} No value assigned bytes

2023-01-05T07:10:06-08:00 ERR (3): Indexing failed while processing “26” (type forum post) with the error “Could not perform index modification: Data too long for column ‘contents’ at row 1” No value assigned bytes

2023-01-05T07:10:06-08:00 INFO (6): addDocument forum post 33 {"memoryUsage":136264208} No value assigned bytes

2023-01-05T07:10:08-08:00 ERR (3): Indexing failed while processing “33” (type forum post) with the error “Could not perform index modification: Data too long for column ‘contents’ at row 1” No value assigned bytes

2023-01-05T07:10:08-08:00 INFO (6): addDocument forum post 32 {"memoryUsage":136265312} No value assigned bytes

2023-01-05T07:10:09-08:00 ERR (3): Indexing failed while processing “32” (type forum post) with the error “Could not perform index modification: Data too long for column ‘contents’ at row 1” No value assigned bytes

2023-01-05T07:10:09-08:00 INFO (6): addDocument forum post 27 {"memoryUsage":136266416} No value assigned bytes

2023-01-05T07:10:11-08:00 ERR (3): Indexing failed while processing “27” (type forum post) with the error “Could not perform index modification: Data too long for column ‘contents’ at row 1” No value assigned bytes

2023-01-05T07:10:11-08:00 INFO (6): addDocument forum post 310 {"memoryUsage":136267520} No value assigned bytes

2023-01-05T07:10:13-08:00 ERR (3): Indexing failed while processing “310” (type forum post) with the error “Could not perform index modification: Data too long for column ‘contents’ at row 1” No value assigned bytes

2023-01-05T07:10:13-08:00 INFO (6): addDocument forum post 51 {"memoryUsage":136269488} No value assigned bytes

2023-01-05T07:10:14-08:00 ERR (3): Indexing failed while processing “51” (type forum post) with the error “Could not perform index modification: Data too long for column ‘contents’ at row 1” No value assigned bytes

2023-01-05T07:10:14-08:00 INFO (6): addDocument forum post 41 {"memoryUsage":136270592} No value assigned bytes

2023-01-05T07:10:16-08:00 ERR (3): Indexing failed while processing “41” (type forum post) with the error “Could not perform index modification: Data too long for column ‘contents’ at row 1” No value assigned bytes

2023-01-05T07:10:16-08:00 INFO (6): addDocument forum post 47 {"memoryUsage":136272016} No value assigned bytes

2023-01-05T07:10:18-08:00 ERR (3): Indexing failed while processing “47” (type forum post) with the error “Could not perform index modification: Data too long for column ‘contents’ at row 1” No value assigned bytes

And so on...

I then tried to repair the tables directly in MYSQL:

mysqlcheck user root password repair databases tiki

But it only repaired the indexes (MyISAM search engine), not the rest of the tables (InnoDB search engine) and I had to change the search engine from InnoDB to MyISAM to be able to repair the tables. Finally I repair them but the build index command still does not work.

I have been thinking that maybe I could delete the information of the tables that are failing in the index rebuild but I really don't know what they are.

I have run out of ideas, not that I am an expert either, to be honest. I don't know if you can help me.

Thank you very much.

There are no comments at this time.

Upcoming Events

1)  18 Apr 2024 14:00 GMT-0000
Tiki Roundtable Meeting
2)  16 May 2024 14:00 GMT-0000
Tiki Roundtable Meeting
3)  20 Jun 2024 14:00 GMT-0000
Tiki Roundtable Meeting
4)  18 Jul 2024 14:00 GMT-0000
Tiki Roundtable Meeting
5)  15 Aug 2024 14:00 GMT-0000
Tiki Roundtable Meeting
6)  19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting
7) 
Tiki birthday
8)  17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting
9)  21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting
10)  19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting