#dusk $DUSK @Dusk
I nearly reached for the reset button because a Dusk node looked stuck.
That would have been the wrong fix.
In the workshop, a machine that is slow and a machine that is dead are two very different problems. Dusk’s node docs make the same distinction.
If block height is behind but still increasing, the node may simply be catching up.
So before touching state, I’d do one boring check:
read the block height,
wait about 30 seconds,
read it again.
If it moved, I have evidence of progress.
If it didn’t, then I start checking peers, logs and service state.
That matters because a full reset is not a harmless “try again” button. It deletes local state, archive data, wallet cache and logs, then forces the node to synchronize again.
So my rule is simple:
lag is a symptom, not a diagnosis.
Don’t erase the evidence before proving the node is actually stuck.
I nearly reached for the reset button because a Dusk node looked stuck.
That would have been the wrong fix.
In the workshop, a machine that is slow and a machine that is dead are two very different problems. Dusk’s node docs make the same distinction.
If block height is behind but still increasing, the node may simply be catching up.
So before touching state, I’d do one boring check:
read the block height,
wait about 30 seconds,
read it again.
If it moved, I have evidence of progress.
If it didn’t, then I start checking peers, logs and service state.
That matters because a full reset is not a harmless “try again” button. It deletes local state, archive data, wallet cache and logs, then forces the node to synchronize again.
So my rule is simple:
lag is a symptom, not a diagnosis.
Don’t erase the evidence before proving the node is actually stuck.
