search

pi-node / instructions

254 stars 154 forks source link

Concensus suddenly disabled #74

Open iKMOD opened 3 years ago

iKMOD commented 3 years ago

Today after a computer reboot, consensus became disabled, all my troubleshoot data reset to N/A, the button only turns on stellar dummy. Prior to the reboot, my availability was 97%, I was synced with the blockchain and functioned as a supernode. I am current on all my Windows, Pi and Docker versions. I did not change any setting prior to this issue. All ports are still open. Can anyone please help? What caused this problem (so I can avoid in the future) and how do I enable consensus again? Thank you.

Consensus container enabled: No Node switch on: Yes PortsChecker container: running Consensus container: absent State: N/A Protocol version: N/A Latest block: N/A Outgoing connections: N/A Incoming connections: N/A Supporting other nodes: No Pi Node version number: 0.4.3 Operating system: WINDOWS 10.0.19042 (Microsoft Windows 10 Pro) Using Docker Toolbox: No Node installation date: N/A Availability (up to 90 days): N/A

ihatejam commented 3 years ago

It appears as if your configuration has been wiped out. Just to be certain, i would restart windows again and start up the node app afresh, then go through the troubleshooting steps again.

Do you still have both Docker images showing in your Docker Desktop dashboard? If not, then I think someone who has access to your setup may have clicked the "remove blockchain data" link on the Troubleshooting screen of the node app. This will zero your installation -- in some cases, after this is done, you will need to wait until you are invited to the test blockchain again.

iKMOD commented 3 years ago

Thank you. Both images/containers, Dummy and Concensus are still in Docker. But for some reason the button only runs the Dummy. I think you are right. I am resigned to just wait to be invited again. It's just a shame since everything was going so well. I hope this doesn't happen to anyone else.

ihatejam commented 3 years ago

have you tried manually starting the consensus docker image? My consensus image can only be started from docker for some reason -- it seems to ignore the switch in the app. Try starting the consensus image in your Docker Desktop dashboard by clicking the "start" button - see if it helps, and then check the status back in the Node app.

iKMOD commented 3 years ago

Great idea! Unfortunately, it didn't work. If I find out what happened to me or see others explain why some can only start consensus from within Docker, I will let you know. Thanks again for your help!

btcmaster1 commented 2 years ago

Pioneer

michelferia commented 2 years ago

I have same issue and we are many with same problem, I really think that the nodes are not available for new testers o something like that. Anyone have any clues? Thanks