Impossible de synchroniser mon noeud Duniter V1

Frederic_LASSAVE · 23 July 2023 17:57

Ah oui, il est bloqué à une centaine de blocs … J’essaie ça de suite

[EDIT] J"ai donc fait un

duniter webrestart

Le noeud tourne mais j’ai l’impression qu’il ne se connecte à aucun “pairs” …

[EDIT2]

2023-07-23T20:02:59+02:00 info Matched 5 zeros 00000C43C421632202B3AFD17E867F62D5D670AAD09B318717632B1626538A98 with Nonce = 10100001097933 for block#646066 by FEcfFy

2023-07-23T20:03:50+02:00 info Matched 5 zeros 00000775540748918382A9139851F2FA84174214F5C0AE4040272BFEBD7E9FA4 with Nonce = 10200001386423 for block#646066 by FEcfFy

2023-07-23T20:04:53+02:00 info Matched 5 zeros 0000092608BE2CA45C4D2AF587BACDC568320D0E3D089B7CA07241F5D1D2B728 with Nonce = 10100001915683 for block#646066 by FEcfFy

2023-07-23T20:08:52+02:00 info Block resolution: 1 potential blocks after current#646065...

2023-07-23T20:08:53+02:00 error 

2023-07-23T20:08:53+02:00 info Block resolution: 1 potential blocks after current#646065...

2023-07-23T20:08:53+02:00 error 

2023-07-23T20:13:48+02:00 info Matched 5 zeros 00000F3B5DCD33D253BA740A8524A5EEEDE20572A425335D555332608CF04461 with Nonce = 10100004928360 for block#646066 by FEcfFy

2023-07-23T20:15:51+02:00 info Matched 5 zeros 0000051B40D6AB9ED407C8087FF779C64746D8AC2D3C1F2FF55C9393EE3005AB with Nonce = 10200005762611 for block#646066 by FEcfFy

2023-07-23T20:16:24+02:00 error Error: timeout
    at Timeout._onTimeout (/opt/duniter/node_modules/nat-upnp/lib/nat-upnp/client.js:187:14)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

2023-07-23T20:16:38+02:00 info Sibling endpoints:

2023-07-23T20:16:48+02:00 error Error: timeout
    at Timeout._onTimeout (/opt/duniter/node_modules/nat-upnp/lib/nat-upnp/client.js:187:14)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

2023-07-23T20:17:22+02:00 info Matched 5 zeros 00000745B5DB15CB14F92C1AB4C6D015D4D239C046304F3CD7BA8549C87C8DC2 with Nonce = 10200006169203 for block#646066 by FEcfFy

2023-07-23T20:18:52+02:00 info Block resolution: 1 potential blocks after current#646065...

2023-07-23T20:18:53+02:00 error 

2023-07-23T20:18:53+02:00 info Block resolution: 1 potential blocks after current#646065...

2023-07-23T20:18:54+02:00 error 

2023-07-23T20:19:47+02:00 info Matched 5 zeros 00000C4CBE2CA5110E08876045C636E632F141153D0FB46B279DE4470E61B434 with Nonce = 10200006708704 for block#646066 by FEcfFy

Pini · 23 July 2023 19:26

Dans ce cas je tente de redémarrer plusieures fois, et si ça ne marche pas je recommence tout avec synchro complète.

Et si ça ne marche toujours pas, au bout de deux ou trois essais, ben je ne sais pas

Frederic_LASSAVE · 24 July 2023 10:26

J’ai relancé une synchro cette nuit, avec la commande :

export NODE_OPTIONS=--max-old-space-size=6144

J’ai redémarré le noeud plusieurs fois, mais il reste bloqué au bloc 646218 …

Pini · 24 July 2023 10:28

On atteint mes limites de compétences. Désolé

Frederic_LASSAVE · 24 July 2023 11:09

Merci pour tous tes conseils ! J’ai pu avancer un peu

Frederic_LASSAVE · 25 July 2023 19:28

Pour faire suite, et fin j’espère , j’ai donc fait ceci :

export NODE_OPTIONS=--max-old-space-size=5120

Puis :

duniter sync g1.cgeek.fr

Ça a duré super longtemps …
Puis :

duniter webrestart

Ouais, parce que je suis faignant et le serveur a raccroché
Merci pour tout !!

flodef · 26 July 2023 19:15

Bravo pour ta persévérance !
Et le partage de ta réussite !

MikaPac · 6 August 2023 17:36

Bonjour,

J’ai également une erreur lorsque je fais une synchro (première installation de Duniter) à 96% de téléchargement et 94% appliqué.

j’ai d’autres screenshots mais comme je suis nouveau je peux pas les mettre dans le même message.

Au moment où ça a crashé, je crois que j’étais à 3Go de ram de consommation au total, sachant que ça tourne sur une VM avec un coeur i7 11700 et 30Go (c’était au cas où) de ram disponible pour la VM.
Je suis en 1.8.7rc4 et Linux Mint (je ne sais plus quelle version mais elle date à peu près d’un mois)

kimamila · 7 August 2023 09:39

Bonjour @MikaPac oui, c’est un pb mémoire. Cf les posts ci-dessus pour savoir comment augmenter. a+

MikaPac · 7 August 2023 16:33

[quote=“Frederic_LASSAVE, post:4, topic:11427”] au lieu de
export NODE_OPTIONS=--max-old-space-size=8192
[/quote]

ça marche avec la commande export NODE_OPTIONS=–max-old-space-size=8192

Merci kimamila

Par contre maintenant je bloque sur l’accès au noeud… Je l’ai lancé en webstart, j’ai configuré le port 10901, et impossible d’y accéder en localhost avec firefox. → correction, j’essayais avec le port 10901 au lieu de 9220… par contre, il ne le trouve pas quand je l’indique dans l’appli cesium. → bizarrement je viens de voir que ça fonctionne dans l’extension cesium de chromium… je vais voir par après si ça fonctionne dans l’appli → bon impossible de me connecter à mon noeud dans l’appli android (il me jette direct en m’indiquant que mon noeud est inaccessible), problème que je n’ai pas depuis l’extension chromium.

l’adresse de mon noeud : pac.mikapac.be:10901 (pas de SSL)

Damery · 8 August 2023 13:29

Sync KO !!! Que faire, docteur ?
Status: GOT chunk #2474/2602 from 618500 to 618749 on peer g1.le-sou.org
<— Last few GCs —>

[512112:0x3969900] 22852466 ms: Mark-sweep 1350.0 (1439.6) → 1333.5 (1439.6) MB, 2586.8 / 10.8 ms (average mu = 0.256, current mu = 0.156) allocation failure scavenge might not succeed
[512112:0x3969900] 22855413 ms: Mark-sweep 1350.3 (1439.6) → 1333.5 (1439.6) MB, 2521.4 / 2.4 ms (average mu = 0.204, current mu = 0.144) allocation failure scavenge might not succeed

<— JS stacktrace —>

==== JS stack trace =========================================

0: ExitFrame [pc: 0x4a136855941]

Security context: 0x374b9d31e6c1
1: toString [0x24b1264a0651] [buffer.js:~643] [pc=0x4a13b689d56](this=0x109016a8e311 ,encoding=0x1258f93826f1 ,start=0x1258f93826f1 ,end=0x1258f93826f1 )
2: arguments adaptor frame: 0->3
3: InternalFrame [pc: 0x4a13678ee75]
4: EntryFrame [pc: 0x4a1367892c1]
5: ExitFrame [pc: …

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0x8fb090 node::Abort() [/opt/duniter//node/bin/node]
2: 0x8fb0dc [/opt/duniter//node/bin/node]
3: 0xb031ce v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/opt/duniter//node/bin/node]
4: 0xb03404 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/opt/duniter//node/bin/node]
5: 0xef7462 [/opt/duniter//node/bin/node]
6: 0xef7568 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/opt/duniter//node/bin/node]
7: 0xf03642 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/opt/duniter//node/bin/node]
8: 0xf03f74 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/opt/duniter//node/bin/node]
9: 0xf06be1 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/opt/duniter//node/bin/node]
10: 0xeceec5 [/opt/duniter//node/bin/node]
11: 0xed673a v8::internal::NewRawOneByteString(int, v8::internal::PretenureFlag) [/opt/duniter//node/bin/node]
12: 0xed6a4b v8::internal::NewStringFromOneByte(v8::internal::Vector, v8::internal::PretenureFlag) [/opt/duniter//node/bin/node]
13: 0xed749d v8::internal::NewStringFromUtf8(v8::internal::Vector, v8::internal::PretenureFlag) [/opt/duniter//node/bin/node]
14: 0xb11129 v8::String::NewFromUtf8(v8::Isolate*, char const*, v8::NewStringType, int) [/opt/duniter//node/bin/node]
15: 0x9c37e8 node::StringBytes::Encode(v8::Isolate*, char const*, unsigned long, node::encoding, v8::Localv8::Value*) [/opt/duniter//node/bin/node]
16: 0x9177a0 [/opt/duniter//node/bin/node]
17: 0x4a136855941
/usr/bin/duniter : ligne 15 : 512112 Abandon (core dumped) $NODE “DUNITER_DIR/bin/duniter" "@”

JProd · 8 August 2023 14:36

refaire une synchro en baissant la valeur size par exemple a 4096
export NODE_OPTIONS=–max-old-space-size=4096
et
duniter sync noeud.host --nointeractive

ici ca s est synchro comme ca avec 8go de ram

Damery · 8 August 2023 15:16

C’est lancé … A+ pour +
Lancée à 16h55, la synchro est toujours en cours (22h16)

Damery · 9 August 2023 02:37

KO !!!

2023-08-08T23:22:03+02:00 - trace: Eglantine was affected wotb_id 12119
2023-08-08T23:22:03+02:00 - trace: Charbel45 was affected wotb_id 12120

<— Last few GCs —>

[774743:0x3f6f950] 23170301 ms: Mark-sweep 1311.5 (1391.1) → 1311.4 (1391.1) MB, 2075.0 / 0.0 ms (average mu = 0.232, current mu = 0.000) last resort GC in old space requested
[774743:0x3f6f950] 23172519 ms: Mark-sweep 1311.4 (1391.1) → 1311.4 (1390.1) MB, 2218.7 / 0.0 ms (average mu = 0.126, current mu = 0.000) last resort GC in old space requested

<— JS stacktrace —>

==== JS stack trace =========================================

0: ExitFrame [pc: 0x1bc25c45be1d]

Security context: 0x167c77f1e6c1
1: reduceBy [0x2261ecdd0f19] [/opt/duniter/app/lib/indexer.js:~1765] [pc=0x1bc25d8fdda6](this=0x2261ecdd5d89 ,reducables=0x2c1b6d9956a9 <JSArray[36]>,properties=0x2c1b6d995719 <JSArray[2]>)
2: /* anonymous /(aka / anonymous */) [0x2c1b6d987321] [/opt/duniter/app/lib/dal/indexDAL/leveldb/LevelDBCindex.js:234] [bytecode=0…

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
1: 0x8fb090 node::Abort() [/opt/duniter//node/bin/node]
2: 0x8fb0dc [/opt/duniter//node/bin/node]
3: 0xb031ce v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/opt/duniter//node/bin/node]
4: 0xb03404 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/opt/duniter//node/bin/node]
5: 0xef7462 [/opt/duniter//node/bin/node]
6: 0xf06c7f v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/opt/duniter//node/bin/node]
7: 0xecfcd6 v8::internal::AllocateRawArray(int, v8::internal::PretenureFlag) [/opt/duniter//node/bin/node]
8: 0xed055a v8::internal::NewFixedArrayWithFiller(v8::internal::Heap::RootListIndex, int, v8::internal::Object*, v8::internal::PretenureFlag) [/opt/duniter//node/bin/node]
9: 0xed0600 v8::internal::Handlev8::internal::FixedArray v8::internal::NewFixedArrayWithMapv8::internal::FixedArray(v8::internal::Heap::RootListIndex, int, v8::internal::PretenureFlag) [/opt/duniter//node/bin/node]
10: 0x100b430 v8::internal::HashTable<v8::internal::StringTable, v8::internal::StringTableShape>::NewInternal(v8::internal::Isolate*, int, v8::internal::PretenureFlag) [/opt/duniter//node/bin/node]
11: 0x100b48e v8::internal::HashTable<v8::internal::StringTable, v8::internal::StringTableShape>::New(v8::internal::Isolate*, int, v8::internal::PretenureFlag, v8::internal::MinimumCapacity) [/opt/duniter//node/bin/node]
12: 0x101e43f v8::internal::HashTable<v8::internal::StringTable, v8::internal::StringTableShape>::EnsureCapacity(v8::internal::Handlev8::internal::StringTable, int, v8::internal::PretenureFlag) [/opt/duniter//node/bin/node]
13: 0x101e645 v8::internal::StringTable::LookupKey(v8::internal::Isolate*, v8::internal::StringTableKey*) [/opt/duniter//node/bin/node]
14: 0x102128c v8::internal::StringTable::LookupString(v8::internal::Isolate*, v8::internal::Handlev8::internal::String) [/opt/duniter//node/bin/node]
15: 0x11972db [/opt/duniter//node/bin/node]
16: 0x11994e9 v8::internal::Runtime_KeyedGetProperty(int, v8::internal::Object**, v8::internal::Isolate*) [/opt/duniter//node/bin/node]
17: 0x1bc25c45be1d
/usr/bin/duniter : ligne 15 : 774743 Abandon (core dumped) $NODE “DUNITER_DIR/bin/duniter" "@”

Que faire ?

Frederic_LASSAVE · 9 August 2023 07:09

Tu lances quelle commande pour synchroniser ?

Tu stoppes le serveur, avant la synchro ?

Tu as désactivé le cron (ou autre ?) qui relance automatiquement le noeud ?

Damery · 9 August 2023 07:51

Duniter stop
Duniter reset data
Suppression des fichiers du .config (sauf keyring et conf.json (c’est la commande lancée à 4h du mat et qui tourne toujours)
duniter sync g1.duniter.org --nointeractive
Aïe, non, je n’ai pas désactivé la cron table … mais la commande se lance à 1h45 du matin …

Damery · 9 August 2023 09:18

Flûte !! Même chose !
2023-08-09T10:59:38+02:00 - trace: Felicia was affected wotb_id 12098
2023-08-09T10:59:46+02:00 - trace: Titev11 was affected wotb_id 12099
2023-08-09T10:59:52+02:00 - trace: PatriciaLAGIER was affected wotb_id 12100
2023-08-09T10:59:52+02:00 - trace: MTCmlaure was affected wotb_id 12101

<— Last few GCs —>

[1153134:0x31d4940] 22861909 ms: Scavenge 1352.8 (1437.6) → 1340.7 (1437.6) MB, 11.1 / 0.0 ms (average mu = 0.310, current mu = 0.320) allocation failure
[1153134:0x31d4940] 22862038 ms: Scavenge 1354.5 (1437.6) → 1342.2 (1438.1) MB, 12.0 / 0.0 ms (average mu = 0.310, current mu = 0.320) allocation failure
[1153134:0x31d4940] 22862203 ms: Scavenge 1356.1 (1438.1) → 1343.6 (1439.6) MB, 12.1 / 0.0 ms (average mu = 0.310, current mu = 0.320) allocation failure

<— JS stacktrace —>

==== JS stack trace =========================================

Security context: 0x3923f8b9e6c1
0: builtin exit frame: parse(this=0x3923f8b919f9 ,0x3be523f9a201 <Very long string[10401]>,0x3923f8b919f9 )

1: /* anonymous */ [0x3245777316c9] [/opt/duniter/app/lib/dal/indexDAL/leveldb/LevelDBTable.js:~73] [pc=0x39b2e9b179b0](this=0x324577731749 <ReadStream map = 0x100e378a659>,data=0x3be523f8df01 <Object map = 0x100e379d7f1>)

…

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0x8fb090 node::Abort() [/opt/duniter//node/bin/node]
2: 0x8fb0dc [/opt/duniter//node/bin/node]
3: 0xb031ce v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/opt/duniter//node/bin/node]
4: 0xb03404 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/opt/duniter//node/bin/node]
5: 0xef7462 [/opt/duniter//node/bin/node]
6: 0xef7568 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/opt/duniter//node/bin/node]
7: 0xf03642 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/opt/duniter//node/bin/node]
8: 0xf03f74 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/opt/duniter//node/bin/node]
9: 0xf06be1 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/opt/duniter//node/bin/node]
10: 0xedbec0 [/opt/duniter//node/bin/node]
11: 0xedbf57 v8::internal::NewJSObject(v8::internal::Handlev8::internal::JSFunction, v8::internal::PretenureFlag) [/opt/duniter//node/bin/node]
12: 0xfc7136 v8::internal::JsonParser::ParseJsonObject() [/opt/duniter//node/bin/node]
13: 0xfc7f90 v8::internal::JsonParser::ParseJsonValue() [/opt/duniter//node/bin/node]
14: 0xfc8425 v8::internal::JsonParser::ParseJsonArray() [/opt/duniter//node/bin/node]
15: 0xfc7fa0 v8::internal::JsonParser::ParseJsonValue() [/opt/duniter//node/bin/node]
16: 0xfc74dc v8::internal::JsonParser::ParseJsonObject() [/opt/duniter//node/bin/node]
17: 0xfc7f90 v8::internal::JsonParser::ParseJsonValue() [/opt/duniter//node/bin/node]
18: 0xfc8004 v8::internal::JsonParser::ParseJson() [/opt/duniter//node/bin/node]
19: 0xbd7ad8 v8::internal::Builtin_JsonParse(int, v8::internal::Object**, v8::internal::Isolate*) [/opt/duniter//node/bin/node]
20: 0x39b2e32dbf7d
/usr/bin/duniter : ligne 15 : 1153134 Abandon (core dumped) $NODE “DUNITER_DIR/bin/duniter" "@”

Erreur : FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
Du coup, j’essaie de remonter à 8192 et relance (j’ai stoppé la crontab)

kimamila · 9 August 2023 10:49

Que peux tu comprendre de cette ligne de ton log ?

Voilà !

Damery · 9 August 2023 15:39

Même plantage après plus de 6h de synchro …
Comment faire ?
Repasser en V1.8.6 ?
Merci de vos conseils.

Damery · 10 August 2023 14:16

Autre idée qu’il m’est arrivé d’utiliser.
Cédric ou quelqu’un d’autre qui aurait un noeud en 1.8.7 pourrait-il le zipper et me le mettre à disposition sur un cloud ?
Je puis fournir le cloud si besoin (infomaniak).
Si cela est possible à l’un d’entre vous, merci de m’envoyer un texto pour contact au 0686149375
Ensuite, je me débrouille
@cgeek