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
Removing the validator key from the active validator node and then sending a SIGHUP signal to the process produces log output showing the config file being reloaded and that no validator key is found. However, the node appears to continue as a validator with the text "Validator |" on every stats line that lists the number of validators.
To Reproduce
Remove the validator key file on a running active validator node and send a SIGHUP signal to the neard process
Expected behavior
I would expect the node to stop validating when it has detected that no validator key is present after it receives a SIGHUP signal and that there should not be the text "Validator |" on every stats line in the logs.
Version:
nearcore 2.1.0-rc.1
rust version 1.77
testnet
The text was updated successfully, but these errors were encountered:
Describe the bug
Removing the validator key from the active validator node and then sending a SIGHUP signal to the process produces log output showing the config file being reloaded and that no validator key is found. However, the node appears to continue as a validator with the text "Validator |" on every stats line that lists the number of validators.
To Reproduce
Remove the validator key file on a running active validator node and send a SIGHUP signal to the neard process
Expected behavior
I would expect the node to stop validating when it has detected that no validator key is present after it receives a SIGHUP signal and that there should not be the text "Validator |" on every stats line in the logs.
Version:
The text was updated successfully, but these errors were encountered: