C’est juste, mais du coup je ne sais pas comment envoyer des transactions ou des certifications… Or, j’aimerais bien le faire 
J’ai mis mon noeud GT en standby car j’aimerais bien le faire tourner en 1.7.x or si j’arrive parfaitement à le compiler, il plante à l’exécution (en serveur ou en synchro). J’ai testé avec Node 8.x et Node 9.x (la version 10 est trop haute d’après package.json) sans succès, je n’ai pas encore eu le temps de pousser l’enquête plus loin 
@jytou x86_64 le même serveur faisait tourner un nœud G1 et GT. actuellement seul mon noeud G1 en 1.6.31 fonctionne. Je peux retester avec NodeJS 9.11 à l’occasion.
[7458139.826954] traps: node[26476] trap invalid opcode ip:7f8ee76cd0bd sp:7f8ee54b70b0 error:0 in leveldown.node[7f8ee7680000+50000]
./toto.sh: line 15: 26466 Illegal instruction bin/duniter sync $SERVER --home /var/lib/duniter --mdb gtest --nointeractive --slowMon nœud intermittent Duniter-desktop 1.7.11 ne peut plus rejoindre la blockchain majoritaire…
J’ai ces erreurs en boucle :
2019-02-20T16:50:17+01:00 - info: Fork resolution: 48 potential block(s) found...
2019-02-20T16:50:17+01:00 - info: Fork resolution: block #325600-0000CB2C is known as incorrect. Skipping.
2019-02-20T16:50:17+01:00 - debug: Suite -> 325647-000398AA missing block#325600-0000CB2C
2019-02-20T16:50:17+01:00 - info: Fork resolution: block #325599-0001B49A is known as incorrect. Skipping.
2019-02-20T16:50:17+01:00 - debug: Suite -> 325600-0000CB2C missing block#325599-0001B49A
2019-02-20T16:50:28+01:00 - info: [DpJse2t7] ⬇ PEER 5esxEcaS 326603-0
2019-02-20T16:50:28+01:00 - warn: Unknown reference block of peer
2019-02-20T16:50:28+01:00 - info: [DpJse2t7] ⬇ PEER 5esxEcaS 326603-0
2019-02-20T16:50:28+01:00 - warn: Unknown reference block of peer
2019-02-20T16:50:37+01:00 - info: SIDE Block #326638-003951C1 added to the blockchain in 0 ms
2019-02-20T16:50:37+01:00 - info: Block resolution: 2 potential blocks after current#325597...
2019-02-20T16:50:37+01:00 - error: Error: ruleNumber
at Function.checkBlock (/mnt/data/Logiciels/duniter-desktop-v1.7.11-linux-x64/app/lib/blockchain/DuniterBlockchain.js:62:19)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:160:7)
2019-02-20T16:50:37+01:00 - error: Error: ruleNumber
at Function.checkBlock (/mnt/data/Logiciels/duniter-desktop-v1.7.11-linux-x64/app/lib/blockchain/DuniterBlockchain.js:62:19)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:160:7)
Hope it helps.
@Moul et moi-même venons de nous resynchroniser sur @jytou, je suis en train de faire de même pour les miroirs.
Je vais tenter de suivre un peu plus tout ce qui se passe, car visiblement il y a encore de nombreux axes d’amélioration quant à la stabilité de Duniter. Bon, personne n’en doutais 
4 Likes
Ça avance plus :
Current block: n°347924, generated on the 2019-04-01 18:11:20
Generation of next block n°347925 possible by at least 2/3 members
Common Proof-of-Work difficulty level: 59, hash starting with `000[0-4]*`
| uid | match | Π diffi | Σ diffi |
|-----------+---------------+------------+-----------|
| moul-test | 0000000[0-8]* | 1.9 × 10^9 | 119 |
| jyt | 000[0-2]* | 5.3 × 10^4 | 61 |
| cgeek | 000[0-4]* | 4.5 × 10^4 | 59 |
Mon nœud est isolé mais il cherche quand même mais ne semble toujours pas avoir trouvé :
2019-04-02T19:48:39+02:00 - info: Matched 3 zeros 000CEB4D12C13FCD8C05B66476D814F4D154A480C0CDE9006BA08D0428283513 with Nonce = 10100000038400 for block#347925 by 5B8iMA
2019-04-02T19:48:58+02:00 - info: Matched 3 zeros 000A7C1F49145CB8CE2143A6C0D56E5AF3B0CC4248ABB443E6AD1392CA740EDA with Nonce = 10200000037865 for block#347925 by 5B8iMA
2019-04-02T19:49:29+02:00 - info: Sibling endpoints:
2019-04-02T19:49:29+02:00 - info: BMA access: nuc.moul.re:10902
2019-04-02T19:49:29+02:00 - info: [5B8iMAzq] ⬇ PEER 5B8iMAzq 347924-0
2019-04-02T19:49:29+02:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2019-04-02T19:49:29+02:00 - info: Next peering signal in 5 min
2019-04-02T19:49:29+02:00 - info: Matched 3 zeros 000C29C906573CFDCE46B42C3DEC74E8152F3FC0D894C5FA8A279D5DB7D861CA with Nonce = 10100000039345 for block#347925 by 5B8iMA
2019-04-02T19:49:35+02:00 - info: [5B8iMAzq] ⬇ PEER JyTqcD4Q 347925-0
2019-04-02T19:49:35+02:00 - warn: Unknown reference block of peer
2019-04-02T19:49:40+02:00 - info: [5B8iMAzq] ⬇ PEER 85W4GAHQ 201999-0
2019-04-02T19:49:40+02:00 - warn: Error: TOO_OLD_PEER
at fifoPromiseHandler.pushFIFOPromise (/home/gtest/duniter/app/service/PeeringService.js:134:31)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
2019-04-02T19:49:53+02:00 - info: SIDE Block #348694-0064B0EF added to the blockchain in 0 ms
2019-04-02T19:49:53+02:00 - info: Block resolution: 0 potential blocks after current#347924...
2019-04-02T19:50:12+02:00 - info: Matched 3 zeros 000AC9D32B6ECA184EAEAED5D45AE2B2AD742048D14BD6D9EE4DBFD0F9E1B626 with Nonce = 10300000039750 for block#347925 by 5B8iMA
2019-04-02T19:50:56+02:00 - info: Matched 3 zeros 0008CB5B66A9D3F69905BD802699438B31B71B6B9EB2FC2EF153DDFDD5816E6A with Nonce = 10100000040998 for block#347925 by 5B8iMA
2019-04-02T19:50:58+02:00 - info: Matched 3 zeros 000899B87CC71083D58C98B73FF8A782119379DC98B3139344D7F3EB976DA365 with Nonce = 10300000040649 for block#347925 by 5B8iMA
2019-04-02T19:51:02+02:00 - info: SIDE Block #348695-00AF664B added to the blockchain in 0 ms
2019-04-02T19:51:02+02:00 - info: Block resolution: 0 potential blocks after current#347924...
2019-04-02T19:51:08+02:00 - info: [5B8iMAzq] ⬇ PEER 3dnbnYY9 347924-0
2019-04-02T19:51:08+02:00 - info: Matched 3 zeros 0008EB74BF04C614894A069FAB3CE05B0FBC9029E8948A837DC5759536AA76F9 with Nonce = 10300000040852 for block#347925 by 5B8iMA
2019-04-02T19:51:20+02:00 - info: SIDE Block #348696-00A7F642 added to the blockchain in 0 ms
2019-04-02T19:51:20+02:00 - info: Block resolution: 0 potential blocks after current#347924...
2019-04-02T19:51:54+02:00 - info: Matched 3 zeros 00013B1C7323D427FBB8186F1AB6A5387BC001AEFF898027B8623127B92E780F with Nonce = 10400000041268 for block#347925 by 5B8iMA
2019-04-02T19:51:59+02:00 - info: SIDE Block #348697-001A2FCC added to the blockchain in 1 ms
2019-04-02T19:51:59+02:00 - info: Block resolution: 0 potential blocks after current#347924...
2019-04-02T19:52:08+02:00 - info: Matched 3 zeros 000532F8ADE60B13B90927C504061C50B51B2C0EA5E82E413C617A9E32E068CA with Nonce = 10200000041403 for block#347925 by 5B8iMA
2019-04-02T19:52:51+02:00 - info: Matched 3 zeros 000D4084C942C44A56D30447CF4F5499283789DFEA05428E08F6CDB43D34537F with Nonce = 10300000042799 for block#347925 by 5B8iMA
2019-04-02T19:53:05+02:00 - info: SIDE Block #348698-00ABAF6D added to the blockchain in 0 ms
2019-04-02T19:53:05+02:00 - info: Block resolution: 0 potential blocks after current#347924...
2019-04-02T19:53:09+02:00 - info: SIDE Block #348699-002DC53F added to the blockchain in 0 ms
2019-04-02T19:53:09+02:00 - info: Block resolution: 0 potential blocks after current#347924...
Non, pas pour ma part… je peux éventuellement le mettre à jour mais… sur quelle branche va-t-on se mettre ?
Il ne semble pas y avoir d’autre branche que la nôtre.
Il doit y avoir une autre branche qui avance, mais il faut trouver quel nœud la fait avancer :
2019-04-03T09:04:41+02:00 - info: SIDE Block #349013-00BBD711 added to the blockchain in 0 m
Il y a bien des blocs générés ailleurs :
2019-04-04T11:51:03+02:00 - info: SIDE Block #349598-0003D69D added to the blockchain in 0 ms
2019-04-04T11:51:03+02:00 - info: Block resolution: 0 potential blocks after current#347924...
mais pas moyen de les trouver avec :
blockchain/branches
{
"blocks": [
{
"version": 11,
"nonce": 10400000000123,
"number": 347924,
"powMin": 59,
"time": 1554135081,
"medianTime": 1554134087,
"membersCount": 12,
"monetaryMass": 0,
"unitbase": 1,
"issuersCount": 3,
"issuersFrame": 16,
"issuersFrameVar": 0,
"currency": "g1-test",
"issuer": "3dnbnYY9i2bHMQUGyFp5GVvJ2wBkVpus31cDJA5cfRpj",
"signature": "sOfOQihdnyARMIHyUOQzTWO2J29voKVPxo5l7OVeBA9I9dptfhKrs9D91udMTrId0CuPpCXYt/nwH2uK89T5Aw==",
"hash": "0001BB0A8AEEF98A819E995918A70B8AD291A9D769B20AFE7B280C39D5C3A362",
"parameters": "",
"previousHash": "0002FDFAFE33F645E76F6E3A7E7F8853C6C4FD5E43F2D9922B67A200F003E4AF",
"previousIssuer": "JyTqcD4Q9aEAR2CWEpwBUAAyMCjfM6gaE5S2e8GWUuq",
"inner_hash": "6619004D02F43A3E31A101125CFDB5ADE512EB0A1FFD86BCCF038F5B1249D401",
"dividend": null,
"identities": [],
"joiners": [],
"actives": [],
"leavers": [],
"revoked": [],
"excluded": [],
"certifications": [],
"transactions": [],
"raw": "Version: 11\nType: Block\nCurrency: g1-test\nNumber: 347924\nPoWMin: 59\nTime: 1554135081\nMedianTime: 1554134087\nUnitBase: 1\nIssuer: 3dnbnYY9
i2bHMQUGyFp5GVvJ2wBkVpus31cDJA5cfRpj\nIssuersFrame: 16\nIssuersFrameVar: 0\nDifferentIssuersCount: 3\nPreviousHash: 0002FDFAFE33F645E76F6E3A7E7F8853C6C4FD5E43
F2D9922B67A200F003E4AF\nPreviousIssuer: JyTqcD4Q9aEAR2CWEpwBUAAyMCjfM6gaE5S2e8GWUuq\nMembersCount: 12\nIdentities:\nJoiners:\nActives:\nLeavers:\nRevoked:\nEx
cluded:\nCertifications:\nTransactions:\nInnerHash: 6619004D02F43A3E31A101125CFDB5ADE512EB0A1FFD86BCCF038F5B1249D401\nNonce: 10400000000123\n"
},
{
"version": 11,
"nonce": 10200000000118,
"number": 347924,
"powMin": 59,
"time": 1554135080,
"medianTime": 1554134087,
"membersCount": 12,
"monetaryMass": 111796604,
"unitbase": 1,
"issuersCount": 3,
"issuersFrame": 16,
"issuersFrameVar": 0,
"currency": "g1-test",
"issuer": "5B8iMAzq1dNmFe3ZxFTBQkqhq4fsztg1gZvxHXCk1XYH",
"signature": "3zORlpqQZoiHXorGXVoUe8gbsWB6MJk4ZGgMn9eN0OR7C4VWE9dxFIuPnwnYqQCCcFRwHMQMJqRyJ+Wdul0mCQ==",
"hash": "000413FA1533A0610DE65004F9F849D557DD5E953817EEA98621121502BB88F2",
"parameters": "",
"previousHash": "0002FDFAFE33F645E76F6E3A7E7F8853C6C4FD5E43F2D9922B67A200F003E4AF",
"previousIssuer": "JyTqcD4Q9aEAR2CWEpwBUAAyMCjfM6gaE5S2e8GWUuq",
"inner_hash": "F86ECBD1A15CEA7B3DDF78CC6A7263F13E35C61B23BE429F5F5EA63BCA89806C",
"dividend": null,
"identities": [],
"joiners": [],
"actives": [],
"leavers": [],
"revoked": [],
"excluded": [],
"certifications": [],
"transactions": [],
"raw": "Version: 11\nType: Block\nCurrency: g1-test\nNumber: 347924\nPoWMin: 59\nTime: 1554135080\nMedianTime: 1554134087\nUnitBase: 1\nIssuer: 5B8iMAzq
1dNmFe3ZxFTBQkqhq4fsztg1gZvxHXCk1XYH\nIssuersFrame: 16\nIssuersFrameVar: 0\nDifferentIssuersCount: 3\nPreviousHash: 0002FDFAFE33F645E76F6E3A7E7F8853C6C4FD5E43
F2D9922B67A200F003E4AF\nPreviousIssuer: JyTqcD4Q9aEAR2CWEpwBUAAyMCjfM6gaE5S2e8GWUuq\nMembersCount: 12\nIdentities:\nJoiners:\nActives:\nLeavers:\nRevoked:\nEx
cluded:\nCertifications:\nTransactions:\nInnerHash: F86ECBD1A15CEA7B3DDF78CC6A7263F13E35C61B23BE429F5F5EA63BCA89806C\nNonce: 10200000000118\n"
}
]
}⏎
On voit ici, deux blocs trouvé à une seconde prêt.
Ça serait bien de débloquer la situation, car je ne peux plus émettre de transactions.
Toutes mes sources sont bloquées en pending.
1 Like
Moi je ne suis plus membre si vous pouvez certifier Vincentest
Merci
Vincentest sur 9Uwy2bEbYUiUfB6SVrkhGheEiuBr6TSh6bD8AH8dajy7 ?
Oui, c’est ça.
Ça s’accélère avec trois jours de retard à rattraper !!!
C’est beau à voir avec silkaj diffi qui utilise une websocket.
3 Likes
Du coup je ne suis plus trop, quel nœud utiliser ? Sachant que g1-test.duniter.org, legacy.g1test.nordstrom.duniter.org ainsi que g1-test.cgeek.fr sont d’accord entre-eux, mais je veux bien tout rebasculer en 1.7.14 (voire 1.7.15 qui résout le bug des transactions non affichées !).
Ah ce que je vois, mon nœud a décroché cette nuit. Ça a dû aller trop vite. Je vais voir pour rattraper ton nœud qui avance.