search

pi-node / instructions

266 stars 190 forks source link

consensus container Activation #16

Open adwards74 opened 4 years ago

adwards74 commented 4 years ago

Is it recognized that the consensus container is only available in the Docker desktop version? It is not yet active in Docker Toolbox.

Pupazzi73 commented 4 years ago

How can I activate consensus container on Docker Desktop?

adwards74 commented 4 years ago

How can I activate consensus container on Docker Desktop?

The user's consensus container will be specified by the administrators. Now we can't.

App main official quote: However, the new functionality of turning on and viewing the blockchain will be rolled out gradually to different candidates for technical reasons. This means that after downloading the new version, the majority of candidates will probably see the same interface with the old functionality at first, i.e. turning on the statistics container. Don’t feel discouraged, because even though this version may have the same appearance at the beginning, it carries different substances under the hood. In the following week, more candidates will be able to have the new functionality available, i.e. the switch turning on the blockchain container.

PS ...... For more details, please refer to Read more on the main screen of the app.

Mogithub2020 commented 4 years ago

Hear ye, hear ye, I really need help with my Pi node. When checking for open ports, it gets stuck at "Pinging your computer", so there is no way of telling if it has pinged the computer or not. I have used different avenues to confirm that the ports are indeed open. I have also done port forwarding on my router.

Secondly, when I open the troubleshoot page on the Pi node, it tells me that the consensus container is absent and not enabled. I took a look in Docker Desktop and could only find the port test container. Is there anyway around this please?

My computer runs on widows 10 home with WSL 2 and I am using a docker desktop and I have been running the Pi Node for a month now.

milehigh714 commented 3 years ago

I have the same issue as

Hear ye, hear ye, I really need help with my Pi node. When checking for open ports, it gets stuck at "Pinging your computer", so there is no way of telling if it has pinged the computer or not. I have used different avenues to confirm that the ports are indeed open. I have also done port forwarding on my router.

Secondly, when I open the troubleshoot page on the Pi node, it tells me that the consensus container is absent and not enabled. I took a look in Docker Desktop and could only find the port test container. Is there anyway around this please?

My computer runs on widows 10 home with WSL 2 and I am using a docker desktop and I have been running the Pi Node for a month now.

Same issue here.

adwards74 commented 3 years ago

Once the port has been opened, please use the AnalogX portMapper. And now, I also have the same problem with the pinging part of the inquiry part of the PI node, but there is no big problem with the node execution. Please refer to the following link. https://node-pi.com/pinode_eng

milehigh714 commented 3 years ago

I think I figured out my problem. PCMATIC's SUPERSHIELD doesn't allow me to add the program to it's white list. When I turn off SUPERSHIELD everything works fine. I've logged a ticket with PCMATIC.

Thanks for your reply.

Doug

The information contained in or attached to this email message is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message solely to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by phone or email as indicated above. This email may contain information disclosed to you from records protected by federal confidentiality rules (42CFR part2) Federal rules prohibit re-disclosure of this information without express written consent of the person to whom it pertains or as otherwise permitted by law.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, December 4th, 2020 at 4:41 PM, adwards74 notifications@github.com wrote:

Once the port has been opened, please use the AnalogX portMapper. And now, I also have the same problem with the pinging part of the inquiry part of the PI node, but there is no big problem with the node execution. Please refer to the following link. https://node-pi.com/pinode_eng

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

dgagvgeg commented 3 years ago

I installed the PI Node the other day, I believe that I did it correctly. But nothing is really happening, when I hit trouble shoot it says the following, did I do something wrong? or do I need to wait to be activated?

Consensus container enabled: No

Node switch on: Yes

PortsChecker container: running

Consensus container: error

adwards74 commented 3 years ago

I installed the PI Node the other day, I believe that I did it correctly. But nothing is really happening, when I hit trouble shoot it says the following, did I do something wrong? or do I need to wait to be activated?

Consensus container enabled: No

Node switch on: Yes

PortsChecker container: running

Consensus container: error

Currently, the node is in the process of creating blocks and testing wallets, so errors may occur. I understand that the core team is in the process of generating blocks sequentially according to the operation rate and the specifications of the node PC. For more details, please use App Channel's node channel.

ihatejam commented 3 years ago

The line mentioning "Consensus container enabled: No" implies that you have not been selected to participate as a TestNet node yet - once you're selected, that will change to Consensus container enabled: Yes".
When that happens, a Consensus Docker container will be sent to your machine. Without the Consensus container running, it is normal to see the line with "Consensus container: error". I think it will alternate between "error" and "absent" (or maybe it was "missing"?). This line was added in the version 0.4.0 release - we are now on 0.4.1 which is available for download since the end of last week. Leave it in this state until you are selected. I believe selection is based on your availability % on the troubleshooting page which grows over time as long as you leave the node app (+ docker container running).