search

pi-node / instructions

266 stars 190 forks source link

pi node container consensus issue #49

Open alexmihai212 opened 3 years ago

alexmihai212 commented 3 years ago

Troubleshooting Diagnostics Info Container Consensus container enabled: No -HOW to ENABLE? Node switch on: Yes PortsChecker container: running Consensus container: absent **-HOW to ENABLE? pinode problwm

**

Other Pi Node version number: 0.3.8 Operating system: WINDOWS 10.0.19042 (Microsoft Windows 10 Enterprise) Using Docker Toolbox: No Node installation date: 2021-01-14 Availability (up to 90 days): 37.18% from 2021-01-14 to 2021-01-19

Back

AMZNG1 commented 3 years ago

You just have to keep running your node and wait until it gets fully synced

justin6652 commented 3 years ago

Screenshot (4) The node has been hung up for 4 days, how long does it usually take Consensus container？

congmxt commented 3 years ago

Screenshot (4) The node has been hung up for 4 days, how long does it usually take Consensus container？ Hi! I have the same situation with your. How to do? pls

justin6652 commented 3 years ago

just keep running your node until core team enabled the container

racetech22 commented 3 years ago

About 2 days ago, in Troubleshooting, the "Node installation date:" stopped showing the date and now shows N/A.

In "Availability (up to 90 days)", too, it stopped showing availability in % and started showing N/A.

Is this normal or should I do something? 20211021_Pi_Node_Troubleshooting_Capture

justin6652 commented 3 years ago

just keep running node Pi core team will fix this problem!no need do anything ~my node already 3 day no update showing availability!

justin6652 commented 3 years ago

Screenshot 2021-10-03 181855

racetech22 commented 3 years ago

just keep running node Pi core team will fix this problem!no need do anything ~my node already 3 day no update showing availability!

Thanks Justin!

smith111707 commented 3 years ago

I'm experiencing the same issue: pinode1

SeedKunY commented 3 years ago

Keep running the node listener container until your availability stats are higher - this will take a while. Once you approach or exceed 90% availability, you are more likely to be selected to run the consensus container. Once selected, the consensus container will be auto-deployed to your node setup.

My node has exceed 90% availability, but consensus container is still absent. Any idea?IMG_20211111_063524.jpg

ihatejam commented 3 years ago

It's possible that newer nodes will not be getting the consensus container right now - since all existing nodes are running against the testnet blockchain and the Pi Core Team are so close to launching the mainnet. I would not be too concerned about this right now since there is currently no real benefit to running the node -- AFAIK, the Core Team still have to discuss the reward scheme for running nodes.

smith111707 commented 3 years ago

My node has exceed 90% availability, but consensus container is still absent. Any idea? I have an idea. Seems, the Pi Team is just don't care.

@ihatejam, where is the "Core Team"? Who they are? Are they going to answer our questions?

SeedKunY commented 3 years ago 
agree with you. pi node is trash software

在 2021年11月14日星期日，smith111707 @.***> 写道：

My node has exceed 90% availability, but consensus container is still absent. Any idea? I have an idea. Seems, the Pi Team is just don't care.

@ihatejam https://github.com/ihatejam, where is the "Core Team"? Who they are? Are they going to answer our questions?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pi-node/instructions/issues/49#issuecomment-968264023, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABU56IYZQ6XL3RTJUPNOLPDUL6FPHANCNFSM4WIRE7RA .

ihatejam commented 3 years ago

My node has exceed 90% availability, but consensus container is still absent. Any idea? I have an idea. Seems, the Pi Team is just don't care.

@ihatejam, where is the "Core Team"? Who they are? Are they going to answer our questions?

This is just a community page where Pi members help each other with the Node-related questions -- I don't believe the Core Team actually contribute on this page at all. This page is not linked to officially in the menu of the app, like they've linked to their official social media accounts on Twitter/FaceBook/Instagram/Youtube/Telegram.

You have a better chance of getting hold of the Core Team on the main app - sometimes show up in "Developers (English)" chat room -- or by reaching out to support@minepi.com (you could have a looooong wait though).

Have a look in the menu of the main app - under Core Team for an intro to the main Core Team members - the two founders of Pi Network. Of course, there are more Core Team members, but they're mostly developers. Even then, the team is tiny (less than 20 people) so as much as they would like to be responsive on all platforms, with over 25Million engaged users, they cannot possibly be.

smith111707 commented 3 years ago

This is just a community page

Not sure I can agree with that. Take a look who has created the repo ;-)

Of course, there are more Core Team members, but they're mostly developers.

The questions still the same - why the dev team members are a sort of "ninjas"? That looks strange to me.

You have a better chance of getting hold of the Core Team on the main app

That's strange again. Usually github is the main place for developers. If we are about developers ;-)

ihatejam commented 3 years ago

Understood!! I'm aware that NK created the page -- but, as you probably already gathered, this is not a typical dev git. The idea was for the community to contribute to this page as a "self-help" forum for those wanting to try out the node software against the Testnet blockchain. This was (originally) intended to be a "convenient" place for people to help each other setup their nodes until they were able to access the "Node Applicants" chat room in the app. I can't recall the criteria for actually being able to see the "Node Applicants" chat room in the Pi app's chat room list, but I know that it is not available to everyone by default.

This is just a community page

Not sure I can agree with that. Take a look who has created the repo ;-)

Of course, there are more Core Team members, but they're mostly developers.

The questions still the same - why the dev team members are a sort of "ninjas"? That looks strange to me.

You have a better chance of getting hold of the Core Team on the main app

That's strange again. Usually github is the main place for developers. If we are about developers ;-)

sunnygud commented 2 years ago

@here / @admins >>

image

I have installed the Node on 11/19/2021 and till date it shows only 8.83% does this mean, my MAC is not turned on or its not running?

My Mac goes in to Sleep, inorder to keep the containers active .. should have to disable the Screensaver / sleep mode? Any recommendations is appreciated.

whenever i login when the Mac is locked, i keep checking the containers running .. and they are. Does this mean it works even When the lid is closed ?

Any help in answering the above questions is appreciated.

Additionally, i have noticed ... the 31400 Port is used by only 1 Container .. i see other containers running but wouldnt say if its 31400 etc.. i see Port 80 running .. am i doing something wrong in the Docker?

13811462395 commented 2 years ago

理解！！我知道NK创建了这个页面 - 但是，正如你可能已经收集到的那样，这不是一个典型的dev git。这个想法是让社区为这个页面做出贡献，作为一个"自助"论坛，为那些想要尝试针对Testnet区块链的节点软件的人提供服务。这（最初）旨在成为一个"方便"的地方，供人们互相帮助设置他们的节点，直到他们能够访问应用程序中的"节点申请人"聊天室。我不记得实际能够在Pi应用程序的聊天室列表中看到"节点申请人"聊天室的标准，但我知道默认情况下，它不是每个人都可以使用的。

这只是一个社区页面

不确定我能同意这一点。看看谁创建了存储库;-）

当然，核心团队成员更多，但他们大多是开发人员。

问题仍然是一样的 - 为什么开发团队成员是一种"忍者"？这对我来说看起来很奇怪。

您有更好的机会在主应用程序上获得核心团队

这又很奇怪。通常github是开发人员的主要场所。如果我们是关于开发人员的;-）

PortsChecker container: absent问题如何解决谢谢

13811462395 commented 2 years ago

这又很奇怪。通常github是开发人员的主要场所。如果我们是关于开发人员的;-） PortsChecker container: absent请问这个问题如何解决谢谢

MrLexRussian commented 2 years ago

@здесь / @администраторы >>

изображение

I have installed the Node on 11/19/2021 and till date it shows only 8.83% does this mean, my MAC is not turned on or its not running?

Скорее всего, в настройках сети стоит ограничение приема-передачи данных в спящем режиме. Посмотри там.

JO-88 commented 2 years ago

I'm in a similar state. The percentage of "Availability (up to 90 days)" does not increase. Is there anything wrong?

1
MrLexRussian commented 2 years ago

Я нахожусь в аналогичном состоянии. Процент "Доступности (до 90 дней)" не увеличивается.Что-то не так? 1

Я поставил своё железо на круглосуточную работу. За один день поднимается почти 2% "Availability"

ghost commented 2 years ago

First of all, as a node, your computer should not enable sleep mode or any energy-saving mode at all. 

------------------ 原始邮件 ------------------ 发件人: "pi-node/instructions" @.>; 发送时间: 2022年2月4日(星期五) 晚上11:29 @.>; @.***>; 主题: Re: [pi-node/instructions] pi node container consensus issue (#49)

@здесь / @администраторы >>

I have installed the Node on 11/19/2021 and till date it shows only 8.83% does this mean, my MAC is not turned on or its not running?

Скорее всего, в настройках сети стоит ограничение приема-передачи данных в спящем режиме. Посмотри там.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

ramu191193 commented 1 year ago

Its been 2 years i am running the node .. but still its shows availability as N/A.. how long i have to wait or is anything else wrong with node setup? image

cheme75 commented 1 year ago

Its been 2 years i am running the node .. but still its shows availability as N/A.. how long i have to wait or is anything else wrong with node setup? image

Unfortunately, the 2 yrs appear to have been wasted since you do not have the actual consensus container. Hard to say problem from so little info. Are all the ports open? At least 31400-31403 seem to be the ports being used so far. Assuming ports are open, on both pc and router is port forwarding those ports to the ip of pc running node, then see issue #299 - could be the same glitch. Scroll down, there’s a good post with step by step process.

Only other thought is that a while back I had some problems after upgrading docker, so I uninstalled everything, went to docker releases page, downloaded 4.12 and reinstalled which had previously worked well, turned off checking for updates. Reinstalled pi node. Checked my ports manually with a ports checker to be sure they were open. I used info from post issue 299 and all has been good.

salmansaad87 commented 7 months ago

Can you share the data.. troubleshooting + results from command docker ps -a and wsl -l -v from command prompt?

what about this data? I believe Ive done more than required at my current node level. DATA

Consensus container enabled: Yes

Node switch on: Yes

PortsChecker container: exited

Consensus container: running

Consensus State: N/A

Protocol version: N/A

Latest block: N/A

Outgoing connections: N/A

Incoming connections: N/A

Supporting other nodes: No

salmansaad87 commented 7 months ago

Can you share the data.. troubleshooting + results from command docker ps -a and wsl -l -v from command prompt?

what about this data? I believe Ive done more than required at my current node level. DATA

Consensus container enabled: Yes

Node switch on: Yes

PortsChecker container: exited

Consensus container: running

Consensus State: N/A

Protocol version: Latest

Latest block: N/A

Outgoing connections: N/A

Incoming connections: N/A

Supporting other nodes: No

salmansaad87 commented 7 months ago

Can you share the data.. troubleshooting + results from command docker ps -a and wsl -l -v from command prompt?

For "docker ps -a"

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 239938c83864 pinetwork/pi-node-docker:latest "/start --testnet" 53 minutes ago Up 53 minutes 5432/tcp, 0.0.0.0:31402->31402/tcp, 0.0.0.0:31403->1570/tcp, 0.0.0.0:31401->8000/tcp pi-consensus 84ddf80544cf ese7en/node-port-test "node index.js" 44 hours ago Exited (137) 2 hours ago stellar-dummy

and for "wsl -l -v "

NAME STATE VERSION

I believe I've done more than required at my current node level.

Consensus container enabled: Yes Node switch on: Yes PortsChecker container: exited Consensus container: running

Consensus State: Joining SCP Protocol version: Latest Latest block: N/A Outgoing connections: N/A Incoming connections: N/A Supporting other nodes: No

armsagitta commented 4 months ago

On my Windows 10 Home Network state: connected to OpenVPN Server run on a router in a remote location where I could open the ports (31400-31409).

COINTAINER:

Consensus container enabled: Yes Node switch on: Yes PortsChecker container: exited Consensus container: running

CONSENSUS:

State: Joining SCP Protocol version: Latest Latest block: N/A Outgoing connections: 8 Incoming connections: 0 Supporting other nodes: No

In the screenshot below worth noting: Local block number: 1 Unable to reach the network, please provide the IP/domain of a known node...

node

And the diagnostics info diagnostics

Also, ports check is successfull. Ports accessibility is present in browser when launched from stellar-dummy (31400-31409). Page says OK FROM PORT 31401. The same for the other ports. But when consensus container is running port accessibility always fails. This problems is too hard for me to troubleshoot. Any suggestions for a solution?