Thanks for the mention. Trying to sync.
PS: Any blockchain tar/zip updated available for 1.9? My last syncs I couldn’t sync without it.
@vjrj there are 2 sources of .tar.gz archives for nodes 1.9.0 listed here.
Read the (last) comment column as you might have to edit the link to replace the date part.
2 Likes
see the page for available backups/versions : Duniter v1 automatic nodes' data backup links
1 Like
Amazing thanks.
Well, now using your tar.gz I’m in the same situation as you, GVA in block 899709.
I see my 1.9.0 node blocked again around 18:00 
(and indeed, the current block value given by GVA was way lower than the one given by the “/blockchain/current” API call).
I unblocked my node again (got up to #900240); but the GVA part remains blocked at #899709).
I suspect it might be linked to the fact I don’t do a shutdown of my server when creating the backup archive ?
I’ll try to apply archive from Pini instead !
Je viens de stopper ces deux noeuds.
1 Like
J’ai appliqué le backup de @Pini pour mon noeud 1.9.0; la partie GVA reste toujours bloquée à #899709 
curl -s https://g1-1.9.0.de.brussels.ovh/blockchain/current | jq -r '.number'
>
900248
curl -sX POST https://g1-1.9.0.de.brussels.ovh/gva \
-d '{"query":"# Write your query or mutation here\n {currentBlock{number}}"}' | jq -r '.data.currentBlock.number'
>
899709
Du coup aucune idée comment “réparer” la partie gva…
Et question subsidiaire; est-ce qu’il vaut mieux que je coupe mon noeud s’il à la partie GVA qui n’est pas correcte 
I had to reset my 1.9.0 node from a backup twice today. And it lags again now. If you use one of my backups avoid the one from tonight.
1 Like
De mémoire, chaque protocole (BMA, WS2P, GVA) avance à son “rythme”, j’avais noté un décalage suivant le protocole utilisé. Pour moi, ton noeud devrait rattraper. Tu devrais checker un peu plus tard et voir si c’est toujours bloqué.
1 Like
Malheureusement, il ne bougeait pas du tout pour la partie gva; en plus de s’être de nouveau bloqué pour l’API “/blockchain/current” (?bma?) au #900248 - et en redémarrant le noeud; il semble reprendre à partir de #899709 à chaque fois - c’est très étrange - la il s’était rebloqué un block moins loin #900247…
Je tente un dernier reset avec le backup du 17/01 de Pini; si ça ne fonctionne pas, je pense que je couperai mon noeud 1.9.0.
@vjrj Ok, I could finally fix my node by using the oldest backup from Pini of the 16/01/2026.
To make sure we don’t lose that backup; I’ll leave it on my server as well:
https://downloads.de.brussels.ovh/duniter-data-1.9.0-2026-01-16.tar.gz
Now my 1.9.0 node is again synchronized; with both bma? and gva at the same block #900264
curl -s https://g1-1.9.0.de.brussels.ovh/blockchain/current | jq -r '.number'
>
900264
curl -sX POST https://g1-1.9.0.de.brussels.ovh/gva -d '{"query":"{currentBlock{number}}"}' | jq -r '.data.currentBlock.number'
>
900264
1 Like
4th try without luck. I’ll try tomorrow. Thanks!
@vjrj My 1.9.0 node is still properly synced this morning for bma? and gva; so you could try with my backup of this night on your next try 
https://downloads.de.brussels.ovh/auto-backup-g1-1.9.0.de.brussels.ovh-2026-01-19_02-00.tgz
Also a reminder; I think you need the adapted (docker) image of Pini for the node to be able to recover in the current degraded state we are in:
image: pinidh/duniter-190:test
1 Like
Yes, this was the missing part. Thanks indeed!, now is working properly.
2 Likes
they are blocked on Restoring your today backup again!
I restarted from my 20250116 backup again
1 Like
@vjrj, @Pini I think it’s hopeless for our three 1.9.0 servers…
Here is the graph from the last 24 hours of the “heartbeat” of my 1.9.0 node.
The green dots/line (ping) represents the diff of current block with the base server (g1.duniter.org).
It takes the biggest difference between the BMAS & GVA current block of the node being tested.
We see there, that even though my 1.9.0 node is still registered as synchronised in Kazou right now, it actually is more than 90 blocks behind for the gva part !
So I also checked this morning the current state for our three 1.9.0 nodes and another one that works well and all our nodes have that same issue
So all this to say I’m not sure if it’s worth trying to keep our 3 nodes alive