Difference between revisions of "Failed to flush chunk"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
{"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} | ||
| + | status":400,"error":{"type":"mapper_parsing_exception","reason":"object mapping for [kubernetes.labels.app] tried to parse field [app] as object, [[but found a concrete value]]"}}} | ||
Revision as of 14:47, 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}
status":400,"error":{"type":"mapper_parsing_exception","reason":"object mapping for [kubernetes.labels.app] tried to parse field [app] as object, but found a concrete value"}}}
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:
