Duniter stuck at block #54499
Salut,
Sur une nouvelle installation de duniter, en miroir, les logs (ainsi que Cesium desktop) m'indiquent un blocage sur le block #54499 :
2018-01-11T21:04:39+01:00 - info: Block resolution: 1 potential blocks after current#54499... 2018-01-11T21:04:40+01:00 - error: Error: ruleNumber at Error (native) at Function.<anonymous> (/home/admin/duniter/duniter-1.6.14/app/lib/blockchain/DuniterBlockchain.js:53:23) at next (native) at fulfilled (/home/admin/duniter/duniter-1.6.14/app/lib/blockchain/DuniterBlockchain.js:4:58) 2018-01-11T21:04:40+01:00 - info: Fork resolution: 101 potential block(s) found... 2018-01-11T21:04:41+01:00 - info: Fork resolution: 1 potential suite(s) found... 2018-01-11T21:04:41+01:00 - info: Fork resolution: HEAD = block#54499 2018-01-11T21:04:41+01:00 - info: Fork resolution: suite 1/1 (-> #54599-000005) revert to fork point block#54499 2018-01-11T21:04:41+01:00 - info: Fork resolution: suite 1/1 REFUSED block#54500: ruleNumber 2018-01-11T21:04:42+01:00 - info: >> Server starting... 2018-01-11T21:04:42+01:00 - info: Node version: 1.6.14 2018-01-11T21:04:42+01:00 - info: Node pubkey: B7yii8bTa2AA5oktUjj4uh986nvG3PcKMqtiRJ2iCcuh 2018-01-11T21:04:42+01:00 - info: Duniter server listening on http://37.187.105.219:10901 2018-01-11T21:04:42+01:00 - info: Duniter server listening on http://[2001:41d0:a:39db::1]:10901 2018-01-11T21:04:42+01:00 - warn: Local node is not a member. Waiting to be a member before computing a block. 2018-01-11T21:04:42+01:00 - info: Sibling endpoints: 2018-01-11T21:04:42+01:00 - info: BMA access: g1.clapas.net:10901 2018-01-11T21:04:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known 2018-01-11T21:04:42+01:00 - info: Next peering signal in 9 min 2018-01-11T21:04:43+01:00 - info: >> Server ready! .... 2018-01-11T21:07:47+01:00 - info: Block resolution: 1 potential blocks after current#54499... 2018-01-11T21:07:47+01:00 - error: Error: ruleNumber at Error (native) at Function.<anonymous> (/home/admin/duniter/duniter-1.6.14/app/lib/blockchain/DuniterBlockchain.js:53:23) at next (native) at fulfilled (/home/admin/duniter/duniter-1.6.14/app/lib/blockchain/DuniterBlockchain.js:4:58) 2018-01-11T21:07:47+01:00 - info: Fork resolution: 101 potential block(s) found... 2018-01-11T21:07:48+01:00 - info: Fork resolution: block #54500-00000594 is known as incorrect. Skipping.
C'est un problème connu ? J'ai essayé de un --nocautious mais sans plus de succès.