-
Notifications
You must be signed in to change notification settings - Fork 721
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
Cardano node 1.3.0, syncing stops due to ledger failure on testnet #461
Comments
Removing volatile db and restarting the service caused metrics to report but node stopped syncing blocks. We're currently testing clearing entire state. |
Clearing entire state did not resolve. The last blockHeight reported sync'd by the metrics is |
While trying to sync a local byron-proxy to test if that works, it complained about an invalid block around a similar area, with an invalid
|
I'm in the same situation. Is there any solution? BlockHeght stopped at 626706 |
Once the issue is solved, this ticket will be updated @shenyaqi9527. |
A local sync of Byron proxy to testnet, syncs repeatedly, all the way to the real tip, and then loops back this problem block, |
This is using the default proxy config: |
proposal UI gives these details for that proposal:
|
could this be because ledger rules require applicationVersion to be greater than previous 1 instead of greater than or equal to? That could be an easy fix to resolve. |
There are indeed some rules about how the major/minor/patch version numbers must be incremented but I can't recall off the top of my head. Will find them in the program text. Edit: I was referring the "block version". I'd bet there's a similar thing for application version. |
Old ledger (cardano-sl)
New ledger (
Who is right? Old one says version must increase by 1 or stay the same. New version says it must increase by 1. |
I rebuilt proxy with ledger commit
|
Rebuilding proxy with your latest commit hash on that branch @dcoutts (b3c8c59), or with @disassembler's similar branch (dedc232) results in a byron proxy which can sync with testnet fully without throwing the |
A proxy and node sync also works with the cardano-ledger branch |
This is resolved in current master and 1.4.0 pre-release. |
After a
1.2.0
to1.3.0
deployment and service restart ontestnet
, cardano-node1.3.0
stopped syncing as observed by the following changes in behavior:immutable
directory, and the most recent epoch files are not present (last epoch written is 28, current epoch is 33).Systemd reports the
cardano-node
service is active and running. There are periodic 1 minutecardano.messagecounters.[aggregation|ekgview|monitoring]
journalctl updates, but they don't offer any clue about what the state of the service is. There are no errors or warnings being issued.The last few log lines which offer information which may help are:
Restarting the cardano-node service does not resolve the issue.
The text was updated successfully, but these errors were encountered: