Testeurs g1-test : nouvelle pré-release 1.6.17 à tester!

elois · 28 January 2018 22:49

Avant de publier la 1.6.17 nous avons besoins de tester nos dernier correctifs sur g1-test, la release de test est ici : releases:test (#2031) · Jobs · nodes / typescript / duniter · GitLab (cliquez sur download, puis décompressez l’archive, elle contient tout les paquets).

Lien de téléchargement direct pour le paquet deb version server : https://ifee.fr/pub/duniter-server-v20180128.2213.27-linux-x64.deb

A tout les membres de g1-test ayant un noeud duniter, @jytou @gerard94 @fbuland @mmpio @nanocryk @vit, nous avons besoins que vous installiez cette release de test

Ensuite vérifiez que vous arrivez bien a calculer des blocs !

La version est 20180128.2213.27 c’est normal, les releases de test ont pour version date.heure.seconde

Merci pour votre précieuse contribution.

ps: Quelqu’un sait qui sont Mententin, Antoni Ferreira et Bernard V ?

jytou · 28 January 2018 23:40

Salut Éloïs,
j’ai besoin de faire la release ARM, car mon nœud est sur un raspberry. Du coup, je prends quel numéro de version? Je suppose qu’il ne vaut mieux pas que j’utilise le tag 1.6.17…

Mententon_03 · 29 January 2018 00:07

Bonsoir elois.

Mententin et Antonio Ferreira sont la même personne (Mententon sur G1). Je suis un frère à Jean F. Je ne fais tourner qu’un noeud, en ce moment en 1.6.14, mais j’ai instalé et désinstallé la 1.6.16 plusieurs fois sans jamais calculer de bloks avec.
C’est pour l’instal de la 1.6.17 ?
Pour le moment, je calcule régulièrement un blok en 1.6.14 puis il me semble que je rejoins systematiquement un fork avec jytou.

Inso · 29 January 2018 06:01

Impossible de sync sur le noeud g1-test.duniter.org :

2018-01-29T06:50:58+01:00 - error: Error
2018-01-29T06:50:58+01:00 - error: Error
2018-01-29T06:50:58+01:00 - error: Error
2018-01-29T06:50:58+01:00 - info: Getting chunck #404/512 from 101000 to 101249 on peer 91.121.157.13:10900
2018-01-29T06:50:58+01:00 - info: Getting chunck #403/512 from 100750 to 100999 on peer 91.121.157.13:10900
2018-01-29T06:50:58+01:00 - info: Getting chunck #407/512 from 101750 to 101999 on peer 91.121.157.13:10900
2018-01-29T06:50:58+01:00 - error: Error
2018-01-29T06:50:58+01:00 - info: Getting chunck #406/512 from 101500 to 101749 on peer 91.121.157.13:10900
^C2018-01-29T06:50:58+01:00 - error: Error
2018-01-29T06:50:58+01:00 - error: Error
2018-01-29T06:50:58+01:00 - error: Error
2018-01-29T06:50:58+01:00 - debug: Trying to close SQLite...
2018-01-29T06:50:58+01:00 - info: Getting chunck #403/512 from 100750 to 100999 on peer 91.121.157.13:10900
2018-01-29T06:50:58+01:00 - info: Getting chunck #404/512 from 101000 to 101249 on peer 91.121.157.13:10900
2018-01-29T06:50:58+01:00 - info: Getting chunck #407/512 from 101750 to 101999 on peer 91.121.157.13:10900

Je rencontre un problème similaire sur celui de jytou. J’ai ensuite rééssayé sur le noeud duniter.org, et cette fois ci, ça a fonctionné…

Ca faisait un moment que j’avais pas réussi à sync mon noeud sur ğ1-test
Par contre, il semblerait que je sois bloqué sur un fork qui soit incompatible avec le protocole :

gtest@vps55093:/opt/gtest/duniter$ ./bin/duniter logs
2018-01-29T07:01:12+01:00 - warn: Unknown reference block of peer
2018-01-29T07:01:12+01:00 - error: Unknown reference block of peer
2018-01-29T07:01:12+01:00 - error: Unknown reference block of peer
2018-01-29T07:01:17+01:00 - info: SIDE Block #128158-0008A287 added to the blockchain in 32 ms
2018-01-29T07:01:17+01:00 - info: Block resolution: 0 potential blocks after current#128150...
2018-01-29T07:01:17+01:00 - info: Fork resolution: 3 potential block(s) found...
2018-01-29T07:01:33+01:00 - info: WS2P 2RbXrLkmtgWMcis8NWhPvM7BAGT4xLK5mFRkHiYi2Vc7: new incoming connection from 88.174.120.187:34264!
2018-01-29T07:01:33+01:00 - info: WS2P: established incoming connection from 3dnbnYY9 88.174.120.187:34264
2018-01-29T07:01:34+01:00 - info: Matched 3 zeros 000E5F573BBCED2230ED481AF042A7678C5B367BCE35250FE586CB52D77DF515 with Nonce = 10000000006275 for block#128151 by 2RbXrL
2018-01-29T07:01:49+01:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #0009DFDDD34A261D4D127CCAD7A5961D6298A972B3149860D38CBB6ED8D74FEB
2018-01-29T07:01:49+01:00 - info: [done] worker c#0#w#0
2018-01-29T07:01:49+01:00 - info: ENGINE c#0#0 HAS FOUND A PROOF #0009DFDDD34A261D4D127CCAD7A5961D6298A972B3149860D38CBB6ED8D74FEB
2018-01-29T07:01:49+01:00 - info: Matched 3 zeros 0009DFDDD34A261D4D127CCAD7A5961D6298A972B3149860D38CBB6ED8D74FEB with Nonce = 10000000007920 for block#128151 by 2RbXrL
2018-01-29T07:01:49+01:00 - info: Done: #128151, 0009DFDDD34A261D4D127CCAD7A5961D6298A972B3149860D38CBB6ED8D74FEB in 64.61s (~7919 tests, ~122.56 tests/s, using 1 cores, CPU 50%)
2018-01-29T07:01:49+01:00 - info: FOUND proof-of-work with 3 leading zeros followed by [0-9A]!
2018-01-29T07:01:49+01:00 - info: SIDE Block #128151-0009DFDD added to the blockchain in 40 ms
2018-01-29T07:01:49+01:00 - info: Block resolution: 1 potential blocks after current#128150...
2018-01-29T07:01:49+01:00 - error:  Error: ruleIssuerIsMember
    at Function.checkBlock (/opt/gtest/duniter/app/lib/blockchain/DuniterBlockchain.js:53:19)
    at <anonymous>
2018-01-29T07:01:49+01:00 - info: Fork resolution: 3 potential block(s) found...
2018-01-29T07:01:50+01:00 - info: SIDE Block #128159-00070490 added to the blockchain in 20 ms
2018-01-29T07:01:50+01:00 - info: Block resolution: 1 potential blocks after current#128150...
2018-01-29T07:01:50+01:00 - error:  Error: ruleIssuerIsMember
    at Function.checkBlock (/opt/gtest/duniter/app/lib/blockchain/DuniterBlockchain.js:53:19)
    at <anonymous>
2018-01-29T07:01:50+01:00 - info: Fork resolution: 4 potential block(s) found...
2018-01-29T07:02:09+01:00 - info: SIDE Block #128160-00038219 added to the blockchain in 996 ms
2018-01-29T07:02:09+01:00 - info: Block resolution: 1 potential blocks after current#128150...
2018-01-29T07:02:10+01:00 - error:  Error: ruleIssuerIsMember
    at Function.checkBlock (/opt/gtest/duniter/app/lib/blockchain/DuniterBlockchain.js:53:19)
    at <anonymous>
2018-01-29T07:02:10+01:00 - info: Fork resolution: 5 potential block(s) found...
2018-01-29T07:02:16+01:00 - info: SIDE Block #128161-000332B4 added to the blockchain in 55 ms
2018-01-29T07:02:16+01:00 - info: Block resolution: 1 potential blocks after current#128150...
2018-01-29T07:02:16+01:00 - error:  Error: ruleIssuerIsMember
    at Function.checkBlock (/opt/gtest/duniter/app/lib/blockchain/DuniterBlockchain.js:53:19)
    at <anonymous>
2018-01-29T07:02:16+01:00 - info: Fork resolution: 6 potential block(s) found...
2018-01-29T07:02:27+01:00 - info: SIDE Block #128162-0000974F added to the blockchain in 11 ms
2018-01-29T07:02:27+01:00 - info: Block resolution: 1 potential blocks after current#128150...
2018-01-29T07:02:27+01:00 - error:  Error: ruleIssuerIsMember
    at Function.checkBlock (/opt/gtest/duniter/app/lib/blockchain/DuniterBlockchain.js:53:19)
    at <anonymous>
2018-01-29T07:02:27+01:00 - info: Fork resolution: 7 potential block(s) found...
2018-01-29T07:02:44+01:00 - warn: Unknown reference block of peer
2018-01-29T07:02:44+01:00 - warn: Unknown reference block of peer
2018-01-29T07:02:44+01:00 - error: Unknown reference block of peer
2018-01-29T07:02:44+01:00 - error: Unknown reference block of peer
2018-01-29T07:02:44+01:00 - warn: Unknown reference block of peer
2018-01-29T07:02:53+01:00 - info: SIDE Block #128163-0007E8D5 added to the blockchain in 37 ms
2018-01-29T07:02:53+01:00 - info: Block resolution: 1 potential blocks after current#128150...
2018-01-29T07:02:53+01:00 - error:  Error: ruleIssuerIsMember
    at Function.checkBlock (/opt/gtest/duniter/app/lib/blockchain/DuniterBlockchain.js:53:19)
    at <anonymous>
2018-01-29T07:02:53+01:00 - info: Fork resolution: 8 potential block(s) found...
2018-01-29T07:02:59+01:00 - info: SIDE Block #128164-00023E7D added to the blockchain in 32 ms
2018-01-29T07:02:59+01:00 - info: Block resolution: 1 potential blocks after current#128150...
2018-01-29T07:02:59+01:00 - error:  Error: ruleIssuerIsMember
    at Function.checkBlock (/opt/gtest/duniter/app/lib/blockchain/DuniterBlockchain.js:53:19)
    at <anonymous>
2018-01-29T07:02:59+01:00 - info: Fork resolution: 9 potential block(s) found...
2018-01-29T07:03:01+01:00 - warn: Unknown reference block of peer
2018-01-29T07:03:01+01:00 - error: Unknown reference block of peer
2018-01-29T07:03:01+01:00 - error: Unknown reference block of peer
2018-01-29T07:03:01+01:00 - warn: Unknown reference block of peer
2018-01-29T07:03:01+01:00 - warn: Unknown reference block of peer
2018-01-29T07:03:03+01:00 - warn: Unknown reference block of peer
2018-01-29T07:03:03+01:00 - error: Unknown reference block of peer
2018-01-29T07:03:03+01:00 - error: Unknown reference block of peer
2018-01-29T07:03:03+01:00 - error: Unknown reference block of peer
2018-01-29T07:03:03+01:00 - error: Unknown reference block of peer
2018-01-29T07:03:03+01:00 - warn: Unknown reference block of peer
2018-01-29T07:03:03+01:00 - warn: Unknown reference block of peer
2018-01-29T07:03:12+01:00 - warn: Unknown reference block of peer
2018-01-29T07:03:12+01:00 - warn: Unknown reference block of peer
2018-01-29T07:03:12+01:00 - error: Unknown reference block of peer
2018-01-29T07:03:12+01:00 - error: Unknown reference block of peer
2018-01-29T07:03:12+01:00 - warn: Unknown reference block of peer
2018-01-29T07:03:40+01:00 - info: ⬇ 2RbXrLkmtgWMcis8NWhPvM7BAGT4xLK5mFRkHiYi2Vc7 IN
2018-01-29T07:03:40+01:00 - info: ✔ 2RbXrLkmtgWMcis8NWhPvM7BAGT4xLK5mFRkHiYi2Vc7 IN
2018-01-29T07:03:40+01:00 - info: ⬇ 2RbXrLkmtgWMcis8NWhPvM7BAGT4xLK5mFRkHiYi2Vc7 IN
2018-01-29T07:03:40+01:00 - warn:  httpCode=400, ucode=2007, message=Already received membership
2018-01-29T07:03:40+01:00 - info: ⬇ 2RbXrLkmtgWMcis8NWhPvM7BAGT4xLK5mFRkHiYi2Vc7 IN
2018-01-29T07:03:40+01:00 - error:  httpCode=400, ucode=2007, message=Already received membership
2018-01-29T07:03:40+01:00 - info: ⬇ 2RbXrLkmtgWMcis8NWhPvM7BAGT4xLK5mFRkHiYi2Vc7 IN
2018-01-29T07:03:40+01:00 - warn:  httpCode=400, ucode=2007, message=Already received membership
2018-01-29T07:03:41+01:00 - info: SIDE Block #128165-0006EC75 added to the blockchain in 27 ms
2018-01-29T07:03:41+01:00 - info: Block resolution: 1 potential blocks after current#128150...
2018-01-29T07:03:41+01:00 - error:  Error: ruleIssuerIsMember
    at Function.checkBlock (/opt/gtest/duniter/app/lib/blockchain/DuniterBlockchain.js:53:19)
    at <anonymous>
2018-01-29T07:03:41+01:00 - info: Fork resolution: 10 potential block(s) found...
2018-01-29T07:03:46+01:00 - info: SIDE Block #128166-0005ED7A added to the blockchain in 30 ms
2018-01-29T07:03:46+01:00 - info: Block resolution: 1 potential blocks after current#128150...
2018-01-29T07:03:46+01:00 - error:  Error: ruleIssuerIsMember
    at Function.checkBlock (/opt/gtest/duniter/app/lib/blockchain/DuniterBlockchain.js:53:19)
    at <anonymous>
2018-01-29T07:03:46+01:00 - info: Fork resolution: 11 potential block(s) found...

Mententon_03 · 29 January 2018 08:54

Bonjour Inso. Pour moi, rien de changé depuis hier soir. Je suis synchronisé sur:
91.121.157.13: 10900 et public + privé activés. Je calcule des blocs mais bascule juste après sur un fork.

Dois je passer à la 1.6.17 ? ou bien je reste sur la 1.6.14 ???

nanocryk · 29 January 2018 08:54

Est-ce qu’un simple git pull de la branche 1.6 suffit ? @elois

Note : j’aurais sûrement besoin d’être re-certifié.

cgeek · 29 January 2018 09:33

L’idée c’est bien de tester la 1.6.17, via les liens donnés par Eloïs ci-dessus.

Mententon_03 · 29 January 2018 09:40

Synchro 1.6.17 en cours … sur 91.121.157.13:10900

nanocryk · 29 January 2018 10:33

Synchro + calcul de bloc OK.

Inso · 29 January 2018 11:05

Vous êtes sur quelle branche du coup ?

nanocryk · 29 January 2018 11:53

1256-the-1-6-15-and-1-6-16-versions-never-starts-the-calculation-of-blocks qui correspond au dernier commit apparemment.

Mententon_03 · 29 January 2018 11:57

Pour le moment, en 1.6.17, mon « current block » est « aligné » sur la branche principale mais ne calcule pas de blocks. Peut-être une mauvaise idée de me synchroniser sur 91.121.157.13:10900 qui semble tourner en 1.6.14 ??

Inso · 29 January 2018 11:58

Je parle de la branche de la chaine de bloc

nanocryk · 29 January 2018 11:58

Euh, il est sensé en avoir qu’une, non ? x)

EDIT : J’ai miné le bloc #128330 de hash 00032FBC711A5EFA4A559652929781C41279893EE1721FD7A498743B35EC2A4F

nanocryk · 29 January 2018 12:02

Tu peux essayer de te synchro sur le miens ? (g1-test.duniter.nanocryk.fr)

Inso · 29 January 2018 12:04

Oui mais ce matin ça partait dans tout les sens…

nanocryk · 29 January 2018 12:04

Ah d’accord. Tu as le même HEAD que moi du coup ?

Inso · 29 January 2018 12:36

J’ai réussi à me synchroniser sur toi il me semble : http://gtest.duniter.inso.ovh/blockchain/current

nanocryk · 29 January 2018 12:43

Euh … toujours pas de nouveaux blocs depuis le miens ? Ça fait quasi une heure là.

Inso · 29 January 2018 12:48

Le réseau est en grande difficulté… Je vais avoir besoin de certifs par ailleurs.