# Invalid CRI error (Filebeat 7.17 + docker)

**URL:** <https://discuss.elastic.co/t/invalid-cri-error-filebeat-7-17-docker/340930>\
**Category:** Beats\
**Tags:** docker, filebeat\
**Created:** [August 16, 2023, 1:57pm UTC](https://discuss.elastic.co/t/invalid-cri-error-filebeat-7-17-docker/340930 "2023-08-16T13:57:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![111238](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/111238/32/57619_2.png) [@111238](https://discuss.elastic.co/u/111238)\
**Post date:** [August 16, 2023, 1:57pm UTC](https://discuss.elastic.co/t/invalid-cri-error-filebeat-7-17-docker/340930/1 "2023-08-16T13:57:17Z")

</div>

Hi there!

We have a weird problem when Filebeat gets stuck on partial message in Container logs.  
Parse line error: invalid CRI log format

```auto
{"level":"error","timestamp":"2023-08-03T11:55:49.674Z","logger":"reader_docker_json","caller":"readjson/docker_json.go:231","message":"Parse line error: parsing CRI timestamp: parsing time \"\\x06stdout\\x10\\xce\\xde\\xcf\\x9c\\xba\\xac\\xf7\\xbb\\x17\\x1a\\x1fRefresh\" as \"2006-01-02T15:04:05.999999999Z07:00\": cannot parse \"\\x06stdout\\x10\\xce\\xde\\xcf\\x9c\\xba\\xac\\xf7\\xbb\\x17\\x1a\\x1fRefresh\" as \"2006\""}
{"level":"error","timestamp":"2023-08-03T11:55:49.674Z","logger":"reader_docker_json","caller":"readjson/docker_json.go:231","message":"Parse line error: invalid CRI log format"}
{"level":"error","timestamp":"2023-08-03T11:55:49.674Z","logger":"reader_docker_json","caller":"readjson/docker_json.go:231","message":"Parse line error: invalid CRI log format"}
{"level":"error","timestamp":"2023-08-03T11:55:49.674Z","logger":"reader_docker_json","caller":"readjson/docker_json.go:231","message":"Parse line error: invalid CRI log format"}
{"level":"error","timestamp":"2023-08-03T11:55:49.674Z","logger":"reader_docker_json","caller":"readjson/docker_json.go:231","message":"Parse line error: invalid CRI log format"}
{"level":"error","timestamp":"2023-08-03T11:55:49.674Z","logger":"reader_docker_json","caller":"readjson/docker_json.go:231","message":"Parse line error: invalid CRI log format"}

```

As far as I know, that's still not resolved by Elastic.  
Maybe there is a workaround (to ignore such errors for example).  
It seems that logger just gets stuck on it and won't ingest other lines.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 13, 2023, 3:57pm UTC](https://discuss.elastic.co/t/invalid-cri-error-filebeat-7-17-docker/340930/2 "2023-09-13T15:57:45Z")

</div>

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