# pt-query-digest: MySQLProtocolParser caused an error

**URL:** <https://forums.percona.com/t/pt-query-digest-mysqlprotocolparser-caused-an-error/7367>\
**Category:** Percona Toolkit\
**Created:** [January 6, 2020, 6:02am UTC](https://forums.percona.com/t/pt-query-digest-mysqlprotocolparser-caused-an-error/7367 "2020-01-06T06:02:34Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![usafbeach](https://avatars.discourse-cdn.com/v4/letter/u/848f3c/32.png) [@usafbeach](https://forums.percona.com/u/usafbeach)\
**Post date:** [January 9, 2020, 4:49am UTC](https://forums.percona.com/t/pt-query-digest-mysqlprotocolparser-caused-an-error/7367/4 "2020-01-09T04:49:01Z")

</div>

I am having this exact same problem. Interestingly, if I change the date on my computer’s clock back to 2019 and collect a tcpdump, pt-query-digest has no problem parsing that file. But any file collected now with the correct date gives errors like tvlooy posted above. I can’t seem to figure out why a new year might be throwing things off though.

I have attached a 7z archive with two pcaps, one from last year (working), and one from today (not working). Remove the .txt extension.

---

_[View the full topic](https://forums.percona.com/t/pt-query-digest-mysqlprotocolparser-caused-an-error/7367)._