RuntimeError: Weight proof did not arrive in time from peer

[Jily-Zhu]

2021-06-30T14:40:52.549 full_node chia.full_node.full_node: ERROR Error with syncing: <class 'RuntimeError'>Traceback (most recent call last):
File "chia\full_node\full_node.py", line 640, in _sync
RuntimeError: Weight proof did not arrive in time from peer: 76.201.87.186

[devtestnet]

• Fddgictw@@@is ax JN tesgg th j egg ujj in n hmm zuarad

[loppefaaret]

listen @devtestnet if you don't start pulling yourself together, and start posting anything remotely understandable, we are going to have to remove your access to our github!

[devtestnet]

Please do so

[loppefaaret]

just means it had a timeout waiting for data, from that peer, it will try another peer - try and give it some time to get it all fixed up!

[loppefaaret]

yes, give it a bit of time, and see if it cant get pass this it self - the alternative is very disruptive

[loppefaaret]

do you have any that are passed 480666 ? you could close down one that are passed that block, and synced, and take a copy of its blockchain database, and distribute it to other clients manually

[Jily-Zhu]

No, all of them stay at the same height, 480666

[loppefaaret]

damn... ok, i hope you get one of them pass it 🤞

[Jily-Zhu]

thank you for your kindness

[devtestnet]

Bahachina was the 1 to send me the bot trading concept with some fillers users but I didn't used it as my friend MR Dinesh Sharma is already into this type of seen.

Just want and information that what ia this happening.

Can do hard work but I feel that people are trading and swapping their nearer and dearer @. I cannot do this work. So I request you to be straight and clear. git GOT community support and then I am coming backwards.

And it's any special warning for all those who are doing all this.

Playing with an emotion of humanity is just and will be infront of mtggyf cry sjeuctcfhsapwmnmbzbbdhrukwb

Reply stop ✋ must

As if my mentors SAT @IN DOWN A CHAIR AND U  WILL KNOW the all platform will fucked off.

My name is Deepak Gusain. And will not hide from anyone.

And one more thing cross platform should be known understand before start. Ink think of sink.. Jai Mata Di!
. BB dbs d bhej. Na s

Please go further with my thought blessed by you all @ almighty.

• uuuqsaew

I just forwarded you and my three friend.

Should I open AC in this as it's not looking so ********

[devtestnet]

And just keep in your mind. Whatsoever is going around me is all done 100% by me but I was not know to this. Aage aage Dekho hota Hai Kya, wrong doing by knowing is @me [email protected]

Now you have to give complete explanation and one two one ☝️- discussion. GoD knows what I went with me.

If I will be wrong then I am ready to accept it.

So before trade, swap and any illegal work got to be find done by anyone will BE INFRONT OF ME(deepak Gusain).

followed by all

[BrandtH22]

Since this issue has been open for a number of years without additional comments, we will be closing this ticket but if we have closed this ticket in error do not hesitate to reach out to us again with any followup questions, comments, or if the issue persists after an update.

Please note that upgrading major versions of chia generally requires the config.yaml to be recreated using these steps:
1. Stop chia
2. Rename the config or move it to a different directory
3. In CLI run chia init
4. Copy any custom settings from the old config to the new (plot drive directories, pool info, trusted node info, etc) - be careful here as yaml is very picky about formatting including those leading spaces
5. Start Chia

The best place to reach our support team is on Discord (https://discord.gg/chia) or by reopening this ticket.