Waves Dev Jedi | RIDE for dApps

01 Mar 2025 14:30

0.60%... And it was 25%...

Waves Dev Jedi | RIDE for dApps

01 Mar 2025 14:26

are you sure it started from scratch?

Waves Dev Jedi | RIDE for dApps

01 Mar 2025 14:25

A couple of days ago, synchronization reached 25%, and then these errors continued to appear. Restart did not help, I had to do a down/up, and synchronization started from scratch again. Then everything happened again... This is probably the 5th time I’ve started it...

Waves Dev Jedi | RIDE for dApps

01 Mar 2025 14:20

What error are you talk? I see besu doing sync, have you wait it to finish once?

Waves Dev Jedi | RIDE for dApps

01 Mar 2025 12:35

for besu there is no snapshots

Waves Dev Jedi | RIDE for dApps

01 Mar 2025 01:07

My bad was 1am was sleepy 😊😆

Waves Dev Jedi | RIDE for dApps

28 Feb 2025 18:18

Just try with the export:
https://blockchain.wavesnodes.com/

Waves Dev Jedi | RIDE for dApps

28 Feb 2025 18:06

There are definitely problems with the test network!!! I reinstalled my node from scratch, I'll find it purely according to the official... The node started, the synchronization lasted for two days, almost 25%, and that's it! Errors started again! I restarted it, and the synchronization started from scratch again...

Waves Dev Jedi | RIDE for dApps

27 Feb 2025 13:28

we’ve started rolling out native token bridges to stagenet, and hopefully the feature will make it to the testnet in a week or two.
for the feature to work op-geth client is required, so if your deplyments aren’t running smoothly, it may make sense to wait for the instructions on how to prepare for native token bridges release.

Waves Dev Jedi | RIDE for dApps

27 Feb 2025 13:08

That would be nice! But where to place them? The volume of besu is about 42 Gb... I archived it! I know the size.

Waves Dev Jedi | RIDE for dApps

27 Feb 2025 13:05

Looks like a community snapshots could be taken

Waves Dev Jedi | RIDE for dApps

27 Feb 2025 13:02

Unfortunately, it is true; the synchronization I did from scratch on Testnet took 1 week, maybe even longer.

Waves Dev Jedi | RIDE for dApps

26 Feb 2025 20:57

I don't know if SNAP mode is working properly for scratch synchronization at the moment. But I updated it from like this and the setting of the relevant part is still the same;

command:
 - --sync-mode=SNAP
 - --logging=INFO
 - --host-allowlist=*
 - --rpc-http-enabled
 - --rpc-http-api=ETH,NET,WEB3,TXPOOL,TRACE,ADMIN,MINER
 - --rpc-http-cors-origins=all
 - --rpc-ws-enabled
 - --discovery-enabled=true
 - --engine-rpc-enabled
 - --engine-jwt-secret=/etc/secrets/jwtsecret
 #- --engine-jwt-disabled=true
 - --engine-host-allowlist=*
 #- --engine-host-allowlist=localhost,127.0.0.1
 - --node-private-key-file=/etc/secrets/p2p-key
 - --data-path=/var/lib/besu
 - --genesis-file=/etc/besu/genesis.json
 - --static-nodes-file=/etc/besu/static-nodes.json
 - --data-storage-format=BONSAI

Waves Dev Jedi | RIDE for dApps

26 Feb 2025 20:13

As I wrote above, I got an error while synchronizing from scratch with the Testnet default settings, so I tried SNAP and I still continue with that setting without any problem.

However, I did not change the default settings for Mainnet at all. So it might be more logical to try the default settings before using SNAP while deleting everything and installing from scratch.

Waves Dev Jedi | RIDE for dApps

26 Feb 2025 20:04

What exact config do you use? Why you did not follow the official guide?

Waves Dev Jedi | RIDE for dApps

01 Mar 2025 14:27

Have you tried FAST? /channel/waves_ride_dapps_dev/62426

Waves Dev Jedi | RIDE for dApps

01 Mar 2025 14:26

This I know...
But the synchronization cannot end. Errors occur and when you restart it starts all over again... And so on for the fifth time.

Waves Dev Jedi | RIDE for dApps

01 Mar 2025 14:22

testnet besu db size ~44 GiB

Waves Dev Jedi | RIDE for dApps

01 Mar 2025 13:44

This error occurs every 2 minutes! Tell me - is this a problem with my server or is it a besu problem???

Maybe someone can help?

Time passes and this error continues. I'm doing docker compose down/up
And all synchronization starts from scratch...

I'm already starting to give up... 😔😔😔

Waves Dev Jedi | RIDE for dApps

01 Mar 2025 12:30

How can I use this? And what exactly is this? For the fastest synchronization besu...

Waves Dev Jedi | RIDE for dApps

28 Feb 2025 20:17

https://blockchain-testnet.wavesnodes.com/

Waves Dev Jedi | RIDE for dApps

28 Feb 2025 18:11

At this rate, I won't be in sync in a month...

Waves Dev Jedi | RIDE for dApps

28 Feb 2025 16:33

does the testnet grpc 6870/6881 have issues atm?

Waves Dev Jedi | RIDE for dApps

27 Feb 2025 13:10

So we'll have to wait a week...

Waves Dev Jedi | RIDE for dApps

27 Feb 2025 13:07

If I'm not mistaken, @GalkaWavesFunnyNode offered to do this several times, but community didn't seem very enthusiastic about it (maybe for security or other reasons), so she backed out.

Waves Dev Jedi | RIDE for dApps

27 Feb 2025 13:04

The same problem applies to Nodes in the WEST Network, since there is no public data backup in the WEST Network, synchronization can take days or even weeks!

Waves Dev Jedi | RIDE for dApps

27 Feb 2025 12:28

It’s a pity, of course, that you can’t download the besu blockchain in the same way as waves... Synchronization takes a very long time. I think I can finish it in two days...

Waves Dev Jedi | RIDE for dApps

26 Feb 2025 20:51

Are you sure SNAP syncing is actually working? If you started syncing in default mode which is FULL for private networks. Maybe there is a message about that in the besu starting log?

Waves Dev Jedi | RIDE for dApps

26 Feb 2025 20:08

I followed the official instructions 100%! But I only added --sync-mode=SNAP as @subwar recommended. I'll redo everything tomorrow!

Waves Dev Jedi | RIDE for dApps

26 Feb 2025 19:55

As far as I know, Mainnet Unit0 synchronizes faster than Testnet Unit0. Therefore, a fresh installation can be done according to the main guide.

I was getting a similar error with old docker images, but I haven't gotten this error in Mainnet for a long time with the image recommended by the Node team that I posted above.

There may be many reasons for the error, wrong port settings, simple typos that were overlooked, etc.

Maybe you can set the log settings to debug level and search for something there.

But I usually prefer to delete everything and do a fresh installation.

Of course, don't forget to back up your information such as seeds etc.!