-
Notifications
You must be signed in to change notification settings - Fork 248
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
ERR re-enqueueing failed block: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg #701
Comments
Maybe this issue could be related with this other |
I've asked related validators that please turn off the buggy relayer until I check if is related |
Not related, is about Client Updates, not about IBC acks (so forget that comment) |
Hey @RaulBernal can I have a link to your bdjuno implementation? I think you can first try replacing juno version to the latest one |
Upgraded and running, but error still there: How can I link you? (maybe pass me your SSH public key by DM using email/telegram/discord ? ) |
For give you more context:
|
So maybe I need to exec: I have two identical servers; If I try to make the migration in one of them I get: |
3:25PM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=14582098 Any idea guys? on callisto branch cosmos/v0.47.x branch |
Certainly, error has disappears adding:
|
Hi @MonikaCat I'm using BDjuno branch cosmos/v0.47.x with no changes. Everything started smooth but again: 10:31AM DBG processing block height=14729369
10:31AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=14729369
10:31AM DBG processing block height=14729369
10:31AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=14729369
10:31AM DBG processing block height=14729369
10:31AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=14729369
10:31AM DBG processing block height=14729369
10:31AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=14729369
10:31AM DBG processing block height=14729369
10:31AM DBG processing block height=14729369
10:31AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=14729369
10:31AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=14729369
10:31AM DBG processing block height=14729369
10:31AM DBG processing block height=14729574
10:31AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=14729574 It stucks the live sync (https://explorer2.bitcanna.io) When I check in other explorer the block 14729369: (https://www.mintscan.io/bitcanna/block/14729369?chainId=bitcanna-1) |
Bug description
I get this error in loop:
As consequence, the MainNET explorer is 10 hours behind the current synced block.
I have another instance (a backup server) running the same software and is not stucked in the same ERR
Steps to reproduce
BDJuno version is (both servers):
Expected behavior
Expected a bypass if it can't parse the message not a stuck :)
The text was updated successfully, but these errors were encountered: