Difference between revisions of "Failed to flush chunk"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
[[mapper_parsing_exception]] | [[mapper_parsing_exception]] | ||
| − | {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"object mapping for [Data.PASSED] tried to parse field [null] as object, but found a concrete value"}],"type":"mapper_parsing_exception","reason":"object mapping for [Data.PASSED] tried to parse field [null] as object, but found a concrete value"},"status":400} | + | {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"object mapping for [Data.PASSED] tried to parse field [null] as object, but found a concrete value"}],"type":"mapper_parsing_exception","reason":"object mapping for [Data.PASSED] [[tried to parse field]] [null] as object, [[but found a concrete value]]"},"status":400} |
Revision as of 14:45, 27 December 2022
Activate Trace_Error to understand the issue:
[OUTPUT] .... Trace_Error on
mapper_parsing_exception
{"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"object mapping for [Data.PASSED] tried to parse field [null] as object, but found a concrete value"}],"type":"mapper_parsing_exception","reason":"object mapping for [Data.PASSED] tried to parse field [null] as object, but found a concrete value"},"status":400}
Buffer_Size False
.flb
tail.0 paused (mem buf overlimit) Backpressure [error] [upstream] connection #... timed out after ... still running on route Retry_Limit
See also
Advertising:
