#Unable to start validator normally
103 messages · Page 1 of 1 (latest)
I reinstalled the validator several times and still encountered this error. I changed to another vps and also encountered this problem
Hey @pale goblet @fresh hollow, please check this support ticket with unable to fetch list of nodes in the network error.
Here's the bug report submitted by @mental finch : https://github.com/shardeum/bug-reporting/issues/937
I gave feedback on github last week, but I never got a reply
I also tried to reinstall the validator after 11.22, but it still didn’t work, still the same error.
?
@mental finch i am checking in
same here
@mental finch did you upgraded or reinstalled the validator again? can you try again as the network was down yesterday due to some issues with ITN3
Still not working, this error did not just appear yesterday. I updated/reinstalled the verifier on November 18th, and then encountered the error. I saw the update on November 22nd and tried to reinstall it. Until today, I have reinstalled it a lot. times, still not working
It's always been this mistake
cc: @pale goblet
@mental finch can you give me your machine details please?
also, looking at arc server ip from the screenshot, it looks like you are still using old one. can you clean install after uninstalling current one
arc server what does it mean
Do you mean to uninstall this container instance? Or reinstall the ubuntu system?
not your system but uninstall the validator dashboard and install again, https://docs.shardeum.org/docs/node/run/validator/self-host#uninstall-validator
Steps to run a Self Hosted Shardeum Validator on Your Own Hardware
ip:45.204.85.50
x86_64
ubuntu 22.04
I have uninstalled and reinstalled it
Please check here
thanks for sharing details, let me try replicating.
Ubuntu 22.04.1 LTS
can you share with me the script you are using to install?
There seems to be no need to share
@mental finch from the screenshot you shared, i am seeing that you have the wrong archiver IP which means your new validator installation failed to install for some reason. The correct archiver is: https://github.com/shardeum/validator-dashboard/blob/df157b8c09090995bd012844d10d838d6b842401/installer.sh#L607
I recommend manually wiping the old installation, stopping and removing the Docker instance and images, and then proceeding with a fresh reinstall.
There was an error in staking
Never been able to pledge successfully
@pale goblet
From the logs you shared, you weren't able to stake because you had previously staked a node with your connected wallet.
A few things you could do:
- Unstake the previous node if you still have access to it (you can only use 1 wallet for 1 node)
- Connect a new wallet to this node, fund it through the faucet and stake your node
@mental finch please check what @fresh hollow suggests, and it should work
Wait for him to respond?
@mental finch Please follow the instructions here: #1310145774574768251 message
I can't access the previous node because I deleted the docker instance and reinstalled it
Check your stake amount with:
operator-cli stake_info <wallet_address>
Remove stake with:
operator-cli unstake
Add stake with:
operator-cli stake 10
You can also access GUI (Dashboard):
You have to put your IP address in browser.
For eg: https://206.189.136.184:8080/
Where 206.189.135.185 is your VPS IP address and 8080 is your port number that you assigned while installing the validator node.
Go to node settings and Use force remove stake option to remove stake. Then Restake 10 SHM.
Cannot cancel
First go to node settings and Use force remove stake option to remove stake. Then Restake 10 SHM.
How to forcibly remove the pledge directly through the cli command?
Wait 15 minutes after using operator-cli stop
Then use operator-cli unstake
If you're unable to unstake your node, use a new wallet & update the address here: https://shm.gg/validator-wallet-update
Purpose of this form? This form is for validators affected by the recent network update in our ITN Stage 3, which has caused some nodes to experience restart and stake/unstake issues.
Action to be taken: If you've switched to a new wallet to continue node operations and maintain your leaderboard ranking, please use this form to submit your upda...
bro, when i want to update node, i need remove dcoker container?
Or just stop it?
ok, I understand, thank you
thank you very much
For Existing validators: https://shm.gg/validator-update
Steps to run a Self Hosted Shardeum Validator on Your Own Hardware
yes, but in this page write
that means delete container and then start curl?
No, this command is used to exit the container, not delete it.
what command exit container, i don't know
maybe docker stop <id-container> and that's all?
exit
cd ..
Then use the curl command to update the node:
curl -O https://raw.githubusercontent.com/shardeum/validator-dashboard/main/installer.sh && chmod +x installer.sh && ./installer.sh
i see, but i use docker)
stop docker?
or stop and delete?
Hi! Same here … node stopped unable to join the network. Just saw the update about the fix of that error… but the node is node starting either with my original address or with a new one …
When I installed another vps, after the startup command was successful, I could not check the status and an error occurred.
@mental finch you are getting this if the local validator has crashed, stopped, or is unresponsive: https://github.com/shardeum/validator-cli/blob/main/src/utils/fetch-network-data.ts#L265
what you could do here is, run pm2 ps And see what the status is of the processes, You can also run pm2 logs to see the most recent log entries
how do i solve this problem
as mentioned here, try doing pm2 psand see what is the status of your process. if it's errored, try starting the validator again
It's normal here
@pale goblet
@pale goblet
@pale goblet
Sonia is currently attending the IBW conference but she'll respond to you when she is back.
@mental finch i am sorry, i was away for IBW conference, can you tell me what's the latest stage of errors you are facing or it's fixed?
i am happy to jump over call and debug with you!
There's no fix yet, it's always been this way
@mental finch Please share the step by step process you followed to arrive at this issue?
The exact installer script you used, your VM instance specification, etc.
I will try to retrace your steps and see if I can reproduce the error.
Ubuntu 22.04.1 LTS
Docker version 26.1.2, build
1 core 2 threads
4G memory
200G disk
Hong Kong public network ip
Latest installation script
thank you, can you share or link the latest installation script
I can't send the link, send it directly to you through the picture, I installed it using this script
thank you @mental finch I'll try to reproduce
Hey @mental finch I was able to run the installer, stake the node, and have it participate. See the logs attached. Please follow the steps I used in the logs and see if you have some success. If you run into any issues, then let's do it together to hopefully unblock you! share your email and availability so I can set up a call tomorrow