Your computer is starting up the blockchain?

[SexyParabola]

I've had the node installed for several weeks now and today I updated it to the most recent version. I'm curious why my Pi Node never moves on from this statement: "Your computer is starting up the blockchain". Is this what it's supposed to say? Is something wrong with my network or docker settings?

[SexyParabola]

[ihatejam]

I'm keen to have a closer look via a remote session, but only if you're comfortable with it (you're the second person to mention getting stuck in this state).

If you'd like to proceed, feel free to check my creds with the Pi chat mods -- ask them who "ihatejam" is, then let me know here if you're good to go.

[steeveee100]

@ihatejam. I'm sure we'd all be very interested in what you find out.

[SCHagens]

I have the same problem. After updating Docker it no longer connects. Just Stuck. Anybody know how to solve the issue?

[SCHagens]

I've had the node installed for several weeks now and today I updated it to the most recent version. I'm curious why my Pi Node never moves on from this statement: "Your computer is starting up the blockchain". Is this what it's supposed to say? Is something wrong with my network or docker settings?

Did you come right yet?

[hoansg]

Your Node is working well, 2 things that make the block not available

• The node in the stellar-dummy bullet period has not come to Pi-consensus.
• Core Team has not been updated since the 6th day, so I do not know what the node will be like!

[ihatejam]

@SCHagens - I can extend the same offer I aimed at @RoBoLilly above --

I can have a closer look via a remote session, but only if you're comfortable with it.

If you're unsure who I am, feel free to check with the Pi chat mods if they know "ihatejam" -- then let me know here if you're good to go. We can do a remote session via Teamviewer or Anydesk at an agreeable time.

[pilgrim103]

I have had the same problem. I forgot that since I have Xfinity Cable, I am using their router and behind yet ANOTHER firewall. Had to go in their Gateway and do the port forwarding for them also. The second time it happened, for some reason, Ubuntu was not running. Nor Oracle Virtual box. Make sure all the necessary programs are up and running correctly. Use the no famous external port checker to make sure the Node has access to ports. This was my experience. I have more issues but will save that for later. Now running Node/Blockchain and are current at 161xxxx or something.

[SexyParabola]

@ihatejam Sorry for buzzing off. I had a nice weekend. I would be happy to remote and figure this out. I have Teamviewer. I think I'm going to play around with my Xfinity router and see if that helps. Btw docker does say pi-consensus is running and that stellar-dummy is exited...

[SexyParabola]

Double checked my ports for the node are forwarded so that's not the problem.

[ghcassidy]

After I upgraded pi node to latest version, I have the same problem for 2 days. I saw my pi-consensus log has issue, I tried to reinstall docker but still seeing the same problem. Router ports forwarding set up the same as earlier, IP address not changed. Not sure what's the issue here. Does anyone know how to fix this?

[pilgrim103]

Assuming you have the ports set right in Windows Firewall, you also need the Apps allowed in Firewall. My firewall has entries for Docker, Docker Desktop and something called Docker Desktop Backend, both Inbound and Outbound. They are "allowed" Apps. I see from your second photo that the container is running, and mine says the exact same thing, EXCEPT after the word "running" it says "Port 31403" so I would believe that Docker is not getting access to the ports, which you already know. I listed one reason, but there are more. Did you install Oracle's Virtual Box Manager per the instructions (which by the way are out of date)? I have been stumping for an "Installer" for the Node software and all the other code and Powershell commands. Ignore the "Trouble shooting Screen" on the Pi App. It rarely shows correct information. I have been Blockchaining and my screen says all sorts of weird stuff. Just like the "port checker" on the Technical setup screen. Mine always went into an infinite loop, and now comes back saying all my Ports are closed, when of course they are all open. Do you have a Technical background? I have also been trying to get the Powers-to-be to explain that this is not one of the easier installs for an application. And "Docker" is somewhat outdated, not sure why they went this way .

---

From: ghcassidy @.> Sent: Monday, May 10, 2021 10:50 PM To: pi-node/instructions @.> Cc: pilgrim103 @.>; Comment @.> Subject: Re: [pi-node/instructions] Your computer is starting up the blockchain? (#116)

After I upgraded pi node to latest version, I have the same problem for 2 days. I saw my pi-consensus log has issue, I tried to reinstall docker but still seeing the same problem. Router ports forwarding set up the same as earlier, IP address not changed. Not sure what's the issue here. Does anyone know how to fix this? [Screen Shot 2021-05-10 at 23 44 45]https://user-images.githubusercontent.com/44917964/117755311-fa506080-b1e9-11eb-94f8-c6a06dafb135.png [Screen Shot 2021-05-10 at 23 44 26]https://user-images.githubusercontent.com/44917964/117755318-fd4b5100-b1e9-11eb-9fbe-591955af2737.png

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/pi-node/instructions/issues/116#issuecomment-837746906, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUADJJWWCFMYDGPG45SA5SDTNCSPVANCNFSM44HRTJVQ.

[vmonjo]

Same problem with macOS, the checking ports process is correct but the diagnosis info is like ghcassidy...

[pilgrim103]

omg. MacOS? It is hard enough to get it right on Windows with instructions that were written 8 years ago.

---

From: vmonjo @.> Sent: Tuesday, May 11, 2021 1:51 AM To: pi-node/instructions @.> Cc: pilgrim103 @.>; Comment @.> Subject: Re: [pi-node/instructions] Your computer is starting up the blockchain? (#116)

Same problem with macOS, the checking ports process is correct but the diagnosis info is like ghcassidy...

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/pi-node/instructions/issues/116#issuecomment-837941686, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUADJJVYXBVJV5SFNCFBNKDTNDHWXANCNFSM44HRTJVQ.

[ghcassidy]

Assuming you have the ports set right in Windows Firewall, you also need the Apps allowed in Firewall. My firewall has entries for Docker, Docker Desktop and something called Docker Desktop Backend, both Inbound and Outbound. They are "allowed" Apps. I see from your second photo that the container is running, and mine says the exact same thing, EXCEPT after the word "running" it says "Port 31403" so I would believe that Docker is not getting access to the ports, which you already know. I listed one reason, but there are more. Did you install Oracle's Virtual Box Manager per the instructions (which by the way are out of date)? I have been stumping for an "Installer" for the Node software and all the other code and Powershell commands. Ignore the "Trouble shooting Screen" on the Pi App. It rarely shows correct information. I have been Blockchaining and my screen says all sorts of weird stuff. Just like the "port checker" on the Technical setup screen. Mine always went into an infinite loop, and now comes back saying all my Ports are closed, when of course they are all open. Do you have a Technical background? I have also been trying to get the Powers-to-be to explain that this is not one of the easier installs for an application. And "Docker" is somewhat outdated, not sure why they went this way . … ____ From: ghcassidy @.> Sent: Monday, May 10, 2021 10:50 PM To: pi-node/instructions @.> Cc: pilgrim103 @.>; Comment @.> Subject: Re: [pi-node/instructions] Your computer is starting up the blockchain? (#116) After I upgraded pi node to latest version, I have the same problem for 2 days. I saw my pi-consensus log has issue, I tried to reinstall docker but still seeing the same problem. Router ports forwarding set up the same as earlier, IP address not changed. Not sure what's the issue here. Does anyone know how to fix this? [Screen Shot 2021-05-10 at 23 44 45]https://user-images.githubusercontent.com/44917964/117755311-fa506080-b1e9-11eb-94f8-c6a06dafb135.png [Screen Shot 2021-05-10 at 23 44 26]https://user-images.githubusercontent.com/44917964/117755318-fd4b5100-b1e9-11eb-9fbe-591955af2737.png — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#116 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUADJJWWCFMYDGPG45SA5SDTNCSPVANCNFSM44HRTJVQ.

Thank you for your response. I didn't install Oracle's Virtual Box Manager and I have double checked my ports as well are all open properly. I do use the MacOS system which seems the same issue as RoBoLilly saw on windows.

[SexyParabola]

@ghcassidy Your posted docker window is exactly what I have with some differing pid.

[pilgrim103]

Lots to say. First off, I wish people would start ignoring the "Troubleshoot" screen on the Pi Network app. It is misleading, updated irregularly and often just out right WRONG. An admin said as much a few months back. As far as your Docker pictures, they tell alot. You are getting nowhere near Docker running pi-consensus, you cannot even run the stellar container. I know you do not want to hear this but I think it is a Port issue. You should have the "Port 31403" or whatever # listed on the Docker ap after the word "Running". There are two other options I can think of.. 1. Is this version 3.3 of Docker, and do you have a correctly installed version of Linux? Second, have you added the all the apps I previously mentioned to the Firewall? Regarding the message "Starting the Blockchain" on the Pi app. It could mean alot. I have two desktops. One is my wifes and has been running the blockchain for a month with no problem. My desktop is stuck on the starting-blockchain-message for 2 weeks. Since the firewall and router settings are the same, I just waited. Today I nosed around and found out my desktop only has access to ports 31401-31403. GO FIGURE! How can that be? Same settings everywhere. Also, if you have an Xfinity router/Gateway and plan on more than one node you are screwed. For some idiotic reason they do not allow you to Port Forward the same port(s) on two different machines on their network. Now for the bad news. I hope all reading have ALOT of RAM. I have 12GB Windows Home and after a month of chaining have gone from 5GB used to 10GB used. I will run out of RAM soon. So just add more RAM right? Wrong! Windows Home allows a max of 16GB RAM. So unless you have Windows Pro, and have $800 to blow on 64GB RAM, we may be wasting our time. A program called VMmem is using 3GB alone. This "Docker" thing seems to be more trouble than it is worth. The Tech guys I talk to said they stopped using it between 2017-2018. Now for the BAD news...got the "time to push the button" on my phone to keep mining. It is dead and goes into an infinite loop, then comes back with a "We are having trouble with our servers" message, "Please try later" and then a "Try Later" button. Seems like there is trouble in Paradise. Is it a funding issue? And how are we going to get to 100 million users when we are at 17 million? At this rate, and with competition like "Bee", I have alot of doubts. This install stuff is a crock. I have a degree in Computer Science and I am having trouble, what are 100 million going to do? "Try again later". Main Net is a long way away. My biggest issues are that they are ignoring the RAM issue because there are not alot of long term blockchainers right now, and the deafening sound of silence when it comes to support issues. Everyone is so worried about KYC. It will be pointless when you run out of RAM....

[ihatejam]

@ghcassidy I suspect that your config is fine - else you would not have been able to get to the part where the consensus is running (or trying to) without the ports being forwarded correctly -- your port forwarding could of course since have been undone. To confirm whether port forwarding is still fine, go back to the port checking screen and run the port forward test, it should load the "stellar-dummy" container -- while that is running go to https://www.ipfingerprints.com/portscan.php to see if it reports your ports are open. I would expect that it is if you've come this far. If they are indeed open, then move on to the next step, else check to see if your Mac has new DHCP-assigned IP address - if so, reserve it in your DHCP config (setting a static IP on a portable/laptop is not advised so DHCP reservation would be the way to go)

Next - move on and flip the node switch back to On (will show as red when On) - The "stellar-dummy" container should stop running and it should attempt to restart the consensus container (I expect it will fail still at this point). What I would do then is to tap the "Remove all blockchain link" on the troubleshooting page (I reckon everyone should do this part if they've upgraded from Node 0.4.3 or earlier)

Let me know if that helps or if the stellar-core still keeps exiting. Below is what you should end up with:-

[ihatejam]

@pilgrim103 1) There is no dependency on reaching 100M users for Pi to kick-off Phase 3. The Pi Core Team aim to kick off the mainnet/Phase 3 at the end of this year irrespective of the user count. 2) Unlike the port-testing container (stellar-dummy) which listens on all 10 ports (31400 - 31409), the current consensus container only listens on 31401-31403. 3) You cannot forward traffic aimed at a port on your public IP address to two different machines on your internal network- it doesn't matter which router you have. The only way would be to have the source hit the public IP address (with traffic destined for the second PC) on a different port and then route/forward the traffic from that "different port" to the one you want to use internally. A way around it would be to use VPN on any additional Node added in your network. (Possibly not worth the cost since there is currently no reward for running a node, unless you are dead set on helping with the testnet). 4) The Node does not use that much RAM nor does it use much of the CPU -- this is a pic from the Docker stats screen on the pi-consensus container showing the CPU and RAM usage:-

5) my troubleshooting screen does not list any port number after the word "running"

[ghcassidy]

@ihatejam Thank you very much for your detail response! After I clicked "Remove all blockchain Data" It started to sync up from blockchain 1 and the state is showing "Catching up" instead of N/A now. I will wait for couple hours to see if there is any update to sync up.

[steeveee100]

Congratulations!!

On Thu, 13 May 2021 at 00:19, ghcassidy @.***> wrote:

@ihatejam https://github.com/ihatejam Thank you very much for your detail response! After I clicked "Remove all blockchain Data" It started to sync up from blockchain 1 and the state is showing "Catching up" instead of N/A now. I will wait for couple hours to see if there is any update to sync up.

[image: Screen Shot 2021-05-12 at 13 28 23] https://user-images.githubusercontent.com/44917964/118021591-69809e80-b329-11eb-907f-7ea28dfc2664.png

[image: Screen Shot 2021-05-12 at 13 53 54] https://user-images.githubusercontent.com/44917964/118021694-82894f80-b329-11eb-9c0a-7d6600220969.png

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

[ihatejam]

@ghcassidy glad i was able to help -- i expect it to have caught up to the latest block about 30 minutes after you posted this update!?

[ihatejam]

@RoBoLilly apologies - i seem to have missed your response to my offer of help via Teamviewer. If you're still having issues, please let me know.

[ghcassidy]

@ihatejam yes, It's took me around 30 mins to 1 hour to sync up to latest blockchain. It's running fine now. During the time when I click "Check Now" to check ports, I spent quite some time, somehow the ports are randomly showing open or not open. I just kept trying to click it until seeing all ports are open.

[ihatejam]

@ghcassidy Sounds good. I tend to not rely on the built in port checker - IMHO the timeout is too short on it so it misreports. You'll find that ipfingerprints does a better job of it.

[yahyagara]

@ghcassidy I suspect that your config is fine - else you would not have been able to get to the part where the consensus is running (or trying to) without the ports being forwarded correctly -- your port forwarding could of course since have been undone. To confirm whether port forwarding is still fine, go back to the port checking screen and run the port forward test, it should load the "stellar-dummy" container -- while that is running go to https://www.ipfingerprints.com/portscan.php to see if it reports your ports are open. I would expect that it is if you've come this far. If they are indeed open, then move on to the next step, else check to see if your Mac has new DHCP-assigned IP address - if so, reserve it in your DHCP config (setting a static IP on a portable/laptop is not advised so DHCP reservation would be the way to go)

Next - move on and flip the node switch back to On (will show as red when On) - The "stellar-dummy" container should stop running and it should attempt to restart the consensus container (I expect it will fail still at this point). What I would do then is to tap the "Remove all blockchain link" on the troubleshooting page (I reckon everyone should do this part if they've upgraded from Node 0.4.3 or earlier)

Let me know if that helps or if the stellar-core still keeps exiting. Below is what you should end up with:-

@ihatejam many thanks .. solved by remove all blockchain link. just one problem support other node still ( no ) statue

[EarthBoundX5]

Just wanted to add that I too have had this exact same problem with my installation.

I've only seen this since the day I installed the pi node and have assumed it's correct, but reading reddit and others it seems to be no the case.

Here is my Diagnostics screen.