Config qui saute lors du passage 1.6 vers 1.7 ?

Support Duniter-v1
1

Salut à tous,
J’ai eu un truc bizarre lors de la mise a jour de 1.6.xx vers 1.7.5 mais je n’ai pas rpis le temps de m’en occuper.
du coup, je viens de passer en 1.7.7 et je viens de me rendre compte que je viens de relancer une synchro puisque, visiblement, je n’avais plus rien !!!
Donc, y’a peut-etre un pb de config qui saute en passe de 1.6 en 1.7 ???
en tout cas, de mon coté, la synchro est en cours, je devrais vite revenir “online”…
A suivre…
Merci pour le message

2

Salut à tous,

Bon, je fouille mais je n’ai pas tout compris…
Du coup, je suis passé en 1.7.8 et j’ai relancé une synchro…
J’ai un peu plus d’amis qu’en 1.7.7 (connected to 5 peers) mais du coté de la synchro, c’est arrivé là très vite et c’est resté bloqué :
Milestones… (100%)
Download… (0%)
Apply… (0%)
Sandbox… (0%)
Peers… (0%)

J’avoue être un peu perdu donc si ce n’est qu’une question de temps, ok, mais sinon, je suis preneur d’un petit aiguillage…
Autres infos au cas ou ça serait utile:
Current block #182282
Members count 1537
Median time 2018-12-26 10:46:45
Common difficulty level 84
Monetary mass 475674 UD
blocks made by this key (last 2 months) : 0

Merci d’avance,
Duarte

3

Tu t’es mis à jour un peu en avant-première, certes des nœuds se mettent à jour mais c’est plutôt du beta-testing.

Effectivement, quand tu passes de 1.6 à 1.7 toutes les données sont invalidées et il faut relancer une synchronisation.

Pour ton soucis, essayes de redémarrer complètement ton nœud (fermer la fenêtre si tu as une installation de Bureau, couper le serveur et le relancer si tu as la version Serveur) puis de relancer la synchro.

Tu essayes bien sur la Ğ1 ?

1 Like
4

Coucou et merci pour ton aide.
Donc oui, je suis bien sur la Ğ1, j’ai un serveur virtuel dédié rien que pour ça…
J’ai donc redémarré le serveur et relancer la synchro via l’interface Web et ça bloque là au bout de quelques secondes :
Milestones… (100%)
Download… (50%)

(j’avais déjà relancé le noeud et la synchro plusieurs fois, soit en faisant la mise à jour 1.7.5 -> 1.7.7 puis 1.7.7 -> 1.7.8 + un reboot à chaque fois quand j’ai vu que ça bloquait…)

5

juste , si ça peut aider, un bout de la log car j’ai des trucs bizarres, je pense :

2018-12-27T11:55:16+01:00 - warn: Unknown reference block of peer
2018-12-27T11:55:29+01:00 - info: WS2P: Could not connect to peer DTgQ97Au using `WS2P 78.242.59.220 20902: WS2P connection timeout`
2018-12-27T11:55:36+01:00 - info: [GRBPV3Y7] ⬇ PEER BDv28pi7 182565-0
2018-12-27T11:55:36+01:00 - warn: Unknown reference block of peer
2018-12-27T11:55:36+01:00 - info: [GRBPV3Y7] ⬇ PEER BDv28pi7 182565-0
2018-12-27T11:55:36+01:00 - warn: Unknown reference block of peer
2018-12-27T11:55:36+01:00 - info: [GRBPV3Y7] ⬇ PEER BDv28pi7 182565-0
2018-12-27T11:55:36+01:00 - warn: Unknown reference block of peer
2018-12-27T11:55:36+01:00 - info: [GRBPV3Y7] ⬇ PEER BDv28pi7 182565-0
2018-12-27T11:55:36+01:00 - warn: Unknown reference block of peer
2018-12-27T11:55:36+01:00 - info: [GRBPV3Y7] ⬇ PEER BDv28pi7 182565-0
2018-12-27T11:55:36+01:00 - warn: Unknown reference block of peer
2018-12-27T11:56:05+01:00 - info: [GRBPV3Y7] ⬇ PEER 5fPevx21 179816-0
2018-12-27T11:56:05+01:00 - error:  Error: TOO_OLD_PEER
    at fifoPromiseHandler.pushFIFOPromise (/opt/duniter/app/service/PeeringService.js:134:31)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:160:7)
2018-12-27T11:56:05+01:00 - error: Error: TOO_OLD_PEER
    at fifoPromiseHandler.pushFIFOPromise (/opt/duniter/app/service/PeeringService.js:134:31)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:160:7)
2018-12-27T11:56:05+01:00 - warn: TOO_OLD_PEER
2018-12-27T11:56:10+01:00 - info: [GRBPV3Y7] ⬇ PEER HnQH8P6n 182565-0
2018-12-27T11:56:10+01:00 - warn: Unknown reference block of peer
2018-12-27T11:56:10+01:00 - info: [GRBPV3Y7] ⬇ PEER HnQH8P6n 182565-0
2018-12-27T11:56:10+01:00 - warn: Unknown reference block of peer
2018-12-27T11:56:10+01:00 - info: [GRBPV3Y7] ⬇ PEER HnQH8P6n 182565-0
2018-12-27T11:56:10+01:00 - warn: Unknown reference block of peer
2018-12-27T11:56:10+01:00 - info: [GRBPV3Y7] ⬇ PEER HnQH8P6n 182565-0
2018-12-27T11:56:10+01:00 - warn: Unknown reference block of peer
2018-12-27T11:56:10+01:00 - info: [GRBPV3Y7] ⬇ PEER HnQH8P6n 182565-0
2018-12-27T11:56:10+01:00 - warn: Unknown reference block of peer
6

lol, je suis un peu en mode Matrix, je regarde la log défiler …
J’ai eu ça a l’instant …

2018-12-27T12:04:59+01:00 - info: WS2P: Could not connect to peer CV1GNhPp using `WS2P 81.240.101.52 20900: WS2P connection timeout`
2018-12-27T12:04:59+01:00 - info: WS2P: Could not connect to peer 38MEAZN6 using `WS2P g1.duniter.fr 443: WS2P connection timeout`
2018-12-27T12:04:59+01:00 - info: WS2P: Could not connect to peer 82NdD9eE using `WS2P 78.251.5.57 20900: WS2P connection timeout`
2018-12-27T12:04:59+01:00 - info: WS2P: Could not connect to peer HqSgtznE using `WS2P g1.vincentrehm.fr 20901: WS2P connection timeout`
2018-12-27T12:04:59+01:00 - info: WS2P: Could not connect to peer 8iVdpXqF using `WS2P 91.121.157.13 20901: WS2P connection timeout`
2018-12-27T12:04:59+01:00 - info: WS2P: init: bundle of peers 3/4
2018-12-27T12:04:59+01:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2018-12-27T12:04:59+01:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2018-12-27T12:04:59+01:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2018-12-27T12:04:59+01:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2018-12-27T12:04:59+01:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE`Preformatted text`
7

Quand vous collez des log sur le forum merci d’utiliser le bouton “</>” afin de les formater de façon lisible, @Duarte j’ai édité tes messages mais pense y pour les prochaines fois stp :slight_smile:

1 Like
8

Mais quand tu dis que ça bloque, tu attends combien de temps ?

9

Merci

10

J’attends quelques heures, genre toute cette nuit par exemple …

là par exemple, ça fait 4h et j’ai pas l’impression qu’il se passe grand chose … :frowning:

11

OK, je voulais savoir si c’était quelques secondes ou bien plus.

Comme tu as YunoHost, je te suggère le test suivant, tout en ligne de commande :

  1. stopper le nœud Duniter

    duniter stop

  2. synchroniser en mode « non intéractif » (= je veux voir le détail des logs de synchro) :

    duniter sync g1.duniter.org --nointeractive

Tu pourras ensuite donner ici le résultat de la commande. Tu verras plus de détails.

12

Merci,
voici la log

2018-12-27T20:17:57+01:00 - debug: Plugging file system...
2018-12-27T20:17:57+01:00 - debug: Loading conf...
2018-12-27T20:17:57+01:00 - debug: Configuration saved.
Failed to open file for reading : /root/.config/duniter/duniter_default/wotb.bin
2018-12-27T20:17:58+01:00 - debug: Opening SQLite database "/root/.config/duniter/duniter_default/duniter.db"...
2018-12-27T20:17:58+01:00 - debug: Opening SQLite database "/root/.config/duniter/duniter_default/txs.db"...
2018-12-27T20:17:58+01:00 - debug: Opening SQLite database "/root/.config/duniter/duniter_default/peers.db"...
2018-12-27T20:17:58+01:00 - debug: Upgrade database...
2018-12-27T20:17:58+01:00 - info: Block resolution: 0 potential blocks for root block...
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.duniter.org :443...
2018-12-27T20:17:58+01:00 - info: Try with 91.121.157.13:10901 8iVdpX
2018-12-27T20:17:58+01:00 - info: [GRBPV3Y7] ⬇ PEER 8iVdpXqF 182661-0
2018-12-27T20:17:58+01:00 - info: [GRBPV3Y7] ✔ PEER 8iVdpXqF 0-E3B0C4
2018-12-27T20:17:58+01:00 - info: Sync started.
2018-12-27T20:17:58+01:00 - info: Getting remote blockchain info...
2018-12-27T20:17:58+01:00 - debug: Loading conf...
2018-12-27T20:17:58+01:00 - info: Peers...
2018-12-27T20:17:58+01:00 - info: Downloading Blockchain...
2018-12-27T20:17:58+01:00 - info: Connecting to address duniter.normandie-libre.fr :443...
2018-12-27T20:17:58+01:00 - info: Connecting to address 77.141.115.111 :10901...
2018-12-27T20:17:58+01:00 - info: Connecting to address 91.121.157.13 :10901...
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.altsysnet.com :10900...
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.melua.fr :20901...
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.nordstrom.duniter.org :443...
2018-12-27T20:17:58+01:00 - info: Connecting to address 81.57.152.178 :57586...
2018-12-27T20:17:58+01:00 - info: Connecting to address duniter.compleus.com :10901...
2018-12-27T20:17:58+01:00 - info: Connecting to address duniter.adn.life :10901...
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.duniter.sajm.ovh :20902...
2018-12-27T20:17:58+01:00 - info: Connecting to address 88.161.154.41 :20900...
2018-12-27T20:17:58+01:00 - info: Connecting to address 37.60.157.130 :10900...
2018-12-27T20:17:58+01:00 - info: Connecting to address 82.251.191.185 :10901...
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.duniter.org :443...
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.duniter.fr :80...
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.cgeek.fr :80...
2018-12-27T20:17:58+01:00 - info: Connecting to address duniter.fabwice.com :443...
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.donnadieu.fr :12901...
2018-12-27T20:17:58+01:00 - info: Connecting to address duniter.moul.re :80...
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.duniter.inso.ovh :80...
2018-12-27T20:17:58+01:00 - info: Connecting to address 78.242.59.220 :20900...
2018-12-27T20:17:58+01:00 - info: Connecting to address 77.152.31.154 :20901...
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.bertrandbenjamin.com :443...
2018-12-27T20:17:58+01:00 - info: Connecting to address follow.the.white-rabbit.net :18882...
2018-12-27T20:17:58+01:00 - info: Connecting to address duniter.fabwice.com :443...
2018-12-27T20:17:58+01:00 - info: Connecting to address 81.57.152.178 :20900...
2018-12-27T20:17:58+01:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT::4VZkro3N7VonygybESHngKUABA6gSrbW77Ktb94zE969:a3901c87-b682-4c77-be92-c47950bd8c3154b6acf1-98d0-46e6-ac42-920569e7b895
2018-12-27T20:17:58+01:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2018-12-27T20:17:58+01:00 - trace: WS2P >>> sendCONNECT >>> WS2P:SYNC::GRBPV3Y7PQnB9LaZhSGuS3BqBJbSHyibzYq65kTh1nQ4:f2290a96-9f49-4cee-89b1-5178bb07039a61c11166-2485-4b69-8f75-1d6d60499ad2
2018-12-27T20:17:58+01:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT::CRBxCJrTA6tmHsgt9cQh9SHcCc8w8q95YTp38CPHx2Uk:4b4fbadc-5539-4ac2-938b-9e08c96dfcf72af542a5-13dc-4384-83c5-ac2b0f6b6740
2018-12-27T20:17:58+01:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2018-12-27T20:17:58+01:00 - trace: WS2P >>> sendCONNECT >>> WS2P:SYNC::GRBPV3Y7PQnB9LaZhSGuS3BqBJbSHyibzYq65kTh1nQ4:b75a7699-1634-49c2-9776-753424809115ad0a770f-9e45-44cf-87d5-6664d4016449
2018-12-27T20:17:58+01:00 - info: Connecting to address g1.nordstrom.duniter.org :443...
2018-12-27T20:17:59+01:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:Be1eVp7etVfA7cT6er6dcJ9d5KxGJVY2tzCGGCAz3yG:d5fff255-c22f-4351-9ec3-d2648fd809644bbd2c04-eb8c-4535-8525-691b2ab9206b
2018-12-27T20:17:59+01:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:GRBPV3Y7PQnB9LaZhSGuS3BqBJbSHyibzYq65kTh1nQ4:d5fff255-c22f-4351-9ec3-d2648fd809644bbd2c04-eb8c-4535-8525-691b2ab9206b
2018-12-27T20:17:59+01:00 - trace: WS2P >>> sendCONNECT >>> WS2P:SYNC:g1:GRBPV3Y7PQnB9LaZhSGuS3BqBJbSHyibzYq65kTh1nQ4:3d33938e-ce44-4f2b-8048-18f78b43ad224702a400-9c7b-4c13-a607-2f980a7863ad
2018-12-27T20:17:59+01:00 - trace: WS2P >>> registerOK >>> WS2P:OK:g1:Be1eVp7etVfA7cT6er6dcJ9d5KxGJVY2tzCGGCAz3yG:d5fff255-c22f-4351-9ec3-d2648fd809644bbd2c04-eb8c-4535-8525-691b2ab9206b
2018-12-27T20:17:59+01:00 - trace: WS2P >>> registerACK >>> WS2P:ACK:g1:Be1eVp7etVfA7cT6er6dcJ9d5KxGJVY2tzCGGCAz3yG:3d33938e-ce44-4f2b-8048-18f78b43ad224702a400-9c7b-4c13-a607-2f980a7863ad
2018-12-27T20:17:59+01:00 - trace: WS2P >>> sendOK >>> WS2P:OK:g1:GRBPV3Y7PQnB9LaZhSGuS3BqBJbSHyibzYq65kTh1nQ4:3d33938e-ce44-4f2b-8048-18f78b43ad224702a400-9c7b-4c13-a607-2f980a7863ad
2018-12-27T20:17:59+01:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT::DTgQ97AuJ8UgVXcxmNtULAs8Fg1kKC1Wr9SAS96Br9NG:19aada23-8100-499d-bf28-58fafeabfd59b42158f7-0a41-477f-8cab-f8c20bdff5f8
2018-12-27T20:17:59+01:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2018-12-27T20:17:59+01:00 - trace: WS2P >>> sendCONNECT >>> WS2P:SYNC::GRBPV3Y7PQnB9LaZhSGuS3BqBJbSHyibzYq65kTh1nQ4:a76e0879-052e-4394-a529-43ec612f3d76408116aa-2157-4808-b4c7-3398f07f0cd2
2018-12-27T20:17:59+01:00 - debug: Total tx count: 60
2018-12-27T20:17:59+01:00 - trace: Alfybe was affected wotb_id 0
2018-12-27T20:17:59+01:00 - trace: AnneAmbles was affected wotb_id 1
2018-12-27T20:17:59+01:00 - trace: Ariane was affected wotb_id 2
2018-12-27T20:17:59+01:00 - trace: Audrey35 was affected wotb_id 3
2018-12-27T20:17:59+01:00 - info: Milestones 1%, Downloaded 0%, Applied 0%
2018-12-27T20:17:59+01:00 - trace: BenoitLavenier was affected wotb_id 4
2018-12-27T20:17:59+01:00 - trace: BernardORSONI was affected wotb_id 5
2018-12-27T20:17:59+01:00 - trace: CaizohanFerreira was affected wotb_id 6
2018-12-27T20:17:59+01:00 - trace: CaroleFabre was affected wotb_id 7
2018-12-27T20:17:59+01:00 - trace: CatherineLeroy was affected wotb_id 8
2018-12-27T20:18:00+01:00 - trace: DamienChretien was affected wotb_id 9
2018-12-27T20:18:00+01:00 - trace: Darunya was affected wotb_id 10
2018-12-27T20:18:00+01:00 - trace: EstienneDunord was affected wotb_id 11
2018-12-27T20:18:00+01:00 - trace: Fiatoux was affected wotb_id 12
2018-12-27T20:18:00+01:00 - trace: Francisco was affected wotb_id 13
2018-12-27T20:18:00+01:00 - trace: Gaelle was affected wotb_id 14
2018-12-27T20:18:00+01:00 - trace: Galuel was affected wotb_id 15
2018-12-27T20:18:00+01:00 - trace: HubertGicqueau was affected wotb_id 16
2018-12-27T20:18:00+01:00 - info: Milestones 2%, Downloaded 0%, Applied 0%
2018-12-27T20:18:00+01:00 - trace: JoelCaillerie was affected wotb_id 17
2018-12-27T20:18:00+01:00 - trace: Loda was affected wotb_id 18
2018-12-27T20:18:00+01:00 - trace: LudovicPecquot was affected wotb_id 19
2018-12-27T20:18:00+01:00 - trace: MarcelDoppagne was affected wotb_id 20
2018-12-27T20:18:00+01:00 - trace: MariPotter was affected wotb_id 21
2018-12-27T20:18:00+01:00 - trace: Mententon was affected wotb_id 22
2018-12-27T20:18:00+01:00 - trace: Paulart was affected wotb_id 23
2018-12-27T20:18:00+01:00 - trace: Philippe26 was affected wotb_id 24
2018-12-27T20:18:00+01:00 - trace: SebasC was affected wotb_id 25
2018-12-27T20:18:00+01:00 - info: Milestones 2%, Downloaded 1%, Applied 0%
2018-12-27T20:18:00+01:00 - trace: Sybille was affected wotb_id 26
2018-12-27T20:18:00+01:00 - trace: Thatoo was affected wotb_id 27
2018-12-27T20:18:00+01:00 - info: Milestones 3%, Downloaded 1%, Applied 0%
2018-12-27T20:18:01+01:00 - trace: Tortue was affected wotb_id 28
2018-12-27T20:18:01+01:00 - trace: William was affected wotb_id 29
2018-12-27T20:18:01+01:00 - trace: YoanSallami was affected wotb_id 30
2018-12-27T20:18:01+01:00 - trace: bou2fil was affected wotb_id 31
2018-12-27T20:18:01+01:00 - trace: candide was affected wotb_id 32
2018-12-27T20:18:01+01:00 - trace: cgeek was affected wotb_id 33
2018-12-27T20:18:01+01:00 - trace: cuckooland was affected wotb_id 34
2018-12-27T20:18:01+01:00 - trace: elois was affected wotb_id 35
2018-12-27T20:18:01+01:00 - trace: fbuland was affected wotb_id 36
2018-12-27T20:18:01+01:00 - trace: fluidlog was affected wotb_id 37
2018-12-27T20:18:01+01:00 - trace: gege53 was affected wotb_id 38
2018-12-27T20:18:01+01:00 - trace: gerard94 was affected wotb_id 39
2018-12-27T20:18:01+01:00 - trace: gpsqueeek was affected wotb_id 40
2018-12-27T20:18:01+01:00 - info: Milestones 3%, Downloaded 2%, Applied 0%
2018-12-27T20:18:01+01:00 - trace: greyzlii was affected wotb_id 41
2018-12-27T20:18:01+01:00 - trace: inso was affected wotb_id 42
2018-12-27T20:18:01+01:00 - info: Connecting to address follow.the.white-rabbit.net :8882...
2018-12-27T20:18:01+01:00 - trace: jeanferreira was affected wotb_id 43
2018-12-27T20:18:02+01:00 - trace: jytou was affected wotb_id 44
2018-12-27T20:18:02+01:00 - trace: manu was affected wotb_id 45
2018-12-27T20:18:02+01:00 - trace: mathieuBize was affected wotb_id 46
2018-12-27T20:18:02+01:00 - trace: mimi was affected wotb_id 47
2018-12-27T20:18:02+01:00 - trace: moul was affected wotb_id 48
2018-12-27T20:18:02+01:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT::HnQH8P6n5q3mqNk8V9zP44shmZJbqWJJfJfU7ZfTBung:d3991f07-60ca-413f-97ca-4341d8cc9f6fdfe9313e-4a4d-42a2-8944-6640b2e44a22
2018-12-27T20:18:02+01:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2018-12-27T20:18:02+01:00 - trace: WS2P >>> sendCONNECT >>> WS2P:SYNC::GRBPV3Y7PQnB9LaZhSGuS3BqBJbSHyibzYq65kTh1nQ4:6f0973dc-04fe-445b-ba58-ef6746e1f65dde37ee3b-438d-4ee8-a3f1-09f4a0d49d5c
2018-12-27T20:18:02+01:00 - info: Milestones 4%, Downloaded 2%, Applied 0%
2018-12-27T20:18:02+01:00 - trace: nay4 was affected wotb_id 49
2018-12-27T20:18:02+01:00 - trace: nicoleC was affected wotb_id 50
2018-12-27T20:18:02+01:00 - trace: pafzedog was affected wotb_id 51
2018-12-27T20:18:02+01:00 - trace: saintmerlin was affected wotb_id 52
2018-12-27T20:18:02+01:00 - trace: simonelion was affected wotb_id 53
2018-12-27T20:18:02+01:00 - trace: simons was affected wotb_id 54
2018-12-27T20:18:02+01:00 - trace: smyds was affected wotb_id 55
2018-12-27T20:18:02+01:00 - trace: vincentux was affected wotb_id 56
2018-12-27T20:18:02+01:00 - trace: vit was affected wotb_id 57
2018-12-27T20:18:02+01:00 - trace: yannlefranco was affected wotb_id 58
2018-12-27T20:18:02+01:00 - info: Milestones 5%, Downloaded 2%, Applied 0%
2018-12-27T20:18:02+01:00 - info: Milestones 5%, Downloaded 3%, Applied 0%
2018-12-27T20:18:02+01:00 - info: Milestones 6%, Downloaded 3%, Applied 0%
2018-12-27T20:18:02+01:00 - info: Milestones 6%, Downloaded 4%, Applied 0%
2018-12-27T20:18:02+01:00 - info: Milestones 6%, Downloaded 5%, Applied 0%
2018-12-27T20:18:03+01:00 - info: Milestones 7%, Downloaded 5%, Applied 0%
2018-12-27T20:18:03+01:00 - info: Milestones 8%, Downloaded 5%, Applied 0%
2018-12-27T20:18:03+01:00 - info: Milestones 9%, Downloaded 5%, Applied 0%
terminate called after throwing an instance of 'std::out_of_range'
  what():  vector::_M_range_check
/usr/bin/duniter : ligne 15 : 11866 Abandon                 $NODE "$DUNITER_DIR/bin/duniter" "$@"
1 Like