Cesium Client makes it Appear as though the G1 Blockchain were "Stuck"

Support Cesium
1

(Probably no big deal)

As per the Cesium client (Version 1.7.13) the last block appears as though it were from 08/08/2025 4:21 PM (Paris Time). While the last transaction appears as though it were from 08/08/2025 3:15 PM (Paris Time). Not sure if it’s just on my computer, or just the client. I don’t have any G1s on my account so I cannot test if transactions work, but I thought I’d report it in case it can be of any use for you to know.

EDIT: Ginspecte indicates the curret block is 855331 vs 854763 on the Cesium client, so appears very likely it is only either the Cesium client, or something on my computer.

1 Like
2

Is no one else experiencing / witnessing this?

3

Change de Nœud !

4

g1v1.coinduf.eu
g1.duniter.org
g1.cuates.net

all yield the same result

5

There are forks on the network these days!

6

The Ğ1 network seems to be broken right now. The only UP node I could find is remuniter.cgeek.fr (https://remuniter.cgeek.fr/bma/blockchain/current). With the block 854763.

Probably a big fork.

I’m trying to find another node to sync to, but failed up here.

3 Likes
7

info publique pour les utilisateurs envoyée ce matin sur FML : Etat du réseau V1 (2025.08.12) - Duniter v1 - Forum Monnaie Libre

3 Likes
8

En cours de resynchro depuis remuniter-backend.cgeek.fr, si vous trouvez meilleur nœud je suis preneur (https://wotwizard-node.cgeek.fr/) mais à mon avis tous sont HS car :

  1. Un ou plusieurs forks sont en cours
  2. Les nœuds apparaissent hors ligne du fait du déclenchement du mécanisme anti-DDoS, qui se retourne contre nous en rendant l’API BMA indisponible (bien qu’en réalité les nœuds sont probablement encore connectés ensemble via WS2P, mais de mon côté je suis devenu aveugle vu que j’ai éteint mon nœud g1.cgeek.fr pour le resynchroniser).

Si vous tentez de redémarrer votre nœud, celui-ci a plusieurs possibilités :

  • soit il se trouve bloqué sur un fork (bloc #854763) et se bouclera sur la résolution de fork au démarrage : pas de solution pour le moment, je suis en train de tenter une resynchro pour voir si ça permet de passer outre
  • soit il se trouve sur l’autre fork repéré par @Charmander (bloc #855331) et alors il a une chance de démarrer
  • autres cas dont je n’ai pas conscience pour l’instant
4 Likes
9

L’hypothèse semble se confirmer, j’ai https://wotwizard-node.cgeek.fr qui affiche le bloc #855737 et semble avancer. Donc je pense que la couche WS2P fonctionne, je vais plutôt me synchroniser sur ce nœud.

1 Like
10

Mon noeud est sur le block 855 741 mais il ne trouve que 2 pairs

1 Like
11

3!

:check_mark: Container duniter-v1comunesnet-duniter-1 Started 0.4s
duniter-1 | Starting duniter with:
duniter-1 | /usr/bin/duniter --max-old-space-size 8192 direct_webstart
duniter-1 | 2025-08-12T06:44:22+00:00 - info: mode=Start
duniter-1 | 2025-08-12T06:44:22+00:00 - info: open duniter databases…
duniter-1 | 2025-08-12T06:44:22+00:00 - info: Databases successfully opened.
duniter-1 | 2025-08-12T06:44:22+00:00 - info: Current block: #855720-0000001CD72FD67CC381C71E34EF8C07E10E0FFD50C8D07CB7B4289342BAE836
duniter-1 | 2025-08-12T06:44:22+00:00 - info: start dbs threadpool…
duniter-1 | 2025-08-12T06:44:22+00:00 - info: Duniter sever started.
duniter-1 | 2025-08-12T06:44:22+00:00 - info: start duniter modules…
duniter-1 | 2025-08-12T06:44:26+00:00 - info: generated self endpoints: [“GVA S duniter-v1.comunes.net 443 gva”]
duniter-1 | 2025-08-12T06:44:26+00:00 - info: GvaServer::start: conf=GvaConf { enabled: true, ip4: 0.0.0.0, ip6: None, path: “gva”, playground: true, port: 30901, remote_host: Some(“duniter-v1.comunes.net”), remote_port: Some(443), remote_path: Some(“gva”), remote_tls: Some(false), whitelist: [127.0.0.1, ::1] }
duniter-1 | 2025-08-12T06:44:26+00:00 - info: GVA server listen on http://0.0.0.0:30901/gva
duniter-1 | 2025-08-12T06:44:26+00:00 - info: Server::run; addr=0.0.0.0:30901
duniter-1 | 2025-08-12T06:44:26+00:00 - info: listening on http://0.0.0.0:30901
duniter-1 | 2025-08-12T06:44:26+00:00 - info: Block resolution: 0 potential blocks after current#855720…
duniter-1 | 2025-08-12T06:44:26+00:00 - info: Web administration accessible at following address: http://0.0.0.0:9220
duniter-1 | 2025-08-12T06:44:26+00:00 - info: WS2P server 6DrGg8cftpkgffv4Y4Lse9HSjgc8coEQor3yvMPHAnVH listening on 0.0.0.0:20901
duniter-1 | 2025-08-12T06:44:26+00:00 - info: BMA server listening on http://0.0.0.0:10901
duniter-1 | 2025-08-12T06:44:26+00:00 - info: WS2P: init: bundle of peers 1/5
duniter-1 | 2025-08-12T06:44:26+00:00 - info: Sibling endpoints:
duniter-1 | 2025-08-12T06:44:26+00:00 - info: BMA access: duniter-v1.comunes.net:443
duniter-1 | 2025-08-12T06:44:26+00:00 - info: WS2P access: duniter-v1.comunes.net :443 ws2p
duniter-1 | 2025-08-12T06:44:26+00:00 - info: [6DrGg8cf] :down_arrow: PEER 6DrGg8cf 855697-0
duniter-1 | 2025-08-12T06:44:26+00:00 - info: [6DrGg8cf] :check_mark: PEER 6DrGg8cf 855697-0
duniter-1 | 2025-08-12T06:44:26+00:00 - warn: Too high difficulty: waiting for other members to write next block
duniter-1 | 2025-08-12T06:44:27+00:00 - info: Next peering signal in 359 min
duniter-1 | 2025-08-12T06:44:41+00:00 - info: WS2P: Could not connect to peer NoMUXKrL using WS2P 90.15.74.36 20900: WS2P connection timeout
duniter-1 | 2025-08-12T06:44:41+00:00 - info: WS2P: Could not connect to peer 573v8LGa using WS2P duniter-v1-g1.axiom-team.fr 443: WS2P connection timeout
duniter-1 | 2025-08-12T06:44:41+00:00 - info: WS2P: Could not connect to peer ndYUMsDJ using WS2P fania.g1server.net 443: WS2P connection timeout
duniter-1 | 2025-08-12T06:44:41+00:00 - info: WS2P: Could not connect to peer A5DdXxCK using WS2P g1.cuates.net 443: WS2P connection timeout
duniter-1 | 2025-08-12T06:44:41+00:00 - info: WS2P: init: bundle of peers 2/5
duniter-1 | 2025-08-12T06:47:29+00:00 - info: WS2P: Could not connect to peer 7bmwxTBx using WS2P gibraleon.g1server.net 443: WS2P connection timeout
duniter-1 | 2025-08-12T06:47:29+00:00 - info: WS2P: Could not connect to peer 33wEa1Sg using WS2P g1.madeirawonders.com 443: WS2P connection timeout
duniter-1 | 2025-08-12T06:47:29+00:00 - info: WS2P: Could not connect to peer GfKERHnJ using WS2P g1.moul.re 10900: WS2P connection timeout
duniter-1 | 2025-08-12T06:47:29+00:00 - info: WS2P: Could not connect to peer GGdW5Rxd using WS2P ws2p.nodo5.red-g1.ovh 443: WS2P connection timeout
duniter-1 | 2025-08-12T06:47:29+00:00 - info: WS2P: Could not connect to peer 4yojwbYt using WS2P monnaie-libre.ortie.org 443: WS2P connection timeout
duniter-1 | 2025-08-12T06:47:29+00:00 - info: WS2P: init: bundle of peers 3/5

1 Like
12

Mon noeud est sur le bloc 855754 mais il redemarre des qu’il se rend compte que l’API BMA est indisponible (il redémarre en boucle en ce moment).
@cgeek si la couche WS2P fonctionne correctement je devrais virer le redémarrage automatique le temps que d’autres noeuds se synchronisent ?
Ton noeud wotwizard-node.cgeek.fr semble s’être correctement synchronisé et générer à nouveau des blocs (il est sur le 855755). Tu sais pourquoi ta couche BMA répond correctement sur ce noeud, tu as désactivé la protection DOS ?

EDIT : j’ai récupéré ton dernier bloc

2025-08-12T09:23:11+00:00 - info: Current block: #855755-0000002064F6A178B17373F9ABBE549CE3406AD95A7C88D1255C1324A0A13799
2025-08-12T09:23:13+00:00 - info: Block resolution: 0 potential blocks after current#855755…

1 Like
13

C’est le nœud WotWizard, d’habitude je cache sa couche BMA donc la protection DoS n’est pas sollicitée.

De mon côté j’ai synchronisé mon nœud g1.cgeek.fr mais au démarrage il finit par freezer, je cherche pourquoi. Je vois des logs de calcul de bloc mais je ne sais pas si c’est à cause de ça.

1 Like
14

Mon nœud g1.cgeek.fr vient de se remettre, je vais creuser sur ce qui l’a bloqué. En tout cas voici ce qu’il voit désormais :

image
image1742×1300 315 KB

edit : on voit également bien que le consensus en a pris un coup, la génération de blocs prend du retard et la difficulté diminue :

image
image1770×1290 180 KB

3 Likes
15

Ci-dessous un extrait des logs de mon nœud suite à une resynchronisation.

On peut voir que tout s’est débloqué à 2025-08-12T09:30:28+00:00 (GMT, donc 11h30 chez nous) une fois l’initialisation réseau terminée WS2P: init: bundle of peers 4/4.

@aya c’est bizarre que ton nœud “plante”. A la limite qu’il freeze comme le mien serait moins surprenant, en réalité il ne freeze pas vraiment mais attend longuement des connexions WS2P qui finissent en timeout.

Logs 
2025-08-12T09:05:35+00:00 - e[32minfoe[39m: Block resolution: 0 potential blocks after current#855738...
2025-08-12T09:05:35+00:00 - e[32minfoe[39m: Web administration accessible at following address: http://0.0.0.0:9220
2025-08-12T09:05:35+00:00 - e[32minfoe[39m: WS2P server 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ listening on 0.0.0.0:20900
2025-08-12T09:05:35+00:00 - e[32minfoe[39m: BMA server listening on http://0.0.0.0:35556
2025-08-12T09:05:35+00:00 - e[32minfoe[39m: WS2P: init: bundle of peers 1/4
2025-08-12T09:05:35+00:00 - e[32minfoe[39m: Sibling endpoints:
2025-08-12T09:05:35+00:00 - e[32minfoe[39m: BMA access: g1.cgeek.fr:35556
2025-08-12T09:05:35+00:00 - e[32minfoe[39m: WS2P access: 82.65.206.220:20900
2025-08-12T09:05:35+00:00 - e[32minfoe[39m: [2ny7YAdm] ⬇ PEER 2ny7YAdm 855708-0
2025-08-12T09:05:35+00:00 - e[32minfoe[39m: [2ny7YAdm] ✔ PEER 2ny7YAdm 855708-0
2025-08-12T09:05:35+00:00 - e[32minfoe[39m: Next peering signal in 359 min
2025-08-12T09:05:37+00:00 - e[32minfoe[39m: Generating proof-of-work with 6 leading zeros followed by [0-6]... (CPU usage set to 10%) for block#855739 2ny7YA
2025-08-12T09:05:37+00:00 - e[32minfoe[39m: Creating worker c#0#w#1
2025-08-12T09:05:37+00:00 - e[32minfoe[39m: Creating worker c#0#w#2
2025-08-12T09:05:37+00:00 - e[32minfoe[39m: Creating worker c#0#w#3
2025-08-12T09:05:37+00:00 - e[32minfoe[39m: Creating worker c#0#w#4
2025-08-12T09:05:37+00:00 - e[32minfoe[39m: [online] worker c#0#w#0
2025-08-12T09:05:37+00:00 - e[32minfoe[39m: [online] worker c#0#w#1
2025-08-12T09:05:37+00:00 - e[32minfoe[39m: [online] worker c#0#w#2
2025-08-12T09:05:37+00:00 - e[32minfoe[39m: [online] worker c#0#w#3
2025-08-12T09:05:50+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer C3oqFogS using `WS2P g1.duniter.org 443: WS2P connection timeout`
2025-08-12T09:05:50+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer 573v8LGa using `WS2P duniter-v1-g1.axiom-team.fr 443: WS2P connection timeout`
2025-08-12T09:05:50+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer ndYUMsDJ using `WS2P fania.g1server.net 443: WS2P connection timeout`
2025-08-12T09:05:50+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer A5DdXxCK using `WS2P g1.cuates.net 443: WS2P connection timeout`
2025-08-12T09:05:50+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer 7bmwxTBx using `WS2P gibraleon.g1server.net 443: WS2P connection timeout`
2025-08-12T09:05:50+00:00 - e[32minfoe[39m: WS2P: init: bundle of peers 2/4
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer 33wEa1Sg using `WS2P g1.madeirawonders.com 443: WS2P connection timeout`
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer FpAi3xR2 using `WS2P duniter.ganut.fr 443: WS2P connection timeout`
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer DomAF8Qy using `WS2P duniter971.dynssl.com 443: WS2P connection timeout`
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer 4bibsssD using `WS2P g1.asycn.io 443: WS2P connection timeout`
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer 6DrGg8cf using `WS2P duniter-v1.comunes.net 443: WS2P connection timeout`
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: WS2P: init: bundle of peers 3/4
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: Matched 6 zeros 000000D028425363F136E02D007B42F705938A3D6B42BD313F4929C795211876 with Nonce = 10400000022132 for block#855739 by 2ny7YA
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: Matched 5 zeros 000004D5C1E77A21EF0C77ADC095EC267E9F3DD22FD4DA744CD8BC1C1DC924D4 with Nonce = 10400000235335 for block#855739 by 2ny7YA
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: Matched 5 zeros 00000B3C025FD91170B19F41D6558C3F55CC6C54C02EE2A95F8B27198BE1BA20 with Nonce = 10400000284891 for block#855739 by 2ny7YA
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:56288!
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:57286!
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:57924!
2025-08-12T09:09:00+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:63944!
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: Block resolution: 0 potential blocks after current#855738...
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: Web administration accessible at following address: http://0.0.0.0:9220
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: WS2P server 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ listening on 0.0.0.0:20900
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: BMA server listening on http://0.0.0.0:35556
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: WS2P: init: bundle of peers 1/4
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: Sibling endpoints:
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: BMA access: g1.cgeek.fr:35556
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: WS2P access: 82.65.206.220:20900
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: [2ny7YAdm] ⬇ PEER 2ny7YAdm 855709-0
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:60724!
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: [2ny7YAdm] ✔ PEER 2ny7YAdm 855709-0
2025-08-12T09:23:24+00:00 - e[32minfoe[39m: Next peering signal in 359 min
2025-08-12T09:23:27+00:00 - e[32minfoe[39m: Generating proof-of-work with 6 leading zeros followed by [0-6]... (CPU usage set to 10%) for block#855739 2ny7YA
2025-08-12T09:23:27+00:00 - e[32minfoe[39m: Creating worker c#0#w#1
2025-08-12T09:23:27+00:00 - e[32minfoe[39m: Creating worker c#0#w#2
2025-08-12T09:23:27+00:00 - e[32minfoe[39m: Creating worker c#0#w#3
2025-08-12T09:23:27+00:00 - e[32minfoe[39m: Creating worker c#0#w#4
2025-08-12T09:23:27+00:00 - e[32minfoe[39m: [online] worker c#0#w#0
2025-08-12T09:23:27+00:00 - e[32minfoe[39m: [online] worker c#0#w#1
2025-08-12T09:23:27+00:00 - e[32minfoe[39m: [online] worker c#0#w#2
2025-08-12T09:23:27+00:00 - e[32minfoe[39m: [online] worker c#0#w#3
2025-08-12T09:23:33+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:55890!
2025-08-12T09:23:33+00:00 - e[32minfoe[39m: WS2P: established incoming connection from HJ7U5CeY 192.168.65.3:55890
2025-08-12T09:23:39+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer C3oqFogS using `WS2P g1.duniter.org 443: WS2P connection timeout`
2025-08-12T09:23:39+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer 573v8LGa using `WS2P duniter-v1-g1.axiom-team.fr 443: WS2P connection timeout`
2025-08-12T09:23:39+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer ndYUMsDJ using `WS2P fania.g1server.net 443: WS2P connection timeout`
2025-08-12T09:23:39+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer A5DdXxCK using `WS2P g1.cuates.net 443: WS2P connection timeout`
2025-08-12T09:23:39+00:00 - e[32minfoe[39m: WS2P: init: bundle of peers 2/4
2025-08-12T09:23:39+00:00 - e[33mwarne[39m: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2025-08-12T09:23:42+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:63858!
2025-08-12T09:23:42+00:00 - e[32minfoe[39m: WS2P: established incoming connection from fEPfZt2G 192.168.65.3:63858
2025-08-12T09:23:50+00:00 - e[32minfoe[39m: Matched 6 zeros 000000D028425363F136E02D007B42F705938A3D6B42BD313F4929C795211876 with Nonce = 10400000022132 for block#855739 by 2ny7YA
2025-08-12T09:23:54+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer 7bmwxTBx using `WS2P gibraleon.g1server.net 443: WS2P connection timeout`
2025-08-12T09:23:54+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer 33wEa1Sg using `WS2P g1.madeirawonders.com 443: WS2P connection timeout`
2025-08-12T09:23:54+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer FpAi3xR2 using `WS2P duniter.ganut.fr 443: WS2P connection timeout`
2025-08-12T09:23:54+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer DomAF8Qy using `WS2P duniter971.dynssl.com 443: WS2P connection timeout`
2025-08-12T09:23:54+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer 4bibsssD using `WS2P g1.asycn.io 443: WS2P connection timeout`
2025-08-12T09:23:54+00:00 - e[32minfoe[39m: WS2P: init: bundle of peers 3/4
2025-08-12T09:24:09+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer 6DrGg8cf using `WS2P duniter-v1.comunes.net 443: WS2P connection timeout`
2025-08-12T09:24:09+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer A79nvGns using `WS2P g1.nuaje.fr 443: WS2P connection timeout`
2025-08-12T09:24:09+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer EDX2JKzH using `WS2P g1.guenoel.fr 443: WS2P connection timeout`
2025-08-12T09:24:09+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer FBfxjqPH using `WS2P 90.22.71.45 20900: WS2P connection timeout`
2025-08-12T09:24:09+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer 55oM6F9Z using `WS2P g1v1.coinduf.eu 443: WS2P connection timeout`
2025-08-12T09:24:09+00:00 - e[32minfoe[39m: WS2P: init: bundle of peers 4/4
2025-08-12T09:24:10+00:00 - e[31merrore[39m: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2025-08-12T09:27:19+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer GGdW5Rxd using `WS2P ws2p.nodo5.red-g1.ovh 443: WS2P connection timeout`
2025-08-12T09:27:19+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer fEPfZt2G using `WS2P 83.58.231.30 20902: WS2P connection timeout`
2025-08-12T09:27:19+00:00 - e[32minfoe[39m: WS2P: Could not connect to peer GfKERHnJ using `WS2P g1.moul.re 10900: WS2P connection timeout`
2025-08-12T09:27:19+00:00 - e[32minfoe[39m: Matched 5 zeros 000004D5C1E77A21EF0C77ADC095EC267E9F3DD22FD4DA744CD8BC1C1DC924D4 with Nonce = 10400000235335 for block#855739 by 2ny7YA
2025-08-12T09:27:19+00:00 - e[32minfoe[39m: Matched 5 zeros 00000B3C025FD91170B19F41D6558C3F55CC6C54C02EE2A95F8B27198BE1BA20 with Nonce = 10400000284891 for block#855739 by 2ny7YA
2025-08-12T09:27:19+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:55642!
2025-08-12T09:27:19+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:58394!
2025-08-12T09:27:19+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:56646!
2025-08-12T09:27:19+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:55298!
2025-08-12T09:30:28+00:00 - e[33mwarne[39m: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2025-08-12T09:30:28+00:00 - e[33mwarne[39m: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2025-08-12T09:30:28+00:00 - e[33mwarne[39m: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2025-08-12T09:30:28+00:00 - e[33mwarne[39m: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: Matched 5 zeros 00000AD26F226721B52C054758ECB69F5858BE54B76131E7ECFBC16B1D42D42F with Nonce = 10100001004974 for block#855739 by 2ny7YA
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: Matched 5 zeros 00000170C821DF29E71DBCF547F6321B2C5D10CD44D1DA1789762BE5903122C4 with Nonce = 10100001432158 for block#855739 by 2ny7YA
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: Matched 5 zeros 000009BC3C5952279F193C3D7B8CF5D52A3C8C6B1D01BA856885DF5C3FE2AC7A with Nonce = 10100001532703 for block#855739 by 2ny7YA
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: Matched 5 zeros 0000028A937316B994D1859E529D8D93CFBF33AB975A8BDDB47937C4684F0E8C with Nonce = 10200001029698 for block#855739 by 2ny7YA
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: Matched 5 zeros 00000906600164AE93EC774888DA0CD3611FCD841CF0F2DB65494BB7114E41E4 with Nonce = 10200001240191 for block#855739 by 2ny7YA
2025-08-12T09:30:28+00:00 - e[31merrore[39m:  Error: not opened
    at WebSocket.send (/duniter/duniter/node_modules/ws/lib/WebSocket.js:219:16)
    at WebSocketServer.connection (/duniter/duniter/app/modules/bma/lib/bma.js:134:24)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
2025-08-12T09:30:28+00:00 - e[31merrore[39m:  Error: not opened
    at WebSocket.send (/duniter/duniter/node_modules/ws/lib/WebSocket.js:219:16)
    at WebSocketServer.connection (/duniter/duniter/app/modules/bma/lib/bma.js:134:24)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:59158!
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:59992!
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:59242!
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:59156!
2025-08-12T09:30:28+00:00 - e[31merrore[39m:  Error: not opened
    at WebSocket.send (/duniter/duniter/node_modules/ws/lib/WebSocket.js:219:16)
    at WebSocketServer.connection (/duniter/duniter/app/modules/bma/lib/bma.js:134:24)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
2025-08-12T09:30:28+00:00 - e[31merrore[39m:  Error: not opened
    at WebSocket.send (/duniter/duniter/node_modules/ws/lib/WebSocket.js:219:16)
    at WebSocketServer.connection (/duniter/duniter/app/modules/bma/lib/bma.js:134:24)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
2025-08-12T09:30:28+00:00 - e[31merrore[39m:  Error: not opened
    at WebSocket.send (/duniter/duniter/node_modules/ws/lib/WebSocket.js:219:16)
    at WebSocketServer.connection (/duniter/duniter/app/modules/bma/lib/bma.js:134:24)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
2025-08-12T09:30:28+00:00 - e[33mwarne[39m:  httpCode=400, ucode=1015, message=Document already under treatment
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855739-0000000B added to the blockchain in 12 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855740-00000042 added to the blockchain in 4 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855741-00000008 added to the blockchain in 4 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855742-00000021 added to the blockchain in 8 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855743-00000018 added to the blockchain in 1 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855744-00000018 added to the blockchain in 1 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855745-0000004F added to the blockchain in 3 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855746-0000002A added to the blockchain in 1 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855747-00000035 added to the blockchain in 1 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855748-0000003F added to the blockchain in 1 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855749-0000002C added to the blockchain in 0 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855750-00000009 added to the blockchain in 0 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855751-00000003 added to the blockchain in 3 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855752-00000029 added to the blockchain in 1 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855753-00000000 added to the blockchain in 1 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855754-00000023 added to the blockchain in 1 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: SIDE Block #855755-00000020 added to the blockchain in 1 ms
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: Blocks were not applied.
2025-08-12T09:30:28+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855738...
2025-08-12T09:30:29+00:00 - e[32minfoe[39m: Block #855739 added to the blockchain in 493 ms
2025-08-12T09:30:29+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855739...
2025-08-12T09:30:29+00:00 - e[32minfoe[39m: Block #855740 added to the blockchain in 168 ms
2025-08-12T09:30:29+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855740...
2025-08-12T09:30:29+00:00 - e[32minfoe[39m: Block #855741 added to the blockchain in 125 ms
2025-08-12T09:30:29+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855741...
2025-08-12T09:30:29+00:00 - e[32minfoe[39m: Block #855742 added to the blockchain in 119 ms
2025-08-12T09:30:29+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855742...
2025-08-12T09:30:29+00:00 - e[32minfoe[39m: Block #855743 added to the blockchain in 137 ms
2025-08-12T09:30:29+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855743...
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: [done] worker c#0#w#0
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: [done] worker c#0#w#3
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: [done] worker c#0#w#2
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: [done] worker c#0#w#1
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: No engine found the proof. It was probably cancelled.
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: GIVEN proof-of-work for block#855739 with 6 leading zeros followed by [0-6]! stop PoW for 2ny7YA
2025-08-12T09:30:30+00:00 - e[33mwarne[39m: The proof-of-work generation was canceled: Proof-of-work computation canceled because block received
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block #855744 added to the blockchain in 129 ms
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855744...
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block #855745 added to the blockchain in 125 ms
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855745...
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block #855746 added to the blockchain in 139 ms
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855746...
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block #855747 added to the blockchain in 123 ms
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855747...
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block #855748 added to the blockchain in 145 ms
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855748...
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block #855749 added to the blockchain in 144 ms
2025-08-12T09:30:30+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855749...
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block #855750 added to the blockchain in 119 ms
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855750...
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block #855751 added to the blockchain in 126 ms
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855751...
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block #855752 added to the blockchain in 132 ms
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855752...
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block #855753 added to the blockchain in 183 ms
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855753...
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block #855754 added to the blockchain in 160 ms
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855754...
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block #855755 added to the blockchain in 137 ms
2025-08-12T09:30:31+00:00 - e[32minfoe[39m: Block resolution: 0 potential blocks after current#855755...
2025-08-12T09:30:31+00:00 - e[33mwarne[39m: Proof-of-work self-submission: Cannot read properties of null (reading 'version')
2025-08-12T09:30:37+00:00 - e[32minfoe[39m: Generating proof-of-work with 6 leading zeros followed by [0-8]... (CPU usage set to 10%) for block#855756 2ny7YA
2025-08-12T09:30:37+00:00 - e[32minfoe[39m: Block resolution: 0 potential blocks after current#855755...
2025-08-12T09:30:43+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:58966!
2025-08-12T09:30:43+00:00 - e[32minfoe[39m: WS2P: established incoming connection from CRBxCJrT 192.168.65.3:58966
2025-08-12T09:30:43+00:00 - e[33mwarne[39m: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2025-08-12T09:30:43+00:00 - e[33mwarne[39m: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2025-08-12T09:30:43+00:00 - e[33mwarne[39m: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2025-08-12T09:30:43+00:00 - e[33mwarne[39m: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2025-08-12T09:30:57+00:00 - e[32minfoe[39m: Matched 5 zeros 00000109C5A31C70A1C425E95F8E55C2EE198AC80A2C3DE6F1CF187704E0E9FC with Nonce = 10300000015771 for block#855756 by 2ny7YA
2025-08-12T09:31:06+00:00 - e[32minfoe[39m: Matched 5 zeros 00000EC24FF6CA3FC0279C522297EB93ABFA50E6597C5B4043C22E9A9345F9DC with Nonce = 10300000028940 for block#855756 by 2ny7YA
2025-08-12T09:31:26+00:00 - e[32minfoe[39m: Matched 5 zeros 000001207C98074C89C245D84482249A36B848A9E27DBFC5A8F3D5C650460DFA with Nonce = 10100000074610 for block#855756 by 2ny7YA
2025-08-12T09:31:33+00:00 - e[32minfoe[39m: Matched 5 zeros 00000337658C83B069A0B8B571B6CE392636486A4B3D3C9766092E1CAD00B767 with Nonce = 10100000094506 for block#855756 by 2ny7YA
2025-08-12T09:31:38+00:00 - e[32minfoe[39m: SIDE Block #855756-00000001 added to the blockchain in 1 ms
2025-08-12T09:31:38+00:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#855755...
2025-08-12T09:31:38+00:00 - e[32minfoe[39m: Block #855756 added to the blockchain in 168 ms
2025-08-12T09:31:38+00:00 - e[32minfoe[39m: [done] worker c#0#w#2
2025-08-12T09:31:38+00:00 - e[32minfoe[39m: Block resolution: 0 potential blocks after current#855756...
2025-08-12T09:31:38+00:00 - e[32minfoe[39m: [done] worker c#0#w#0
2025-08-12T09:31:38+00:00 - e[32minfoe[39m: [done] worker c#0#w#3
2025-08-12T09:31:38+00:00 - e[32minfoe[39m: [done] worker c#0#w#1
2025-08-12T09:31:38+00:00 - e[32minfoe[39m: No engine found the proof. It was probably cancelled.
2025-08-12T09:31:38+00:00 - e[32minfoe[39m: GIVEN proof-of-work for block#855756 with 6 leading zeros followed by [0-8]! stop PoW for 2ny7YA
2025-08-12T09:31:38+00:00 - e[33mwarne[39m: The proof-of-work generation was canceled: Proof-of-work computation canceled because block received
2025-08-12T09:31:39+00:00 - e[32minfoe[39m: Generating proof-of-work with 6 leading zeros followed by [0-8]... (CPU usage set to 10%) for block#855757 2ny7YA
2025-08-12T09:32:28+00:00 - e[32minfoe[39m: WS2P 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ: new incoming connection from 192.168.65.3:57226!
2025-08-12T09:32:28+00:00 - e[32minfoe[39m: WS2P: established incoming connection from E1cSiXeP 192.168.65.3:57226
2025-08-12T09:32:50+00:00 - e[32minfoe[39m: Matched 5 zeros 0000055E40852422D15B59407A3A15FE9877DC9B52ACDC20DA09CC6E8F4E2720 with Nonce = 10400000167594 for block#855757 by 2ny7YA
2025-08-12T09:32:58+00:00 - e[32minfoe[39m: Matched 5 zeros 0000073A1C0E45682355103F359133AFFD6259616A279217FCCCF398CAECA60D with Nonce = 10400000204863 for block#855757 by 2ny7YA
2025-08-12T09:33:18+00:00 - e[32minfoe[39m: Matched 5 zeros 000004CEB401F48DC144B48E1CF5F5A18AC3CFE871DCF39972FC14E827E35376 with Nonce = 10100000274020 for block#855757 by 2ny7YA
1 Like
16

Il ne plante pas, il freeze et je le redémarre automatiquement s’il freeze trop longtemps.
J’ai un healhcheck dans mon docker :

code=$(echo -e ‘GET / HTTP/1.0\n’ |nc -w 1 duniter 10901 | awk ‘NR == 1 {print $2}’) && [ "$code" = "200" ] && echo "OK" || exit 1

Par contre je viens de voir avec ton screenshot que ma couche WS2P n’est pas bien configurée, je n’ai que des connexions outcoming.

Capture d’écran 2025-08-12 à 12.09.00
Capture d’écran 2025-08-12 à 12.09.002090×1316 388 KB

En fouillant le forum je suis tombé sur une option --ws2p-noupnp à activer, je vais voir si ca résoud mon pb.

2 Likes
17

Peut-être le retirer le temps que la situation se stabilise ?

En tout cas je ne sais pas si les forgerons interviennent mais le réseau reprend progressivement forme :

image
image1674×818 113 KB

Le nœud g1.duniter.org devrait terminer sa synchro d’ici 14h30 je pense.

Aussi concernant le rattrapage du retard temporel, c’est fini :

image
image512×440 12.1 KB

2 Likes
18

C’est fait.

1 Like
19

Un grand MERCI à vous de maintenir ce réseau malgré sa vétusté ! :heart_eyes:
:hugs:

6 Likes
20

On dirait que j’atteins une limite d’utilisation mémoire désormais…

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

<--- Last few GCs --->

[20:0x56343fc89a20]   255260 ms: Scavenge 4068.1 (4164.0) -> 4067.7 (4164.5) MB, 15.8 / 0.0 ms  (average mu = 0.134, current mu = 0.055) allocation failure
[20:0x56343fc89a20]   258565 ms: Mark-sweep 4068.3 (4164.5) -> 4067.9 (4164.0) MB, 3302.6 / 0.0 ms  (average mu = 0.076, current mu = 0.019) allocation failure scavenge might not succeed
[20:0x56343fc89a20]   258588 ms: Scavenge 4068.6 (4164.0) -> 4068.3 (4164.5) MB, 19.8 / 0.0 ms  (average mu = 0.076, current mu = 0.019) allocation failure


<--- JS stacktrace --->

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

Security context: 0x2b424050f951 <JSObject>
    0: builtin exit frame: stringify(this=0x2b4240504069 <Object map = 0x22e98ef842a9>,0x2b8d3e3026f1 <undefined>,0x2b8d3e3026f1 <undefined>,737745,0x2b4240504069 <Object map = 0x22e98ef842a9>)

    1: arguments adaptor frame: 1->3
    2: /* anonymous */(aka /* anonymous */) [0x2bd667706361] [/duniter/app/lib/dal/sqliteDAL/AbstractSQLite.js:~183] [pc=0x6dc579d692a](this=0x2b8d3e3026f1 <undefined...