Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

invalid network header #2920

Closed
suntzu93 opened this issue Nov 10, 2023 · 2 comments
Closed

invalid network header #2920

suntzu93 opened this issue Nov 10, 2023 · 2 comments
Labels
bug Something isn't working external Issues created by non node team members

Comments

@suntzu93
Copy link

Celestia Node version

v0.12.0

OS

20.04.6 LTS

Install tools

No response

Others

No response

Steps to reproduce it

My bridge node shows an error on every block

Expected result

No error

Actual result

I see error invalid network header on every block.

Relevant log output

2023-11-10T09:07:57.027Z        INFO    header/store    store/store.go:365      new head        {"height": 72213, "hash": "E2F508F103597BC5186F6FC1BD7F7D794449250F78FB73952242703B13A76DEE"}
2023-11-10T09:08:07.375Z        ERROR   header/sync     sync/sync_head.go:175   invalid network header  {"height_of_invalid": 72213, "hash_of_invalid": "E2F508F103597BC5186F6FC1BD7F7D794449250F78FB73952242703B13A76DEE", "height_of_subjective": 72213, "hash_of_subjective": "E2F508F103597BC5186F6FC1BD7F7D794449250F78FB73952242703B13A76DEE", "reason": "known header: '72213' <= current '72213'"}
2023-11-10T09:08:09.024Z        INFO    header/store    store/store.go:365      new head        {"height": 72214, "hash": "B70F80B86A2BF72AD5A550FF3593A8423674404231F092746358038DD95C56B0"}
2023-11-10T09:08:17.413Z        ERROR   header/sync     sync/sync_head.go:175   invalid network header  {"height_of_invalid": 72214, "hash_of_invalid": "B70F80B86A2BF72AD5A550FF3593A8423674404231F092746358038DD95C56B0", "height_of_subjective": 72214, "hash_of_subjective": "B70F80B86A2BF72AD5A550FF3593A8423674404231F092746358038DD95C56B0", "reason": "known header: '72214' <= current '72214'"}
2023-11-10T09:08:21.029Z        INFO    header/store    store/store.go:365      new head        {"height": 72215, "hash": "B2314310B52978D2B9EA98A770833C3FC1480F7948D050CEC386A2304EFD736C"}
2023-11-10T09:08:32.469Z        ERROR   header/sync     sync/sync_head.go:175   invalid network header  {"height_of_invalid": 72215, "hash_of_invalid": "B2314310B52978D2B9EA98A770833C3FC1480F7948D050CEC386A2304EFD736C", "height_of_subjective": 72215, "hash_of_subjective": "B2314310B52978D2B9EA98A770833C3FC1480F7948D050CEC386A2304EFD736C", "reason": "known header: '72215' <= current '72215'"}
2023-11-10T09:08:33.174Z        INFO    header/store    store/store.go:365      new head        {"height": 72216, "hash": "C9A78C8FC3B51EECF4202820D303C3A16C362AF3D1617B858764C906755CCECC"}
2023-11-10T09:08:42.518Z        ERROR   header/sync     sync/sync_head.go:175   invalid network header  {"height_of_invalid": 72216, "hash_of_invalid": "C9A78C8FC3B51EECF4202820D303C3A16C362AF3D1617B858764C906755CCECC", "height_of_subjective": 72216, "hash_of_subjective": "C9A78C8FC3B51EECF4202820D303C3A16C362AF3D1617B858764C906755CCECC", "reason": "known header: '72216' <= current '72216'"}
2023-11-10T09:08:43.894Z        INFO    header/store    store/store.go:365      new head        {"height": 72217, "hash": "59BA0A70B7807AA4D86754B9CFA8C46B5BBFB0661B63A14C07B1A19C01955EC1"}

Notes

No response

@suntzu93 suntzu93 added the bug Something isn't working label Nov 10, 2023
@github-actions github-actions bot added the external Issues created by non node team members label Nov 10, 2023
@renaynay
Copy link
Member

Hey @suntzu93 this is not an actual bug but an issue with the way we log this situation. Closing as we will address it in celestiaorg/go-header#110

@ghazni101
Copy link

ghazni101 commented Nov 12, 2023

Hey @suntzu93 this is not an actual bug but an issue with the way we log this situation. Closing as we will address it in celestiaorg/go-header#110

Hey I am getting this error in the log as well. Does this mean everything is working fine? Or do we need to do something to get rid of this error?

I also noticed that this error only appears when I am exposing bridge node prometheus metrics

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working external Issues created by non node team members
Projects
None yet
Development

No branches or pull requests

3 participants