You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Noticed already a couple of times my node gets stuck with the server gets a forced reboot by the supplier.
Only way a got around it and got it working was a full node reset (ruskreset) which then triggers a full re-sync, specially when fast-sync is not available (yet).
But would be better if after a forced reboot rusk would recover normally.
To Reproduce
force reboot your node
login to console and try to start rusk or fetch the status.
Expected behaviour
Node recovers itself after a hardware issue when hardware is restarted and doesn't get corrupt
Logs/Screenshot
Platform
Vultr node according to specs
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
Noticed already a couple of times my node gets stuck with the server gets a forced reboot by the supplier.
Only way a got around it and got it working was a full node reset (ruskreset) which then triggers a full re-sync, specially when fast-sync is not available (yet).
But would be better if after a forced reboot rusk would recover normally.
To Reproduce
force reboot your node
login to console and try to start rusk or fetch the status.
Expected behaviour
Node recovers itself after a hardware issue when hardware is restarted and doesn't get corrupt
Logs/Screenshot
Platform
Vultr node according to specs
Additional context
The text was updated successfully, but these errors were encountered: