Getting ERROR Message in graylog-server log file


(Tafsir) #1

Hi All

Huge backlog on graylog data nodes. While seeing the graylog-server logs I found some messages but I can’t able to understand it. Please help me to fix this.

Graylog-Version -2.4.6
Elasticsearch Version - 5.6

2018-09-13T21:35:50.571Z ERROR [Messages] Failed to index [2] messages. Please check the index error log in your web interface for the reason. Error: One or more of the items in the Bulk request failed, check BulkResult.getItems() for more information.
2018-09-13T21:35:51.320Z WARN  [Messages] Failed to index message: index=<graylog_523> id=<e29ef6d6-b79c-11e8-a103-1244b83420c4> error=<{"type":"illegal_argument_exception","reason":"Document contains at least one immense term in field=\"reconciliation_log\" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped.  Please correct the analyzer to not produce such terms.  The prefix of the first immense term is: '[123, 34, 120, 95, 114, 101, 113, 117, 101, 115, 116, 95, 105, 100, 34, 58, 110, 117, 108, 108, 44, 34, 100, 101, 97, 108, 101, 114, 95, 105]...', original message: bytes can be at most 32766 in length; got 61511","caused_by":{"type":"max_bytes_length_exceeded_exception","reason":"max_bytes_length_exceeded_exception: bytes can be at most 32766 in length; got 61511"}}>

Quick response will be appreciated.

Thanks


(Jan Doberstein) #2

he @Tafsir_Alam

the field reconciliation_log is longer than the max length 32766 that is why the error happens. You should shorten the field or have ignore above in your elasticsearch template for that field.


(Tafsir) #3

Hi @jan

How can we identify that I have ignored above Elasticsearch template for that field.

Thanks in advance.


(Jan Doberstein) #4

your custom mapping would include that.

http://docs.graylog.org/en/2.4/pages/configuration/elasticsearch.html#custom-index-mappings


(system) #5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.