Node stuck due to "Certification based on an unexisting block"
My node got an IP address change during the night.
I have modified the config.json file to update the new IP address et restart Duniter Desktop 1.7.16 on Ubuntu 14.04.
About twenty nodes are connected to me (incoming), the pool is updated with data, but I got a repeating error message about a missing bloc preventing the node to get back in the track and switch to the main branch.
2019-04-17T10:43:22+02:00 - info: ⬇ CERT AhguU4QXRo7fuNNat8hUNyJPNzA3pcbDet14eqcHZw9Y block#213020 -> amduni
2019-04-17T10:43:22+02:00 - info: ✘ CERT AhguU4QXRo7fuNNat8hUNyJPNzA3pcbDet14eqcHZw9Y Certification based on an unexisting block
2019-04-17T10:43:22+02:00 - warn: Error: Certification based on an unexisting block
at checkCertificationShouldBeValid (/mnt/data/home/vit/Logiciels/duniter-desktop-v1.7.16-linux-x64/app/lib/rules/global_rules.js:241:23)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:160:7)
The node is only 89 blocs away from the main branch at this time...
Stuck at 212931-00000083E2D662AF38
Need to reach 213020-000000A78528914786
Other error message from the log:
2019-04-17T02:36:35+02:00 - [32minfo[39m: Block resolution: 1 potential blocks after current#212930...
2019-04-17T02:36:35+02:00 - [31merror[39m: Error: ruleNumber
at Function.checkBlock (/mnt/data/home/vit/Logiciels/duniter-desktop-v1.7.16-linux-x64/app/lib/blockchain/DuniterBlockchain.js:62:19)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:160:7)
2019-04-17T02:36:35+02:00 - [32minfo[39m: Fork resolution: 2 potential block(s) found...
2019-04-17T02:36:35+02:00 - [32minfo[39m: Fork resolution: block #212933-00000650 is known as incorrect. Skipping.
2019-04-17T02:36:35+02:00 - [32minfo[39m: Fork resolution: block #212932-00000211 is known as incorrect. Skipping.