search

kaspanet / kaspad

Kaspad is the reference full node Kaspa implementation written in Go (golang).
ISC License
436 stars 225 forks source link

loop: the proposed pruning point is the same as the current pruning point #2231

Open daro84b opened 7 months ago

daro84b commented 7 months ago

Hi, does anybody know why I cant finally sync the whole node? It seems like there are only 20k blocks from the last one synced in my node and the current one.

I restarted node, server, i tried everything and after I launch kaspad it keeps looping each peer looking up for a new pruning point without success, because kaspad disconnects from each peer with the same message the proposed pruning point is the same as the current pruning point

`2023-11-14 21:55:06.584 [INF] PPMN: Applying level 219 from the pruning point proof 2023-11-14 21:55:06.584 [INF] PPMN: Applying level 219 from the pruning point proof - applied 0 headers out of 1 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 220 from the pruning point proof 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 220 from the pruning point proof - applied 0 headers out of 1 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 221 from the pruning point proof 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 221 from the pruning point proof - applied 0 headers out of 1 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 222 from the pruning point proof 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 222 from the pruning point proof - applied 0 headers out of 1 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 223 from the pruning point proof 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 223 from the pruning point proof - applied 0 headers out of 1 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 224 from the pruning point proof 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 224 from the pruning point proof - applied 0 headers out of 1 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 225 from the pruning point proof 2023-11-14 21:55:06.585 [INF] PPMN: Applying level 225 from the pruning point proof - applied 0 headers out of 1 2023-11-14 21:55:06.586 [INF] BDAG: Done applying the pruning point proof 2023-11-14 21:55:06.586 [INF] PROT: Downloading the past pruning points and the pruning point anticone from <d765c76d9476c27bcc3fc3a19677c863: 104.136.180.204:16111> 2023-11-14 21:55:06.586 [INF] PROT: IBD with pruning proof from <d765c76d9476c27bcc3fc3a19677c863: 104.136.180.204:16111> was unsuccessful. Deleting the staging consensus. (the proposed pruning point is the same as the current pruning point) 2023-11-14 21:55:06.586 [INF] PRFX: Deleting database prefix &{0} 2023-11-14 21:55:07.604 [INF] PRFX: Compacting database after prefix delete 2023-11-14 21:55:07.940 [INF] PROT: IBD with peer <d765c76d9476c27bcc3fc3a19677c863: 104.136.180.204:16111> finished (interrupted: the proposed pruning point is the same as the current pruning point) 2023-11-14 21:55:07.940 [ERR] PROT: Non-critical peer protocol error from HandleIBD, printing the full stack for debug purposes:

the proposed pruning point is the same as the current pruning point

2023-11-14 21:55:07.940 [INF] PROT: Disconnecting from <d765c76d9476c27bcc3fc3a19677c863: 104.136.180.204:16111> (reason: the proposed pruning point is the same as the current pruning point) 2023-11-14 21:55:08.781 [INF] NTAR: Disconnected from <d765c76d9476c27bcc3fc3a19677c863: 104.136.180.204:16111> 2023-11-14 21:55:08.905 [INF] CMGR: Connecting to [2603:8081:1401:7dbd:3814:7282:384f:49b2]:16111 2023-11-14 21:55:08.905 [INF] CMGR: Connecting to [2603:8081:1401:7dbd:3814:7282:384f:49b2]:16111 2023-11-14 21:55:09.451 [INF] PROT: IBD started with peer <7c62bfa8c7395d64afa181483638b6ab: 54.78.82.207:16111> 2023-11-14 21:55:09.451 [INF] PROT: IBD started with peer <7c62bfa8c7395d64afa181483638b6ab: 54.78.82.207:16111> and relayBlockHash 227e61ccbba142a79f8a2bbe70f560ab5d9329f4a01fd0761ba0c46f0002e28b 2023-11-14 21:55:09.451 [INF] PROT: Syncing blocks up to 227e61ccbba142a79f8a2bbe70f560ab5d9329f4a01fd0761ba0c46f0002e28b 2023-11-14 21:55:09.452 [INF] PROT: Trying to find highest known syncer chain block from peer <7c62bfa8c7395d64afa181483638b6ab: 54.78.82.207:16111> with relay hash 227e61ccbba142a79f8a2bbe70f560ab5d9329f4a01fd0761ba0c46f0002e28b 2023-11-14 21:55:09.575 [INF] PROT: Found highest known syncer chain block 77430fe710c20c9defe489c59f5e8444639c3c941a0e29351cfb1129643bd3d2 from peer <7c62bfa8c7395d64afa181483638b6ab: 54.78.82.207:16111> 2023-11-14 21:55:09.575 [INF] PROT: Starting IBD with headers proof 2023-11-14 21:55:09.698 [INF] PROT: Downloading the pruning point proof from <7c62bfa8c7395d64afa181483638b6ab: 54.78.82.207:16111> 2023-11-14 21:55:09.906 [INF] CMGR: Connecting to 22.36.181.5:16311 2023-11-14 21:55:10.907 [INF] CMGR: Connecting to [240e:35d:884:ae00:507d:81e3:d124:a847]:16111 2023-11-14 21:55:11.908 [INF] CMGR: Connecting to 66.131.34.50:16111 2023-11-14 21:55:12.128 [INF] TXMP: P2P Connected to 66.131.34.50:16111 2023-11-14 21:55:12.245 [INF] PROT: Registering p2p flows for peer <605b83166d075265c3ee10ccd0101028: 66.131.34.50:16111> for protocol version 5`

and then it loops again starting from the same point

2023-11-14 21:55:27.577 [INF] PPMN: Validating level 28 from the pruning point proof 2023-11-14 21:55:28.336 [INF] PPMN: Validating level 27 from the pruning point proof 2023-11-14 21:55:29.241 [INF] PPMN: Validating level 26 from the pruning point proof 2023-11-14 21:55:30.801 [INF] PPMN: Validating level 25 from the pruning point proof 2023-11-14 21:55:31.708 [INF] PPMN: Validating level 24 from the pruning point proof 2023-11-14 21:55:32.504 [INF] PPMN: Validating level 23 from the pruning point proof 2023-11-14 21:55:33.352 [INF] PPMN: Validating level 22 from the pruning point proof 2023-11-14 21:55:34.027 [INF] PPMN: Validating level 21 from the pruning point proof 2023-11-14 21:55:34.612 [INF] PPMN: Validating level 20 from the pruning point proof 2023-11-14 21:55:35.842 [INF] PPMN: Validating level 19 from the pruning point proof 2023-11-14 21:55:36.483 [INF] PPMN: Validating level 18 from the pruning point proof 2023-11-14 21:55:37.056 [INF] PPMN: Validating level 17 from the pruning point proof 2023-11-14 21:55:37.631 [INF] PPMN: Validating level 16 from the pruning point proof 2023-11-14 21:55:38.315 [INF] PPMN: Validating level 15 from the pruning point proof 2023-11-14 21:55:38.854 [INF] PPMN: Validating level 14 from the pruning point proof 2023-11-14 21:55:38.907 [INF] CMGR: Connecting to 107.167.5.124:16111 2023-11-14 21:55:39.389 [INF] PPMN: Validating level 13 from the pruning point proof 2023-11-14 21:55:39.909 [INF] CMGR: Connecting to [2a00:a040:1a0:e70d:c8bf:1628:105b:78ca]:16111 2023-11-14 21:55:39.923 [INF] PPMN: Validating level 12 from the pruning point proof 2023-11-14 21:55:40.463 [INF] PPMN: Validating level 11 from the pruning point proof 2023-11-14 21:55:40.909 [INF] CMGR: Connecting to [240e:36b:18cd:6e00:1f54:a977:fe77:e41d]:16111 2023-11-14 21:55:41.008 [INF] PPMN: Validating level 10 from the pruning point proof 2023-11-14 21:55:41.536 [INF] PPMN: Validating level 9 from the pruning point proof 2023-11-14 21:55:42.078 [INF] PPMN: Validating level 8 from the pruning point proof 2023-11-14 21:55:42.635 [INF] PPMN: Validating level 7 from the pruning point proof 2023-11-14 21:55:43.186 [INF] PPMN: Validating level 6 from the pruning point proof 2023-11-14 21:55:43.904 [INF] PPMN: Validating level 5 from the pruning point proof 2023-11-14 21:55:44.478 [INF] PPMN: Validating level 4 from the pruning point proof 2023-11-14 21:55:45.046 [INF] PPMN: Validating level 3 from the pruning point proof 2023-11-14 21:55:45.615 [INF] PPMN: Validating level 2 from the pruning point proof 2023-11-14 21:55:46.211 [INF] PPMN: Validating level 1 from the pruning point proof 2023-11-14 21:55:46.780 [INF] PPMN: Validating level 0 from the pruning point proof 2023-11-14 21:55:47.355 [INF] BDAG: Done validating the pruning point proof 2023-11-14 21:55:47.355 [INF] BDAG: Applying the pruning point proof 2023-11-14 21:55:51.667 [INF] PPMN: Applying level 0 from the pruning point proof 2023-11-14 21:55:51.667 [INF] PPMN: Applying level 0 from the pruning point proof - applied 0 headers out of 2002 2023-11-14 21:55:51.741 [INF] PPMN: Applying level 0 from the pruning point proof - applied 1000 headers out of 2002 2023-11-14 21:55:51.814 [INF] PPMN: Applying level 0 from the pruning point proof - applied 2000 headers out of 2002

Any idea? maybe a peer with old data? a date&time error I checked date&time and it seems fine.

any help will be appreciated Thanks

collabothon commented 7 months ago

encountering the same issue:

2023-12-12 16:21:35.989 [INF] PROT: IBD with pruning proof from <c395fb6ced2a9236260762727dc276e1: 116.202.50.249:16111> was unsuccessful. Deleting the staging consensus. (the proposed pruning point is the same as the current pruning point) 2023-12-12 16:21:35.989 [INF] PRFX: Deleting database prefix &{0} 2023-12-12 16:21:36.220 [INF] CMGR: Connecting to [2409:8a34:1a37:2120:d4b6:6cc2:d05d:58a3]:16111 2023-12-12 16:21:36.657 [INF] PRFX: Compacting database after prefix delete 2023-12-12 16:21:36.980 [INF] PROT: IBD with peer <c395fb6ced2a9236260762727dc276e1: 116.202.50.249:16111> finished (interrupted: the proposed pruning point is the same as the current pruning point) 2023-12-12 16:21:36.980 [ERR] PROT: Non-critical peer protocol error from HandleIBD, printing the full stack for debug purposes:

the proposed pruning point is the same as the current pruning point

kaspad version 0.12.14 - December 12 2023

daro84b commented 6 months ago

encountering the same issue:

2023-12-12 16:21:35.989 [INF] PROT: IBD with pruning proof from <c395fb6ced2a9236260762727dc276e1: 116.202.50.249:16111> was unsuccessful. Deleting the staging consensus. (the proposed pruning point is the same as the current pruning point)

2023-12-12 16:21:35.989 [INF] PRFX: Deleting database prefix &{0} 2023-12-12 16:21:36.220 [INF] CMGR: Connecting to [2409:8a34:1a37:2120:d4b6:6cc2:d05d:58a3]:16111 2023-12-12 16:21:36.657 [INF] PRFX: Compacting database after prefix delete 2023-12-12 16:21:36.980 [INF] PROT: IBD with peer <c395fb6ced2a9236260762727dc276e1: 116.202.50.249:16111> finished (interrupted: the proposed pruning point is the same as the current pruning point) 2023-12-12 16:21:36.980 [ERR] PROT: Non-critical peer protocol error from HandleIBD, printing the full stack for debug purposes:

the proposed pruning point is the same as the current pruning point

kaspad version 0.12.14 - December 12 2023

I fixed it starting utxo with parameters -reset_db and -ban enable, try kaspad --help to get the exact parameter, I dont remember them now! Hope you fix it.