# Error - commit is for a block we do not know about **URL:** \ **Category:** Validation\ **Created:** [November 7, 2022, 10:59am UTC](https://forum.cosmos.network/t/error-commit-is-for-a-block-we-do-not-know-about/8153 "2022-11-07T10:59:27Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![DB\_VLD22](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/db_vld22/32/2950_2.png) [@DB\_VLD22](https://forum.cosmos.network/u/DB_VLD22)\ **Post date:** [November 7, 2022, 10:59am UTC](https://forum.cosmos.network/t/error-commit-is-for-a-block-we-do-not-know-about/8153/1 "2022-11-07T10:59:27Z")
Hi all, We are getting the following error in the logs of our validator: ```auto 10:21AM INF commit is for a block we do not know about; set ProposalBlock=nil commit=C109A5A72B5520E99824A3E274C74EE25E0A304E8DCC0BCCF15FDF9C115CDF3B commit_round=0 height=12750921 module=consensus proposal= 10:26AM INF commit is for a block we do not know about; set ProposalBlock=nil commit=A508BDDD2D92A5D734D9A242A210BA778FF4ECA5C062D6FBAA6DCEA98217E47E commit_round=0 height=12750972 module=consensus proposal= ``` It appears after we see a missed block in the explorer. Is this normal? Have you seen this in your logs? Any insights or pointers will be greatly appreciated. Thanks! ---
**Author:** ![serejandmyself](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/serejandmyself/32/8086_2.png) [@serejandmyself](https://forum.cosmos.network/u/serejandmyself)\ **Post date:** [November 23, 2022, 1:34pm UTC](https://forum.cosmos.network/t/error-commit-is-for-a-block-we-do-not-know-about/8153/2 "2022-11-23T13:34:57Z")
Have you tried dropping this error to the Discord? There is a lot of cosmos devs there ---
**Author:** ![DB\_VLD22](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/db_vld22/32/2950_2.png) [@DB\_VLD22](https://forum.cosmos.network/u/DB_VLD22)\ **Post date:** [November 23, 2022, 2:17pm UTC](https://forum.cosmos.network/t/error-commit-is-for-a-block-we-do-not-know-about/8153/3 "2022-11-23T14:17:16Z")
Yes with no result. Thanks for suggestion though ---
**Author:** ![serejandmyself](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/serejandmyself/32/8086_2.png) [@serejandmyself](https://forum.cosmos.network/u/serejandmyself)\ **Post date:** [November 23, 2022, 2:42pm UTC](https://forum.cosmos.network/t/error-commit-is-for-a-block-we-do-not-know-about/8153/4 "2022-11-23T14:42:41Z")
Showed it to a devOps. They didnt say much. Just that its hard to say =) Possibly because it missed the block, the node takes time to catch up with the set so to speak and after it resynchs it spits this out. Maybe the node is too heavy, maybe the storage is too slow, etc. Wild guesses here ---
**Author:** ![DB\_VLD22](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/db_vld22/32/2950_2.png) [@DB\_VLD22](https://forum.cosmos.network/u/DB_VLD22)\ **Post date:** [November 23, 2022, 3:42pm UTC](https://forum.cosmos.network/t/error-commit-is-for-a-block-we-do-not-know-about/8153/5 "2022-11-23T15:42:09Z")
Yeah, the error is too generic. Our validator is on-premises with enterprise grade hardware and nvme disks and has plenty of resources. Sentries are in AWS. Network connectivity also looks healthy. So, we are stuck… ---
**Author:** ![serejandmyself](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/serejandmyself/32/8086_2.png) [@serejandmyself](https://forum.cosmos.network/u/serejandmyself)\ **Post date:** [November 23, 2022, 4:02pm UTC](https://forum.cosmos.network/t/error-commit-is-for-a-block-we-do-not-know-about/8153/6 "2022-11-23T16:02:05Z")
If you manage to crack it, let us know too please ---
**Author:** ![ironsf](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/ironsf/32/6379_2.png) [@ironsf](https://forum.cosmos.network/u/ironsf)\ **Post date:** [December 20, 2023, 10:59am UTC](https://forum.cosmos.network/t/error-commit-is-for-a-block-we-do-not-know-about/8153/7 "2023-12-20T10:59:50Z")
I also tryed toreduce missed blocks on my node. And setting peer\_gossip\_sleep\_duration to 2ms helped (I still see some missed blocks, but less than before) ---
**Author:** ![maanav](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/maanav/32/6429_2.png) [@maanav](https://forum.cosmos.network/u/maanav)\ **Post date:** [January 2, 2024, 10:44am UTC](https://forum.cosmos.network/t/error-commit-is-for-a-block-we-do-not-know-about/8153/8 "2024-01-02T10:44:29Z")
Hi, were you able to figure out how to solve this? Stuck on this issue too, I tried reducing `peer_gossip_sleep_duration` to 2ms but no luck yet ---
**Author:** ![jacobgadikian](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/jacobgadikian/32/6994_2.png) [@jacobgadikian](https://forum.cosmos.network/u/jacobgadikian)\ **Post date:** [January 4, 2024, 12:13pm UTC](https://forum.cosmos.network/t/error-commit-is-for-a-block-we-do-not-know-about/8153/9 "2024-01-04T12:13:38Z")
Hi, that error is a little bit normal. You will frequently see that error when your node is almost synced. Is that where you are seeing it?