Nodes 1.9 with GVA part desynchronized

Support Duniter-v1
1

Hi there,

For some days I detected that some duniter nodes with GVA (1.9) are not well synchronized, but only the GVA part.

That is, if you query the current block via BMA is bigger than the the block in a GVA query.

Only two GVA enabled nodes are in sync (in the GVA part) with the BMA nodes, https://g1.brussels.ovh (@Nicolas80) and https://g1.copylaradio.com (@Frederic_Renault).

I’ve just installed a v1 duniter node (https://duniter-v1.comunes.net) and I started to see that the GVA part is returning a lower block that the BMA part.

Cesium capture:

image
image808×705 112 KB

G1nkgo capture (a minute later):

image
image1030×580 95.5 KB

GVA Playground query (after writing this, still with the same block):

image
image757×316 16.6 KB

Some GVA enabled nodes were all in an old block for many days (with the BMA in sync):

image
image893×550 76.3 KB

Any idea of what’s is going on?

PS: Thanks to @elmau to trying to have a look on this.

1 Like
2

Thanks for the detailed report :slight_smile:
I have no idea of what’s going on. Duniter 1.9 will be in beta forever and bugs like this or Bug balance DB GVA have very low chance to find a contributor who wants to have a deeper look.

1 Like
3

At the end, and after several sync retries and with patience, we are all in sync again.
image

Thanks and sorry for the v1 noise.