snarkOS icon indicating copy to clipboard operation
snarkOS copied to clipboard

Published 20 hours ago • verified publisher icon AleoNet

prover Failed to connect a peer.

Open johnnychen8188 opened this issue 2 years ago • 4 comments

I compiled the latest code and tried to run prover, but the log showed that I could not connect to the peer. I checked the network of my local firewall, and there was no problem. How to solve this situation? The log is as follows: 2022-12-02T04:56:42.588375Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:56:47.587455Z DEBUG No connected peers 2022-12-02T04:56:47.587517Z DEBUG Connecting to 164.92.111.59:4133... 2022-12-02T04:56:47.788952Z WARN Connection refused (os error 111) 2022-12-02T04:57:02.588925Z DEBUG No connected peers 2022-12-02T04:57:02.588989Z DEBUG Connecting to 138.68.103.139:4133... 2022-12-02T04:57:02.835167Z DEBUG Received a connection request from '138.68.103.139:4133' 2022-12-02T04:57:02.835229Z TRACE Sending 'ChallengeRequest-A' to '138.68.103.139:4133' 2022-12-02T04:57:03.095912Z WARN Connection reset by peer (os error 104) 2022-12-02T04:57:07.599857Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:07.599895Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:07.599904Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:07.599862Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:07.599910Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:07.599922Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:12.859929Z WARN Connection timed out (os error 110) 2022-12-02T04:57:17.590066Z DEBUG No connected peers 2022-12-02T04:57:17.590296Z DEBUG Connecting to 161.35.24.55:4133... 2022-12-02T04:57:17.843137Z DEBUG Received a connection request from '161.35.24.55:4133' 2022-12-02T04:57:17.843183Z TRACE Sending 'ChallengeRequest-A' to '161.35.24.55:4133' 2022-12-02T04:57:18.096189Z WARN Connection reset by peer (os error 104) 2022-12-02T04:57:32.591123Z DEBUG No connected peers 2022-12-02T04:57:32.591408Z DEBUG Connecting to 167.71.219.176:4133... 2022-12-02T04:57:32.600637Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:32.600677Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:32.600695Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:32.600711Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:32.600725Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:32.600741Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:47.593475Z DEBUG No connected peers 2022-12-02T04:57:47.593555Z DEBUG Connecting to 207.154.215.49:4133... 2022-12-02T04:57:47.847980Z DEBUG Received a connection request from '207.154.215.49:4133' 2022-12-02T04:57:47.848041Z TRACE Sending 'ChallengeRequest-A' to '207.154.215.49:4133' 2022-12-02T04:57:48.101503Z WARN '207.154.215.49:4133' did not send a challenge request 2022-12-02T04:57:57.601600Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:57.601656Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:57.601665Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:57.601672Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:57.601685Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:57:57.601696Z TRACE Skipping an iteration of the coinbase puzzle (no connected peers) 2022-12-02T04:58:02.595030Z DEBUG No connected peers 2022-12-02T04:58:02.595103Z DEBUG Connecting to 157.245.205.209:4133... 2022-12-02T04:58:02.661189Z DEBUG Received a connection request from '157.245.205.209:4133' 2022-12-02T04:58:02.661234Z TRACE Sending 'ChallengeRequest-A' to '157.245.205.209:4133' 2022-12-02T04:58:02.727398Z WARN Connection reset by peer (os error 104)

Is the problem that the server reaches a performance limit and fails to connect? Or have I looked up something that tells me that if the node is not trusted, there will be this exception, how do I solve this problem?

johnnychen8188 avatar Dec 02 '22 04:12 johnnychen8188

It seems like your peers are dropping your connection. Are you running the latest version of snarkOS?

niklaslong avatar Dec 02 '22 15:12 niklaslong

@johnnychen8188 I would git pull and try again. The logs seem to me like the node is running an older version.

howardwu avatar Dec 04 '22 19:12 howardwu

It seems like your peers are dropping your connection. Are you running the latest version of snarkOS?

Let me try git pull again. thank you

johnnychen8188 avatar Dec 05 '22 11:12 johnnychen8188

@johnnychen8188 I would git pull and try again. The logs seem to me like the node is running an older version.

Thank you help.

johnnychen8188 avatar Dec 05 '22 11:12 johnnychen8188

Closing, as it seems that this has been fixed. Feel free to reopen if the issue resurfaces.

ljedrz avatar Dec 19 '22 11:12 ljedrz