-
Notifications
You must be signed in to change notification settings - Fork 1.6k
v0.7.22 Kusama still not possible to sync node #894
Comments
This is a log from a validator? Did you disable archive mode? |
It is from a node running with the validator flag. Archival node has of course not been disabled. |
What you mean by |
Here is the command I'm running it with:
You can see what I meant with the |
Problem still persists on
|
Every log you posted, was this from a fresh resync? We released a new version today, that added a fix for syncing. Maybe that helps you? I synced today as well and run into a similar problem :( However, I did not yet try the latest version. |
Both logs I posted are from the same sync. They are just 8 days apart. I did no purging between these two. Now, I purged the chain and started a resync with the newest version and everything looks good so far. Will close this once the node is done syncing without the issue. |
Ok, this issue seems to be resolved. However, a note for everyone who has the same problem: You need to purge and resync from scratch. Otherwhise the new upgrade will also not work. |
Yeah it depends on the error, this one really required a full resync. |
5330d84e CLI: naming clean-up. (paritytech#897) f99f2225 Westend<>Rococo Headers Relay (paritytech#875) 72c9117b Use complex headers+messages relay in test deployments (paritytech#905) 48423d5b Stop recursing when creating test headers (paritytech#906) f8586fd4 Fix outstanding bridge names. (paritytech#901) 54b683b3 Complex headers+messages Millau<->Rialto relay (paritytech#878) c0e77ca1 fix message generator scripts (paritytech#900) debf3a82 Use Substrate state_getReadProof RPC method to get storage proofs (paritytech#893) c3fa7216 Support more than `u8::max_value` GRANDPA validators (paritytech#896) e5cb87f9 Grandpa Pallet Pruning (paritytech#890) 0b6a8920 RestartNeeded is a connection error (paritytech#894) 2cf5fa26 CLI: Estimate Fee (paritytech#888) 7dace624 CLI: Send Message (paritytech#886) f8eaecfa CLI: Encode Message (paritytech#889) 1610f868 Bump `jsonrpsee` to Alpha.3 (paritytech#892) d665b531 Use new Cargo feature resolver (paritytech#891) ce2ee6ed Rialto Millau Maintenance Dashboard (paritytech#881) 7c585ce8 Revert to older nightly. (paritytech#887) 73a0470e Adding GrandpaJustification custom type (paritytech#882) b9ccea9c Install CA certificates in relay images (paritytech#880) ec7841a2 fix widget names (paritytech#879) REVERT: 746a4027 Accidentally committed `cargo-expand`ed code 🤦 REVERT: 1a5d09c5 Add note to more closely match `initialize` Call variant REVERT: fdd6e6b3 Add `submit_finality_proof` mock Call variant REVERT: 768b053e Simplify the Rococo and Westend signing params REVERT: 62aca80e Add Westend<>Rococo variants to `relay_headers` REVERT: 0bcb0f51 Add Westend<>Rococo variants to `init_bridge` REVERT: 01d1305f Use mock Westend and Rococo finaltiy tx calls REVERT: fb34b9dd Add modules for Rococo<>Westend header sync git-subtree-dir: bridges git-subtree-split: 5330d84e9511e38cf9d9ec765bee865fedd4b260
I'm on Kusama v0.7.22 and still experiencing the issue referenced in #866 . The issue was closed because it should be merged in the next release. v0.7.22 is the next release, but the issue persists.
Is there a workaround to sync a node with the current release? If not, when can we expect a release that fixes this?
The text was updated successfully, but these errors were encountered: