Hi all,
I am starting to get pretty annoyed by the way the pNode behaves lately. I am not sure if this has to do with the hardware used in the pNode, which might be too weak, but it makes running a node somehow useless. My node is up and running on a very strong, stable, business grade internet connection and has been constantly online since weeks waiting for its turn to be in the committee. No issues, no stalls, no reboots. Yesterday it was the node’s turn to validate blocks and the epoch before committee the node had a “beacon stall” which I recognized by chance as I was checking the node’s status every day. So i rebooted the node through the (very user unfriendly) web interface on port 5000. But a docker restart made the node start syncing again. However apparently not quickly enough to make it in time, so it got slashed… It even doesn’t show up on https://monitor.incognito.org/node-monitor anymore since the docker restart. While the app shows “online” and “syncing”… Pretty strange.
-
How can I get the node refunded after it got slashed? @Support Can you help?
-
Are there any plans to get notifications from the app once the beacon stalls? Else you are required to check the node manually every few hours…
-
Can it be the node hardware is too weak to properly sync the shard data in time and could that be the reason for the constant stalls right before commitee?
Looking forward to hearing from you,
scooter