Synchro impossible Nœud v1

joss.rendall · 11 April 2023 15:02

Bonjour à Tous !!
Voila 1 semaine que je n’arrive pas à resynchro mon noeud 1.8.5 sous Yunohost !!

voila le log de sortie :

root@lesfoisonnantes:/home/rendall# sudo systemctl stop duniter && sudo su - duniter -c "duniter --home \$HOME sync g1.duniter.org" && sudo systemctl start duniter
2023-04-11T12:04:37+02:00 - debug: Plugging file system...
2023-04-11T12:04:37+02:00 - debug: Loading conf...
2023-04-11T12:04:37+02:00 - debug: Configuration saved.
2023-04-11T12:04:37+02:00 - debug: Opening SQLite database "/home/yunohost.app/duniter/duniter_default/duniter.db"...
2023-04-11T12:07:19+02:00 - debug: Now open indexers...
2023-04-11T12:07:19+02:00 - debug: Opening SQLite database "/home/yunohost.app/duniter/duniter_default/txs.db"...
2023-04-11T12:07:19+02:00 - debug: Opening SQLite database "/home/yunohost.app/duniter/duniter_default/peers.db"...
2023-04-11T12:07:20+02:00 - debug: Upgrade database...
2023-04-11T12:07:20+02:00 - info: Block resolution: 0 potential blocks for root block...
Progress:

Milestones:   [||||||||||||||||||||] 100 %
Download:     [||||||||||||||||||||] 100 %
Apply:        [||||||||||||||||||| ] 99 %
Sandbox:      [                    ] 0 %
Peers:        [                    ] 0 %

Status: GOT chunck #2466/2468 from 616500 to 616749 on peer 83.198.62.173
<--- Last few GCs --->1 pipe listeners added. Use emitter.setMaxListeners() to increase limit
[2330:0x3082960] 17019994 ms: Mark-sweep 1260.0 (1367.6) -> 1260.0 (1363.6) MB, 950.5 / 0.0 ms  (average mu = 0.268, current mu = 0.000) last resort GC in old space requested
[2330:0x3082960] 17021062 ms: Mark-sweep 1260.0 (1363.6) -> 1260.0 (1363.6) MB, 1068.1 / 0.0 ms  (average mu = 0.149, current mu = 0.000) last resort GC in old space requested


<--- JS stacktrace --->

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

    0: ExitFrame [pc: 0x32738cf64f41]
Security context: 0x10a0430dc8b1 <JSObject>
    1: getOrNull [0x13c5e3b5f09] [/opt/duniter/app/lib/dal/indexDAL/leveldb/LevelDBTable.js:~20] [pc=0x32738d46b003](this=0x1c8bdb002611 <LevelDBTable map = 0x31000a171751>,k=0x04b8df302aa9 <String[10]: 0000613574>)
    2: indexConsumptions [0x13c5e3b5289] [/opt/duniter/app/lib/dal/indexDAL/leveldb/LevelDBDividend.js:~43] [pc=0x32738e5730dd](this=0x2f9a89be1...

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::Factory::AllocateRawArray(int, v8::internal::PretenureFlag) [/opt/duniter//node/bin/node]
 8: 0xed055a v8::internal::Factory::NewFixedArrayWithFiller(v8::internal::Heap::RootListIndex, int, v8::internal::Object*, v8::internal::PretenureFlag) [/opt/duniter//node/bin/node]
 9: 0xed0600 v8::internal::Handle<v8::internal::FixedArray> v8::internal::Factory::NewFixedArrayWithMap<v8::internal::FixedArray>(v8::internal::Heap::RootListIndex, int, v8::internal::PretenureFlag) [/opt/duniter//node/bin/nod                                                                                                                            e]
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::Handle<v8::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: 0xed123b v8::internal::Factory::InternalizeUtf8String(v8::internal::Vector<char const>) [/opt/duniter//node/bin/node]
15: 0xb1119b v8::String::NewFromUtf8(v8::Isolate*, char const*, v8::NewStringType, int) [/opt/duniter//node/bin/node]
16: 0x90b0c6 napi_has_named_property [/opt/duniter//node/bin/node]
17: 0x7f90492f635e db_get(napi_env__*, napi_callback_info__*) [/opt/duniter/node_modules/leveldown/prebuilds/linux-x64/node.napi.glibc.node]
18: 0x906e35  [/opt/duniter//node/bin/node]
19: 0x32738cf64f41
/usr/bin/duniter: line 15:  2330 Aborted                 $NODE "$DUNITER_DIR/bin/duniter" "$@"

Une aide serait la bienvenue chers camarades d’Axiom.

Sign : Rendall d’Axiom Team PACA

joss.rendall · 11 April 2023 15:26

déjà merci et désolé pour la mise en page …
et ci-dessous les logs accessibles depuis la WebGui
g1.lesfoisonnantes.fr.txt (23,6 Ko)

Pini · 11 April 2023 16:57

D’après la doc de node:events ce warning est juste informatif, pour aider à détecter d’éventuels memory leaks :

This is not a hard limit. The EventEmitter instance will allow more listeners to be added but will output a trace warning to stderr indicating that a “possible EventEmitter memory leak” has been detected.

Je ne l’ai rencontré pour ma part que lors de séquences bundle of peers où le nombre de peers est supérieur à 10. Tout à fait normal donc, puisque la valeur par défaut est 10.

Moul · 11 April 2023 17:04

Une utilisation trop importante de RAM pour la RAM installée :

Pini · 11 April 2023 17:12

Quand tu synchronises il faut au préalable avoir supprimé les données :

systemctl stop duniter
rm -fr /home/yunohost.app/duniter/duniter_default/data
su - duniter -c "duniter --home \$HOME sync g1.duniter.org"
systemctl start duniter

Note : je vois que tu es root au moment de passer ces commandes. Inutile donc d’utiliser sudo.

Moul · 11 April 2023 17:25

Pour le paquet YunoHost, les commandes doivent être lancées avec l’utilisateur duniter autrement il y a des problèmes de droits lors de l’exécution de Duniter.

joss.rendall · 12 April 2023 06:45

Mon VPS possède 8Go… grâce à Netdata monitoring, on voit que la consommation de RAM n’a jamais dépassé 4 Go…
Comme le Noeud se désynchronise de façon chronique, est il vraiement nécessaire de supprimer toute les données avant une nouvelle synchro ?

joss.rendall · 12 April 2023 06:53

Ok pour l’utilisateur Duniter mais Quid mot de pass de cet utilisateur pour lancer les commandes depuis ce compte… (su duniter) ?

Moul · 12 April 2023 06:59

Vérifie que les connexions WS2P sont bien établies et que ton endpoint WS2P est bien configuré, autrement il se désynchronise.

Non, lancer une synchronisation, supprime les données avant de se lancer.

Il n’ y a pas de mot de passe configuré pour l’utilisateur duniter lors de sa création. Tu peux passer root, puis duniter sans mot de passe.

sudo -i
su - duniter

joss.rendall · 12 April 2023 07:06

merci de ces retours rapides et constructifs !!
regarde, STP, dans le fichier log joint à mon second post, effectivement j’ai des alertes sur le WS2P.

Moul · 12 April 2023 07:08

Il y a des problèmes de WS2P, à investiguer.

joss.rendall · 12 April 2023 07:11

je lance une nouvelle synchro depuis l’utilisateur duniter dans un premier temps

mika90 · 12 April 2023 08:15

pareil avec un rasperry pi 4 8go arm64 , impossible de synchroniser ça plante toujours vers les 90 %
j’ai pris la version 1.8.5 armv7 , donc la dernière en date avec cette architecture rien a faire , j’ai essayé des anciennes versions , pareil .
j’ai aussi essayé avec docker , mais aucune version disponible avec cette architecture , je n’en trouve que pour du x86
la je tente une syncro en slow , mais je pense que ca va etre pareil.
j’ai aussi tenté de synchroniser sur mon pc , linux , 6go de ram , pour récupérer le dossier “duniter_default” et le coller sur ma carte sd de mon rasperry , planté aussi

je sèche …

joss.rendall · 13 April 2023 08:06

La Suite…
Synchro impossible à terminer, donc RAZ sur mon Yuno… Desinstall + reinstall = tout propre mais suis bloqué au nœud 596249 pour 617766 à l’heure ou j’écris ces lignes (Ǧinspecte)

2023-04-13T09:56:34+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:41302!

2023-04-13T09:56:34+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:03c8cd47-1f9a-4fed-8861-3b52cecbac901438f3c6-f753-4f27-9744-4ec0dd86828c

2023-04-13T09:56:34+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:56:35+02:00 info ⬇ IDTY 8xaDdHWLpowevFhiUqJH5MAXnADy4hq5UAWJfNTtWRSB Caro18

2023-04-13T09:56:35+02:00 info ✘ IDTY 8xaDdHWLpowevFhiUqJH5MAXnADy4hq5UAWJfNTtWRSB Caro18

2023-04-13T09:56:35+02:00 warn

2023-04-13T09:56:37+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:56:44+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:56:49+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:57:04+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:43208!

2023-04-13T09:57:04+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:8cb31162-125c-4443-9aa2-23a90d3aee2d74526e06-b610-43ba-a575-d4e2871e65a0

2023-04-13T09:57:04+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:57:08+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:48396!

2023-04-13T09:57:08+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:8cba7dab-984f-48f7-89df-e224d88173f543928e2d-7bc1-44a0-b00c-154427538c28

2023-04-13T09:57:08+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:57:09+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:48402!

2023-04-13T09:57:09+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:5d0265fe-f269-4230-b173-4e86f2c4a6bdf8fb5ff5-da2b-4ced-8223-9f533ff21540

2023-04-13T09:57:09+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:48414!

2023-04-13T09:57:09+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:89c85e0f-e993-4651-be58-62b3beef3ea0c9268273-bfc9-47cc-8c59-5f315520ba7d

2023-04-13T09:57:09+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:57:09+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:57:19+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:57:23+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:57:23+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:45302!

2023-04-13T09:57:23+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:f56e37f5-fc15-4456-9f1c-9ef93f2a6832c94e7553-f279-41c7-9e9b-c30de8255cef

2023-04-13T09:57:23+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:57:24+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:57:24+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:57:32+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:49190!

2023-04-13T09:57:32+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:c118e298-db50-438f-8e7e-2710c2f74e92039d6a4b-9ba7-4ffd-823f-99235b356f2c

2023-04-13T09:57:32+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:57:38+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:57:47+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:58:28+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:39408!

2023-04-13T09:58:28+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:0f5007d8-a4e9-40a7-b61d-adbbd3cdefca1ecf308d-51db-47e3-a2ee-93b90bf4a006

2023-04-13T09:58:28+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:58:30+02:00 info ⬇ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:30+02:00 info ✘ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:30+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:30+02:00 info ⬇ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:30+02:00 info ✘ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:30+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:30+02:00 info ⬇ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:30+02:00 info ✘ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:30+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:30+02:00 info ⬇ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:30+02:00 info ✘ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:30+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:30+02:00 info ⬇ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:30+02:00 info ✘ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:30+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:31+02:00 info ⬇ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 info ✘ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:31+02:00 info ⬇ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 info ✘ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:31+02:00 info ⬇ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 info ✘ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:31+02:00 info ⬇ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 info ✘ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:31+02:00 info ⬇ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 info ✘ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:31+02:00 info ⬇ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 info ✘ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:31+02:00 info ⬇ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 info ✘ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:31+02:00 info ⬇ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 info ✘ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:31+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:32+02:00 info ⬇ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:32+02:00 info ✘ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:32+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:32+02:00 info ⬇ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:32+02:00 info ✘ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:32+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:32+02:00 info ⬇ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:32+02:00 info ✘ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:32+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:33+02:00 info ⬇ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:33+02:00 info ✘ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:33+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:34+02:00 info ⬇ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:34+02:00 info ✘ TX 42040:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:34+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:34+02:00 info ⬇ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:34+02:00 info ✘ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:34+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:34+02:00 info ⬇ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:34+02:00 info ✘ TX 50000:0 from 6gyCbnQNwiVhodpYciyBwLcT8KVpeuXRiCjRN34AgcQc

2023-04-13T09:58:34+02:00 warn Wrong blockstamp for transaction

2023-04-13T09:58:36+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:36348!

2023-04-13T09:58:36+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:b8479d55-5197-4301-8f66-6f09ef9a13d82964b018-b2ee-4ad7-bae8-4967540b7986

2023-04-13T09:58:36+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:58:39+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:36352!

2023-04-13T09:58:39+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:e3ffacd3-6c23-4292-a1ba-4edc15b9a8938139c5c1-3e7d-45c8-b8d5-33f41e6d549c

2023-04-13T09:58:39+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:58:43+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:58:51+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:58:51+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:37362!

2023-04-13T09:58:51+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:fe722796-6c2c-44d6-a0fd-f0170a6039004743e366-3cca-43d2-87be-b9b257a35338

2023-04-13T09:58:51+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:58:54+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:59:06+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:59:13+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:55724!

2023-04-13T09:59:13+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:8071bba6-0cc8-44ce-994f-5d14ec8f7e0f2a382c39-cf59-4043-9b08-2c9743efc80c

2023-04-13T09:59:13+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:59:19+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:46538!

2023-04-13T09:59:19+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:aa448691-7783-4b31-b1bc-d5c79bb27fdef814b69b-c76d-4729-9696-79dbe68c626b

2023-04-13T09:59:19+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:59:28+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:59:34+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:59:40+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:35400!

2023-04-13T09:59:40+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:38ae4391-e2cd-4d63-af89-2274780e4d9cad27b876-f927-4882-a022-5caa7f8ca792

2023-04-13T09:59:40+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T09:59:50+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-04-13T09:59:55+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T09:59:57+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:44938!

2023-04-13T09:59:57+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:b715a964-720d-44c1-a865-1a4a53abda5bf40a74fc-910f-4dbb-8689-1dce5371915f

2023-04-13T09:59:57+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T10:00:12+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T10:00:36+02:00 info ⬇ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:36+02:00 info WS2P: init: bundle of peers 1/1

2023-04-13T10:00:36+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:58084!

2023-04-13T10:00:36+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:5c5d08c5-2ed2-41ea-b6c7-37a3d20b3aca33de0207-2975-4429-a0ad-efe31404dcce

2023-04-13T10:00:36+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:50bcda7f-5950-47a1-909e-c5c52f42319c529e33d9-bd25-43e0-848f-43c2b750a8fe

2023-04-13T10:00:36+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T10:00:36+02:00 trace WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:50bcda7f-5950-47a1-909e-c5c52f42319c529e33d9-bd25-43e0-848f-43c2b750a8fe

2023-04-13T10:00:36+02:00 trace WS2P >>> sendACK >>> WS2P:ACK:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:50bcda7f-5950-47a1-909e-c5c52f42319c529e33d9-bd25-43e0-848f-43c2b750a8fe

2023-04-13T10:00:36+02:00 info WS2P: close incoming connection from FCHCfCD3 127.0.0.1:37440

2023-04-13T10:00:36+02:00 warn Security trigger: proof-of-work process seems stuck

2023-04-13T10:00:36+02:00 trace PoW loops = 81

2023-04-13T10:00:36+02:00 warn Local node is not a member. Waiting to be a member before computing a block.

2023-04-13T10:00:36+02:00 info ✘ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:36+02:00 warn Wrong blockstamp for transaction

2023-04-13T10:00:36+02:00 info ⬇ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:36+02:00 info ✘ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:36+02:00 warn Wrong blockstamp for transaction

2023-04-13T10:00:36+02:00 info Blocks were not applied.

2023-04-13T10:00:36+02:00 info Blocks were not applied.

2023-04-13T10:00:37+02:00 info ⬇ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 info ✘ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 warn Wrong blockstamp for transaction

2023-04-13T10:00:37+02:00 info Blocks were not applied.

2023-04-13T10:00:37+02:00 info ⬇ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 info ✘ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 warn Wrong blockstamp for transaction

2023-04-13T10:00:37+02:00 info ⬇ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 info ✘ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 warn Wrong blockstamp for transaction

2023-04-13T10:00:37+02:00 info ⬇ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 info ✘ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 warn Wrong blockstamp for transaction

2023-04-13T10:00:37+02:00 info ⬇ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 info ✘ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 warn Wrong blockstamp for transaction

2023-04-13T10:00:37+02:00 info ⬇ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 info ✘ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 warn Wrong blockstamp for transaction

2023-04-13T10:00:37+02:00 info ⬇ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 info ✘ TX 3500:0 from 8YP66jFgKU2ToHVu8ttFswWrneRVxkdg7FAzdeGqJ3TA

2023-04-13T10:00:37+02:00 warn Wrong blockstamp for transaction

2023-04-13T10:00:39+02:00 info [8umnf6uD] ⬇ PEER A5LQXCkx 617741-0

2023-04-13T10:00:39+02:00 warn Unknown reference block of peer

2023-04-13T10:00:39+02:00 info [8umnf6uD] ⬇ PEER A5LQXCkx 617741-0

2023-04-13T10:00:39+02:00 info [8umnf6uD] ⬇ PEER A5LQXCkx 617741-0

2023-04-13T10:00:39+02:00 warn Unknown reference block of peer

2023-04-13T10:00:39+02:00 info [8umnf6uD] ⬇ PEER A5LQXCkx 617741-0

2023-04-13T10:00:39+02:00 warn Unknown reference block of peer

2023-04-13T10:00:39+02:00 info [8umnf6uD] ⬇ PEER A5LQXCkx 617741-0

2023-04-13T10:00:39+02:00 warn Unknown reference block of peer

2023-04-13T10:00:39+02:00 info [8umnf6uD] ⬇ PEER A5LQXCkx 617741-0

2023-04-13T10:00:39+02:00 warn Unknown reference block of peer

2023-04-13T10:00:39+02:00 info [8umnf6uD] ⬇ PEER A5LQXCkx 617741-0

2023-04-13T10:00:39+02:00 warn Unknown reference block of peer

2023-04-13T10:00:39+02:00 info [8umnf6uD] ⬇ PEER A5LQXCkx 617741-0

2023-04-13T10:00:39+02:00 warn Unknown reference block of peer

2023-04-13T10:00:39+02:00 info [8umnf6uD] ⬇ PEER A5LQXCkx 617741-0

2023-04-13T10:00:39+02:00 warn Unknown reference block of peer

2023-04-13T10:00:51+02:00 info WS2P: Could not connect to peer 8umnf6uD using `WS2P g1.lesfoisonnantes.fr 443: WS2P connection timeout`

2023-04-13T10:00:51+02:00 debug WS2P: init: failed connection

2023-04-13T10:00:51+02:00 warn WS2P request timeout

2023-04-13T10:00:51+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

2023-04-13T10:00:51+02:00 info Block resolution: 1 potential blocks after current#596249...

2023-04-13T10:00:51+02:00 error
2023-04-13T10:00:51+02:00 info Fork resolution: 48 potential block(s) found...

2023-04-13T10:00:51+02:00 info Fork resolution: block #596250-00000037 is known as incorrect. Skipping.

2023-04-13T10:00:51+02:00 debug Suite -> 596299-00000029 missing block#596250-00000037

2023-04-13T10:00:51+02:00 info Blocks were not applied.

2023-04-13T10:00:51+02:00 info Blocks were not applied.

2023-04-13T10:00:51+02:00 info Blocks were not applied.

2023-04-13T10:00:51+02:00 info Blocks were not applied.

2023-04-13T10:00:51+02:00 info Block resolution: 1 potential blocks after current#596249...

2023-04-13T10:00:51+02:00 error
2023-04-13T10:00:52+02:00 info Fork resolution: 48 potential block(s) found...

2023-04-13T10:00:52+02:00 info Fork resolution: block #596250-00000037 is known as incorrect. Skipping.

2023-04-13T10:00:52+02:00 debug Suite -> 596299-00000029 missing block#596250-00000037

2023-04-13T10:00:57+02:00 info [8umnf6uD] ⬇ PEER EK76xRvy 617741-0

2023-04-13T10:00:57+02:00 info [8umnf6uD] ⬇ PEER EK76xRvy 617741-0

2023-04-13T10:00:57+02:00 info [8umnf6uD] ⬇ PEER EK76xRvy 617741-0

2023-04-13T10:00:57+02:00 warn Unknown reference block of peer

2023-04-13T10:00:57+02:00 info [8umnf6uD] ⬇ PEER EK76xRvy 617741-0

2023-04-13T10:00:57+02:00 info [8umnf6uD] ⬇ PEER EK76xRvy 617741-0

2023-04-13T10:00:57+02:00 warn Unknown reference block of peer

2023-04-13T10:00:57+02:00 info [8umnf6uD] ⬇ PEER EK76xRvy 617741-0

2023-04-13T10:00:57+02:00 info [8umnf6uD] ⬇ PEER EK76xRvy 617741-0

2023-04-13T10:00:57+02:00 warn Unknown reference block of peer

2023-04-13T10:00:57+02:00 info [8umnf6uD] ⬇ PEER EK76xRvy 617741-0

2023-04-13T10:00:57+02:00 warn Unknown reference block of peer

2023-04-13T10:00:57+02:00 info [8umnf6uD] ⬇ PEER EK76xRvy 617741-0

2023-04-13T10:00:57+02:00 warn Unknown reference block of peer

2023-04-13T10:01:00+02:00 info [8umnf6uD] ⬇ PEER 3tBWySvy 617741-0

2023-04-13T10:01:00+02:00 info [8umnf6uD] ⬇ PEER 3tBWySvy 617741-0

2023-04-13T10:01:00+02:00 warn Unknown reference block of peer

2023-04-13T10:01:00+02:00 info [8umnf6uD] ⬇ PEER 3tBWySvy 617741-0

2023-04-13T10:01:00+02:00 warn Unknown reference block of peer

2023-04-13T10:01:00+02:00 info [8umnf6uD] ⬇ PEER 3tBWySvy 617741-0

2023-04-13T10:01:00+02:00 warn Unknown reference block of peer

2023-04-13T10:01:00+02:00 info [8umnf6uD] ⬇ PEER 3tBWySvy 617741-0

2023-04-13T10:01:00+02:00 info [8umnf6uD] ⬇ PEER 3tBWySvy 617741-0

2023-04-13T10:01:00+02:00 warn Unknown reference block of peer

2023-04-13T10:01:00+02:00 info [8umnf6uD] ⬇ PEER 3tBWySvy 617741-0

2023-04-13T10:01:00+02:00 warn Unknown reference block of peer

2023-04-13T10:01:00+02:00 info [8umnf6uD] ⬇ PEER 3tBWySvy 617741-0

2023-04-13T10:01:00+02:00 warn Unknown reference block of peer

2023-04-13T10:01:00+02:00 info [8umnf6uD] ⬇ PEER 3tBWySvy 617741-0

2023-04-13T10:01:00+02:00 warn Unknown reference block of peer

2023-04-13T10:01:09+02:00 info SIDE Block #617772-00000008 added to the blockchain in 1 ms

2023-04-13T10:01:09+02:00 info Block resolution: 1 potential blocks after current#596249...

2023-04-13T10:01:09+02:00 error
2023-04-13T10:01:09+02:00 info Fork resolution: 48 potential block(s) found...

2023-04-13T10:01:09+02:00 info Fork resolution: block #596250-00000037 is known as incorrect. Skipping.

2023-04-13T10:01:09+02:00 debug Suite -> 596299-00000029 missing block#596250-00000037

2023-04-13T10:01:20+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:40042!

2023-04-13T10:01:20+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:5cf254c3-35f3-4365-b0cd-85bb7434bf112a6192cd-97ad-48fe-92b0-46fba01d05a2

2023-04-13T10:01:20+02:00 trace WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:8m7MA4TeFDynJxxyP7UyURGaeBNeMZjvVifduaAXED8c:059408b1-fe57-4644-bf42-4524af58fb98fcfc6365-f8ec-4ace-8a79-5a985d8b299c

2023-04-13T10:01:20+02:00 trace WS2P >>> sendACK >>> WS2P:ACK:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:059408b1-fe57-4644-bf42-4524af58fb98fcfc6365-f8ec-4ace-8a79-5a985d8b299c

2023-04-13T10:01:20+02:00 trace WS2P >>> registerACK >>> WS2P:ACK:g1:8m7MA4TeFDynJxxyP7UyURGaeBNeMZjvVifduaAXED8c:5cf254c3-35f3-4365-b0cd-85bb7434bf112a6192cd-97ad-48fe-92b0-46fba01d05a2

2023-04-13T10:01:20+02:00 trace WS2P >>> sendOK >>> WS2P:OK:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:5cf254c3-35f3-4365-b0cd-85bb7434bf112a6192cd-97ad-48fe-92b0-46fba01d05a2

2023-04-13T10:01:20+02:00 trace WS2P >>> registerOK >>> WS2P:OK:g1:8m7MA4TeFDynJxxyP7UyURGaeBNeMZjvVifduaAXED8c:059408b1-fe57-4644-bf42-4524af58fb98fcfc6365-f8ec-4ace-8a79-5a985d8b299c

2023-04-13T10:01:20+02:00 info WS2P: established incoming connection from 8m7MA4Te 127.0.0.1:40042

2023-04-13T10:01:26+02:00 info WS2P 8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ: new incoming connection from 127.0.0.1:55500!

2023-04-13T10:01:26+02:00 trace WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:8umnf6uDtriTj64Me1hEuPDnbBmxjZEJ59TsHK8HS8nZ:8f24d42a-94ad-4fbc-a8f6-e0e02bb039e69ef533e6-b6bb-4881-a5ab-045592414fcf

2023-04-13T10:01:26+02:00 error WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE

2023-04-13T10:01:41+02:00 warn WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout

Désolé mais je ne trouve rien sur le forum pouvant me permettre d’etre autonome sur la résolution de ce non fonctionnement correct
Je peux ouvrir l’acces admin en public au noeud pour celui qui veux regarder si je ne passe pas a côté de quelque chose d’evident pour un habitué.

JProd · 13 April 2023 18:46

salut , visiblement c’est le meme pbm que sur ce post et aparement résolu je vois les nœuds synchros

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

Synchronisation où il y a un message bizarre - #3 by Wilfriedg39

joss.rendall · 14 April 2023 11:08

Merci de ton aide mais pas mieux… j’ai monte la mémoire à 8Go mais je n’ai jamais dépassé 4 Go utilisé pendant la synchro avant qu’elle ne Bug…

vit · 14 April 2023 13:43

Une limite de 4 Go ? Ca sent la limite 32 bits ça.

Une taille en octets ne peut pas dépasser 4 Go si on tente de la stocker dans un entier U32 (32bits non signé = 2^32 = 4294967296). Hope it helps…

Mais je ne vois pas pourquoi tu aurais un système/stockage/ram 32 bits sur un VPS…

joss.rendall · 14 April 2023 14:26

Je dis juste que lorsque je lance la synchro en SSH via putty, j’affiche dans mon navigateur la fenêtre de NetData installé sur mon VPS qui me permet de suivre en direct les ressources du VPS et la RAM consommée ne dépasse jamais 4 Go…

Moul · 14 April 2023 14:33

L’erreur dit que ça n’a pas pu allouer la mémoire nécessaire.
Bien qu’il y en ait suffisamment ou que tu n’as pas observé l’occupation passer au-delà de 4 Go ne dit rien au problème. Il y doit y avoir une raison pour laquelle Node.js n’a pas pu allouer la mémoire nécessaire.

Quelle est l’architecture de ton serveur ? Juste pour être sûr. Que te donne ?

getconf LONG_BIT

joss.rendall · 14 April 2023 16:32

getconf LONG_BIT

reponse : 64

grep -o -w ‘lm’ /proc/cpuinfo | sort -u
reponse : lm

rendall@lesfoisonnantes:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye

avec la derniere version de yunohost, tous paquets à jour

node -v : v14.21.3