Skip to content
This repository has been archived by the owner on Apr 19, 2022. It is now read-only.

Getting weird 'headers' messages when syncing over network #58

Closed
svyatonik opened this issue Mar 20, 2019 · 1 comment · Fixed by #61
Closed

Getting weird 'headers' messages when syncing over network #58

svyatonik opened this issue Mar 20, 2019 · 1 comment · Fixed by #61
Assignees
@svyatonik
Labels
F2-bug 🐞 M4-core ⛓

Comments

@svyatonik
Copy link
Contributor

I'm getting something like that:

2019-03-20 14:17:13  WARN sync Previous header of the first header from peer#7 `headers` message is unknown. First: 0003eb875fc001da4a57de8465f68a2730c24ca086f37c6f14780ac9ee3ea3d5. Previous: 00052461a5006c2e3b74ce48992a08695607912d5604c3eb8da25749b0900444
2019-03-20 14:17:13  WARN sync Previous header of the first header from peer#8 `headers` message is unknown. First: 0003eb875fc001da4a57de8465f68a2730c24ca086f37c6f14780ac9ee3ea3d5. Previous: 00052461a5006c2e3b74ce48992a08695607912d5604c3eb8da25749b0900444
2019-03-20 14:17:13  WARN sync Previous header of the first header from peer#7 `headers` message is unknown. First: 0003eb875fc001da4a57de8465f68a2730c24ca086f37c6f14780ac9ee3ea3d5. Previous: 00052461a5006c2e3b74ce48992a08695607912d5604c3eb8da25749b0900444
2019-03-20 14:17:14  WARN sync Previous header of the first header from peer#6 `headers` message is unknown. First: 0003eb875fc001da4a57de8465f68a2730c24ca086f37c6f14780ac9ee3ea3d5. Previous: 00052461a5006c2e3b74ce48992a08695607912d5604c3eb8da25749b0900444
2019-03-20 14:17:14  WARN sync Previous header of the first header from peer#7 `headers` message is unknown. First: 0003eb875fc001da4a57de8465f68a2730c24ca086f37c6f14780ac9ee3ea3d5. Previous: 00052461a5006c2e3b74ce48992a08695607912d5604c3eb8da25749b0900444
2019-03-20 14:17:14  WARN sync Previous header of the first header from peer#7 `headers` message is unknown. First: 0003eb875fc001da4a57de8465f68a2730c24ca086f37c6f14780ac9ee3ea3d5. Previous: 00052461a5006c2e3b74ce48992a08695607912d5604c3eb8da25749b0900444
2019-03-20 14:17:14  WARN sync Previous header of the first header from peer#8 `headers` message is unknown. First: 0003eb875fc001da4a57de8465f68a2730c24ca086f37c6f14780ac9ee3ea3d5. Previous: 00052461a5006c2e3b74ce48992a08695607912d5604c3eb8da25749b0900444

too often, when trying to sync with the network. There's no block with this hash in Zcash, ZClassic or BTC.
@svyatonik svyatonik self-assigned this Mar 20, 2019
@NikVolf
Copy link
Contributor

NikVolf commented Mar 20, 2019

https://explorer.zel.cash/block/0003eb875fc001da4a57de8465f68a2730c24ca086f37c6f14780ac9ee3ea3d5

but there is zel.cash block? :)

@svyatonik svyatonik mentioned this issue Mar 21, 2019
Merged
@svyatonik svyatonik mentioned this issue Apr 17, 2019
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@svyatonik svyatonik

Labels
F2-bug 🐞 M4-core ⛓
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Penalize peer when receiving unknown headers message paritytech/parity-zcash
2 participants
@svyatonik @NikVolf