Pi Node local block number stopped moving

[hellohp-Ping]

Pi Node local block number stopped to synchronize. I have tried everything, reinstalling docker, removing all block data, it is still not moving.

Does anyone have solution for the issue

Thanks

[steeveee100]

Hi. I have exactly the same issue for last 3 days. Proves its not our setup anyways.

Sent from my iPhone

On 3 Oct 2021, at 20:15, hellohp-Ping @.***> wrote:

 Pi Node local block number stopped to synchronize. I have tried everything, reinstalling docker, removing all block data, it is still not moving.

Does anyone have solution for the issue

Thanks

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

[gjstein101]

Same problem.

[adwards74]

same problem too. I had this problem a week ago.

[sufitdi]

Same problem. All ok, but stopped...

[steeveee100]

Hey guys. We really need the thoughts of ihatejam on this.

[hellohp-Ping]

Yes, everything seems fine except local block number stopped moving. Last nite, I also verified all the ports and they are wide open. I don't see any CPU, memory and disk issue. I felt that it could be system wide issue.

[nathusius]

Same here too, block number stopped updating about a week ago, tried a few PC re-starts which didn't help, then deleted all local blockchain info and now I am stuck on block #1, doh!! But I do have incoming & outgoing connections as normal, so I wonder if it is somehow just a reporting error maybe, as the node appears to be working as normal otherwise? Docker did get an update recently, so could this be an issue? Yes, would be good to get the view of @ihatejam on this one!

[sufitdi]

no way, i checked everything, ports at main router, ip address, ports at all webpages that scan ports everything ok, ok with firewall, etc. it connects perfect but dont update for days now.

[sufitdi]

my connection is really fast, always update very fast... so now... :-( Please @ihatejam have a look asap... please.

my docker desltop made a few updates.... i keep thinking will be because of that.... dont know anyway....

[Gemzerella]

I have exactly this problem too, says it's syncing but no blocks :-(

[thankboy]

find the config stellar-core.cfg file at C:\Users{your user name folder}\AppData\Roaming\Pi Network\docker_volumes\stellar\core\etc

open this file, and add this content at the end of the file,then restart your computer and start the node, it will be catch up the new block. [HISTORY.custom] get="curl -sf 161.35.227.224:31403/{0} -o {1}"

图片

[adwards74]

find the config stellar-core.cfg file at C:\Users{your user name folder}\AppData\Roaming\Pi Network\docker_volumes\stellar\core\etc

open this file, and add this content at the end of the file,then restart your computer and start the node, it will be catch up the new block. [HISTORY.custom] get="curl -sf http://144.126.242.168:31403/{0} -o {1}"

图片

Why is the IP location you provided Singapore? The address originally provided is https://history.testnet.minepi.com . You need a source and clarification for this source.

[adwards74]

After asking through MOD, we received the following answers, so please refer to it.

Re:// Many thanks. I saw that circulating in Chinese community. I have reported it to CT two times. Anyway, it doesn't make too much sense to me to change that URL, also could be labelled by CT as bad actors. Let's wait for answers from CT.

[thankboy]

find the config stellar-core.cfg file at C:\Users{your user name folder}\AppData\Roaming\Pi Network\docker_volumes\stellar\core\etc open this file, and add this content at the end of the file,then restart your computer and start the node, it will be catch up the new block. [HISTORY.custom] get="curl -sf http://144.126.242.168:31403/{0} -o {1}" 图片

Why is the IP location you provided Singapore? The address originally provided is https://history.testnet.minepi.com . You need a source and clarification for this source.

who tell you this ip location is singapore? it is CT server ip!

[sufitdi]

get="curl -sf http://144.126.242.168:31403/{0} -o {1}"

didnt worked for me, still the same.

[adameveada]

I've had the same problem since Oct. 3rd.

[steeveee100]

Still no answers from CT!!

[thankboy]

get="curl -sf http://144.126.242.168:31403/{0} -o {1}"

没有为我工作，还是一样。

where are you come from? use http://161.35.227.224:31403/{0} -o {1} , and try agin. don't forget restart your computer!

[gjstein101]

This is getting to the point of no return! Still no answer from CT - makes me wonder!

[hellohp-Ping]

I start to believe this is working as designed. No fix is needed.

[gjstein101]

Hellohp-Ping - so your local block numbers have started to catch up without doing anything. Anyone else seen updated local block numbers?

[hellohp-Ping]

My local block still stay at 1, not moving at all !

[Felianthus]

Same problem as described -> Local block stays at 1, not moving at all! Until mid of September everything was working fine...

[sufitdi]

Still the same, we believed in the project, we supported them with a machine 24/7 we pay electricity (too expensive now in Spain) and what we get? nothing. .. no support, no help, nothing. That talks very bad about Pi Blockchain.... really bad.

[KTM250xcw]

I am seeing the same thing as well. I was running fine then all of a sudden it stopped. I have rechecked all settings locally and on the network (no changes on the network either). I have cleared all blockchain data a few times and let it sit for a long time - no change. Also not a fan of no update or word from the core team or Mods. Needs to be addressed or at minimum told as to what changed and why if this is expected.

[gjstein101]

LTM250xcw - I agree - core team need to step up to the plate.... we need some type of explanation as to why or a fix to this problem.

[sufitdi]

i found more people like us:

https://www.reddit.com/r/PiNetwork/comments/pzzbcr/there_seems_to_be_a_widespread_issue_with_nodes/

https://www.reddit.com/r/PiNetwork/comments/q00tip/pi_node_not_syncing/

wow.... i can not trust Pi project if they can not fix this.... maybe project too big for them....

[KTM250xcw]

i found more people like us:

https://www.reddit.com/r/PiNetwork/comments/pzzbcr/there_seems_to_be_a_widespread_issue_with_nodes/

https://www.reddit.com/r/PiNetwork/comments/q00tip/pi_node_not_syncing/

wow.... i can not trust Pi project if they can not fix this.... maybe project too big for them....

Great finds. I'll drop my post in those as well. If the cert is expired as that one log indicates that should be a fairly easy fix. Wish there was a way to get the core teams/mods attention easier

[hellohp-Ping]

I noticed today that my Availability (90 days) comes back after disappearing around the same time of local block number.

[gjstein101]

My availability has also updated but not the local block number.

[sufitdi]

My availability has also updated but not the local block number.

[gjstein101]

I have read on other forums it could be a lapsed certificate. If that is the case, why have we not been notified of this problem and the corrective action they are taking. That is all it would take to build some confidence.

[hellohp-Ping]

Just found out that the local block number started moving again !

[KTM250xcw]

Awesome I'll fire it back up and see what happens. Thanks for the update!

[nathusius]

Mine appears to be working as expected again now, it reports as being sync'd to latest block and availability is up-to-date too - it only took about three weeks to get sorted!!

[KTM250xcw]

Working for me now as well.

[sufitdi]

not for me.... :-(

Did you removed all blockchain data?

[gjstein101]

I did remove all of the blockchain data when it was not updating and now my local block numbers are up-to-date with the latest block numbers. I also noticed my availability has started to increase where in the past always declined even though I been running 24-7 since March 2, 21. Looks like things are back on track.

[nathusius]

I also removed all blockchain data, then it sat on block 1 for weeks, so no idea if doing that actually helped or not, but all good now. Availability also increasing (slowly) for me now too, rather than dropping; but it's still only at 72%, even though PC has been on 24/7 for months now!

[steeveee100]

Wow! I'm suddenly back up and running again. Guess we'll never know what it was about.

[sufitdi]

not for me...

[hellohp-Ping]

Did you install new version of docker?

[steeveee100]

I just use version 4.1.1 of docker desktop.

[KTM250xcw]

Same I'm on v4.1.1. While I was troubleshooting I downgraded to v4. As upgrading to v4.1.1 was the last thing I changed. But it happened to be just be a coincidence. 

[Gemzerella]

My node has had exactly the same issues as detailed above, it suddenly stopped and hasn't worked again until this evening.

I checked the Docker and when I tried to start it up, I received this message:

(HTTP code 500) server error - Ports are not available: listen tcp 0.0.0.0:31403: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

After a bit of Googling, I found a known fix, to run a command prompt to turn winnat off, start the Docker container and then turn it back on.

Has worked for me. Another example of Windows 10 updates screwing it up IMO, I see this a lot at work.

[thankboy]

Not yet

从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送

发件人: @.> 发送时间: 2021年10月31日 1:09 收件人: @.> 抄送: @.>; @.> 主题: Re: [pi-node/instructions] Pi Node local block number stopped moving (#184)

Did you install new version of docker?

― You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/pi-node/instructions/issues/184#issuecomment-955498380, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFADXVS6D52HIZKDVO25YKDUJQRFRANCNFSM5FH5NXAA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[uwegrille]

Mein Knoten hatte genau die gleichen Probleme wie oben beschrieben, er hörte plötzlich auf und hat bis heute Abend nicht mehr funktioniert.

Ich habe das Docker überprüft und als ich versucht habe, es zu starten, habe ich diese Meldung erhalten:

(HTTP-Code 500) Serverfehler - Ports sind nicht verfügbar: listen tcp 0.0.0.0:31403: bind: Es wurde versucht, auf einen Socket in einer Weise zuzugreifen, die durch seine Zugriffsberechtigungen verboten ist.

Nachdem ich ein wenig gegoogelt hatte, fand ich eine bekannte Lösung, um eine Eingabeaufforderung zum Deaktivieren von Winnat auszuführen, den Docker-Container zu starten und dann wieder einzuschalten.

Hat bei mir funktioniert. Ein weiteres Beispiel für Windows 10-Updates, die es IMO vermasseln, ich sehe das oft bei der Arbeit.

Habe Docker AMD installiert, für AMD Chip, jetzt rennt Pi Node

[uwegrille]

Keine Updates mehr machen, für Docker!

[uwegrille]

Ausser es gibt ein Update, für Docker AMD Chip!