node-installer icon indicating copy to clipboard operation
node-installer copied to clipboard

Testnet: event="Consensus msg discarded" reason="too far in the future"

Open PLombi100 opened this issue 1 year ago • 1 comments

Describe the bug There appears to be an issue with either the node installer for (Testnet mode) or with Testnet itself.

After installing the node from curl --proto '=https' --tlsv1.2 -sSfL https://github.com/dusk-network/node-installer/releases/latest/download/node-installer.sh | sudo bash -s testnet numerous times starting from fresh VPS sessions each time I keep encountering the same issue where the block-height remains on 0. The rusk log shows the following message: event="Consensus msg discarded" reason="too far in the future".

I've tried ruskreset multiple times as well as re-synchronising my date-time to no avail.

OS: Ubuntu 24.04 LTS

At least one more node runner has claimed experiencing the same issue yesterday.

To Reproduce Simply following the instruction in https://docs.dusk.network/operator/guides/provisioner-node/ and choosing the node installer from the 'Testnet' tab.

// Be exhaustive //


**Expected behaviour**
A clear and concise description of what you expected to happen.

**Logs/Screenshot**
If applicable, add damning logs

**Platform**
Fill as appropriate
 - Architecture: [ARM, 8086]
 - OS: [e.g. iOS, Linux]
 - Browser [e.g. chrome, safari]

**Additional context**
Add any other context about the problem here.

PLombi100 avatar Jan 24 '25 10:01 PLombi100

Note, I have this happen every couple days on Mainnet as well -- just in case it could be the same cause:

2025-01-24T13:03:03.710215Z WARN node::chain::acceptor: event="Consensus msg discarded" reason="too far in the future" topic=Ratification info=ConsensusHeader { prev_block_hash: "0b568f9b98c38076...4f6cf95e68abfa9b", round: 147193, iteration: 0 } ray_id="" 2025-01-24T13:03:03.854045Z WARN node::chain::acceptor: event="Consensus msg discarded" reason="too far in the future" topic=Candidate info=ConsensusHeader { prev_block_hash: "0b568f9b98c38076...4f6cf95e68abfa9b", round: 147193, iteration: 1 } ray_id=""

Restarting rusk allows it to run properly again, in my case.

wolfrage76 avatar Jan 24 '25 14:01 wolfrage76