Open davidch8686 opened 11 months ago
Seems it is able to connected to peers.
2023-12-29T20:51:36.887265Z WARN Unable to connect to '35.224.50.150:4133' - Connection reset by peer (os error 104) 2023-12-29T20:51:37.013954Z INFO Coinbase Puzzle (Epoch 2974, Block 1070690, Coinbase Target 4302897150, Proof Target 33616384) 2023-12-29T20:51:37.030179Z DEBUG Connecting to 183.99.121.41:4133... 2023-12-29T20:51:37.051905Z WARN Unable to connect to '118.36.228.252:39055' - Connection refused (os error 111) 2023-12-29T20:51:37.429280Z INFO Connected to '183.99.121.41:4133' 2023-12-29T20:51:39.635521Z WARN Disconnecting from '8.219.145.250:4133' - PeerRefresh 2023-12-29T20:52:01.833228Z DEBUG Connected to 7 peers [161.97.103.67:4133, 46.105.76.234:4133, 203.176.232.131:4133, 51.81.176.217:44133, 212.126.35.133:4133, 183.99.121.41:4133, 15.235.53.79:4133] 2023-12-29T20:52:01.833312Z INFO Disconnecting from '203.176.232.131:4133' (periodic refresh of peers) 2023-12-29T20:52:01.903667Z DEBUG Connecting to 35.227.159.141:4133... 2023-12-29T20:52:01.942216Z INFO Coinbase Puzzle (Epoch 2974, Block 1070692, Coinbase Target 4294967295, Proof Target 33554432)
Based on this log, does it mean I am actively helping proving the network?
Is the problem solved?
I am not sure if that is working properly. What is the expected logs? I shared the log above. Seems i can connect to peers, but it does not see it help the network solving puzzles(the account does not get any credit, my understanding is if it helps solving puzzles, that will reward credit).
the same problem 2024-01-31T16:25:36.871716Z WARN Unable to connect to '34.150.221.166:4133' - Connection reset by peer (os error 104) 2024-01-31T16:26:01.383846Z DEBUG No connected peers 2024-01-31T16:26:01.604806Z DEBUG Connecting to 34.150.221.166:4133... 2024-01-31T16:26:03.260006Z WARN Unable to connect to '34.150.221.166:4133' - Connection reset by peer (os error 104) 2024-01-31T16:26:26.385503Z DEBUG No connected peers 2024-01-31T16:26:26.551694Z DEBUG Connecting to 35.227.159.141:4133... 2024-01-31T16:26:26.715956Z WARN Unable to connect to '35.227.159.141:4133' - Connection reset by peer (os error 104) 2024-01-31T16:26:51.386243Z DEBUG No connected peers 2024-01-31T16:26:51.631247Z DEBUG Connecting to 35.224.50.150:4133... 2024-01-31T16:26:52.030366Z WARN Unable to connect to '35.224.50.150:4133' - Connection reset by peer (os error 104) 2024-01-31T16:27:16.387731Z DEBUG No connected peers 2024-01-31T16:27:16.609314Z DEBUG Connecting to 34.139.203.87:4133... 2024-01-31T16:27:16.831734Z WARN Unable to connect to '34.139.203.87:4133' - Connection reset by peer (os error 104) 2024-01-31T16:27:41.390327Z DEBUG No connected peers 2024-01-31T16:27:41.637473Z DEBUG Connecting to 34.150.221.166:4133... 2024-01-31T16:27:41.882489Z WARN Unable to connect to '34.150.221.166:4133' - Connection reset by peer (os error 104) 2024-01-31T16:28:06.391994Z DEBUG No connected peers 2024-01-31T16:28:06.590511Z DEBUG Connecting to 35.224.50.150:4133... 2024-01-31T16:28:06.792256Z WARN Unable to connect to '35.224.50.150:4133' - '35.224.50.150:4133' disconnected before sending "Message::ChallengeResponse"
related to #3011
me too
🐛 Bug Report
2023-12-29T15:06:22.278809Z DEBUG No connected peers 2023-12-29T15:06:22.309149Z DEBUG Connecting to 35.224.50.150:4133... 2023-12-29T15:06:24.083090Z WARN Unable to connect to '35.224.50.150:4133' - Connection reset by peer (os error 104) 2023-12-29T15:06:47.279772Z DEBUG No connected peers 2023-12-29T15:06:47.304883Z DEBUG Connecting to 34.150.221.166:4133... 2023-12-29T15:06:47.328420Z WARN Unable to connect to '34.150.221.166:4133' - '34.150.221.166:4133' disconnected before sending "Message::ChallengeResponse"
Steps to Reproduce
Just run
./run-prover.sh
Expected Behavior
Your Environment