My node is stuck on an old block

I’ve restarted my node after some hour without run properly.

It seems stuck at block 510851 doing a lot of:

2022-03-24T10:06:54+01:00 - info: Matched 4 zeros 0000646372B1358D1BFFCAEA1F575E5EF2FC7F809422E11EE4CF307D7E81BCCF with Nonce = 10200006600172 for block#510851 by 2jztXx
2022-03-24T10:06:58+01:00 - info: Matched 4 zeros 0000A728083D414AE05023EE0F77BCD2A00022C8C7736CACDBA498B6063D440B with Nonce = 10200006634034 for block#510851 by 2jztXx
2022-03-24T10:06:59+01:00 - info: Matched 4 zeros 00001D65D16C03FCA07D9AD927584D99365703450E61EDD7081A1F8EE8601BA5 with Nonce = 10200006644112 for block#510851 by 2jztXx

I wonder why is it not synchronizing… (I think the latest block is 510952)
Well, I could sync just doing a « duniter sync node_ip:443 » but why if this happens when I don’t realize? Hasn’t a node able to sync for itself?

A more complete log

2022-03-24T10:14:04+01:00 - info: WS2P: init: bundle of peers 5/6
2022-03-24T10:14:04+01:00 - info: WS2P: connected to peer 4fHMTFBM using WS2P g1.help-web-low.fr 443!
2022-03-24T10:14:04+01:00 - info: WS2P: connected to peer 8Hz9bkC3 using WS2P g1.cloud-libre.eu 443!
2022-03-24T10:14:04+01:00 - info: WS2P: connected to peer 6dncYK2m using WS2P duniter.coinduf.eu 443!
2022-03-24T10:14:04+01:00 - info: WS2P: connected to peer 5UhU5aNc using WS2P g1.fdlibre.eu 443!
2022-03-24T10:14:06+01:00 - info: Matched 4 zeros 00002F4095AAF1C705CF02CFDBE176842E6531E7C38AB519E720ECEACEA3F67C with Nonce = 10100010321013 for block#510851 by 2jztXx
2022-03-24T10:14:06+01:00 - info: Matched 4 zeros 0000607ECC937F2FE4BA3EB414D5FE960AFC564BDAAA12BC611B6001C8D6AB41 with Nonce = 10100010323221 for block#510851 by 2jztXx
2022-03-24T10:14:13+01:00 - info: Matched 4 zeros 000041A72AA39D64641B90BA3E2E114959DCE6CA5D106941C58118E3F089E78F with Nonce = 10100010385957 for block#510851 by 2jztXx
2022-03-24T10:14:14+01:00 - info: Matched 4 zeros 0000DE837F64E9C23C8D00358F0A500CA89D758D38CEA183B5627BD1CA733520 with Nonce = 10100010396138 for block#510851 by 2jztXx
2022-03-24T10:14:18+01:00 - info: Matched 4 zeros 0000A7DCCA134B7CA838C52E1F3EFDA263AA2EF8B700626B85B27D8515F2760C with Nonce = 10100010435555 for block#510851 by 2jztXx
2022-03-24T10:14:19+01:00 - info: WS2P: Could not connect to peer 7F6oyFQy using WS2P vit.fdn.org 443: WS2P connection timeout
2022-03-24T10:14:19+01:00 - info: WS2P: init: bundle of peers 6/6
2022-03-24T10:14:19+01:00 - info: WS2P: connection [8Hz9bkC3 WS2P g1.cloud-libre.eu 443] has been closed
2022-03-24T10:14:19+01:00 - info: WS2P: connection [74RBUM4V WS2P monit.g1.nordstrom.duniter.org 443] has been closed
2022-03-24T10:14:19+01:00 - info: WS2P: connected to peer HnQH8P6n using WS2P panoramix.toutat.is 443!
2022-03-24T10:14:20+01:00 - info: Matched 4 zeros 000091F5E558A08F34E7E241DA271DF1CEBBDCADBF3F0FB644E1C863F80F0060 with Nonce = 10200010570556 for block#510851 by 2jztXx
2022-03-24T10:14:22+01:00 - info: Matched 4 zeros 000024C4250E4048042BD330DFA0DFE2D21572D43F4B023698B04BED184837F7 with Nonce = 10200010586112 for block#510851 by 2jztXx
2022-03-24T10:14:31+01:00 - info: Matched 4 zeros 00009D17031C8899162DF875E555EB632B9332B58DD08FCD7065E50CA5E5B1FC with Nonce = 10200010666577 for block#510851 by 2jztXx
2022-03-24T10:14:33+01:00 - info: Matched 4 zeros 00009CFA3A7F14503D15B739EC75891F96A4941EF53832A6C7C36C52CEB1C315 with Nonce = 10100010570218 for block#510851 by 2jztXx
2022-03-24T10:14:34+01:00 - info: WS2P: connection [6dncYK2m WS2P duniter.coinduf.eu 443] has been closed
2022-03-24T10:14:35+01:00 - info: WS2P: connection [5UhU5aNc WS2P g1.fdlibre.eu 443] has been closed
2022-03-24T10:14:35+01:00 - info: Matched 4 zeros 00002C0301FAF4BAEB1A89F74BF6713920D729D681D6F9C5BEE84C2E22495A59 with Nonce = 10100010588820 for block#510851 by 2jztXx
2022-03-24T10:14:36+01:00 - info: Matched 4 zeros 00004C26A9D6DBF894FD3E377E15619651580A56499999C387416A9AC08B26CE with Nonce = 10200010717342 for block#510851 by 2jztXx
2022-03-24T10:14:50+01:00 - info: Matched 4 zeros 00006EB6617C0FCAA82CD250417038DEC8FBE92640DE105764D19AF3F3FC3120 with Nonce = 10100010724562 for block#510851 by 2jztXx
2022-03-24T10:14:58+01:00 - info: Matched 4 zeros 0000A1DD254FC904D8E979F35C47801808D8529538939B2148F3579F4D9BA156 with Nonce = 10200010912304 for block#510851 by 2jztXx
2022-03-24T10:14:59+01:00 - info: Matched 4 zeros 0000A627E39122239D2B0EFF10F16A6C4207A7B2FF6A0BAEA1087E4E08A8FFBE with Nonce = 10200010913239 for block#510851 by 2jztXx
2022-03-24T10:14:59+01:00 - info: Matched 4 zeros 0000DA5056371923EC8E948168986E1F881D5C1A14154F163F4E0CC3D4AB699E with Nonce = 10100010807572 for block#510851 by 2jztXx
2022-03-24T10:15:01+01:00 - info: Matched 4 zeros 0000DB6CFFBB927F74DD0B11689EBB3CE9493549A6B9A1B5962B60B3FE464A05 with Nonce = 10200010937638 for block#510851 by 2jztXx
2022-03-24T10:15:02+01:00 - info: Matched 4 zeros 0000907E40379046BC0B41588A0D44068DA589375CE60842CCDE868C2612212A with Nonce = 10100010834662 for block#510851 by 2jztXx
2022-03-24T10:15:04+01:00 - info: WS2P: connection [4fHMTFBM WS2P g1.help-web-low.fr 443] has been closed
2022-03-24T10:15:07+01:00 - info: Matched 4 zeros 00001B33BD52A9B144B54901AC85945FB21965566D2E2C0C09FAADEB9E7F9920 with Nonce = 10100010877182 for block#510851 by 2jztXx
2022-03-24T10:15:13+01:00 - info: Matched 4 zeros 0000742B7BF69328620F7B2E9C8B22FCD6FCB63268C210C66D5BBE612796CB35 with Nonce = 10200011041883 for block#510851 by 2jztXx
2022-03-24T10:15:19+01:00 - info: WS2P: connection [HnQH8P6n WS2P panoramix.toutat.is 443] has been closed
2022-03-24T10:15:23+01:00 - info: SIDE Block #510962-00000016 added to the blockchain in 0 ms
2022-03-24T10:15:23+01:00 - info: Block resolution: 1 potential blocks after current#510850…
2022-03-24T10:15:24+01:00 - error: Error: ruleNumber
at Function.checkBlock (/opt/duniter/app/lib/blockchain/DuniterBlockchain.js:63:19)
at process._tickCallback (internal/process/next_tick.js:68:7)
2022-03-24T10:15:24+01:00 - info: Fork resolution: 66 potential block(s) found…
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510916-00000003 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510915-00000049 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510914-00000029 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510913-0000002A is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510912-0000003F is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510911-0000000A is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510910-00000004 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510909-00000002 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510908-0000002D is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510907-0000000C is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510906-00000010 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510905-00000010 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510904-00000025 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510903-00000003 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510902-00000013 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510901-00000009 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510900-0000002B is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510899-00000009 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510898-0000003B is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510897-00000026 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510896-00000043 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510895-00000013 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510894-00000009 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510893-00000018 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510892-0000003C is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510891-00000026 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510890-00000043 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510889-0000002F is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510888-00000006 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510887-0000001D is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510886-0000001A is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510885-00000025 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510884-00000044 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510883-00000018 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510882-00000009 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510881-00000012 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510880-00000004 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510879-00000048 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510878-00000007 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510877-00000012 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510876-00000014 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510875-0000004D is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510874-00000013 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510873-00000009 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510872-00000053 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510871-00000042 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510870-00000015 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510869-00000010 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510868-0000003C is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510867-0000000A is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510866-00000025 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510865-0000000B is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510864-00000011 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510863-0000004F is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510862-00000047 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510861-0000002F is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510860-0000005C is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510859-00000014 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510858-0000001F is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510857-00000052 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510856-0000002E is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510855-0000000C is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510854-00000014 is known as incorrect. Skipping.
2022-03-24T10:15:24+01:00 - info: Fork resolution: block #510853-0000000A is known as incorrect. Skipping.
2022-03-24T10:15:26+01:00 - info: Matched 4 zeros 00003136EBE2D68F825288AD059992EC277E143FB09B0A53E7529649B04BCB72 with Nonce = 10100011050116 for block#510851 by 2jztXx
2022-03-24T10:15:31+01:00 - info: Matched 4 zeros 0000FB5076DA986DD1FB80AA399168D852EA28CC8BCEF4A5A374AEDC94C5253C with Nonce = 10100011091833 for block#510851 by 2jztXx
2022-03-24T10:15:31+01:00 - info: Matched 4 zeros 0000786F365BDE6B51BFA34331D477F50F21ACD9032DB8FA4DA7D8B275D08957 with Nonce = 10100011093248 for block#510851 by 2jztXx
2022-03-24T10:15:41+01:00 - info: Matched 4 zeros 00005DC282D0FF2D06FED01DE560882506F4DBD745C1856F3FE2F727444F816C with Nonce = 10200011298755 for block#510851 by 2jztXx

Maybe related: Désynchro rapide de mon serveur Ğ1 - #11 par vit

Your node is not able to resolve the fork, because of this invalid block. The solution we found is to run full-resync.

1 « J'aime »