Waves Dev Jedi | RIDE for dApps

11 Jul 2024 20:10

I replaced docker-compose.yml with the old version - it started!

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 20:03

Tried too, it doesn't work

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 20:02

I want to do everything right! As required by the documentation! But it doesn’t work!...

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:59

Also you do not have to follow official docs if you know how things work (for you)

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:57

Then run without -d, you will see them in console

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:55

The node worked. The height of the blocks matched! Only there were problems with besu. I changed everything in the docker-compose file as written in official sources! And now my node won't start at all...

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:51

you doing something wrong

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:47

Ride should be pretty interesting then... It is quite special...

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:45

So where to look for the problem? Why is there no connection?

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:43

--retry-max-time 60
need to change it to 180...

Even if I change it to 50,000 - no way!

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:33

down is needed to stop all node processes
pull is to check for possible updates
up -d is start all services in daemon mode

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:29

There is whole new besu-checker section in the yml

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:27

I didn't find anything about snap...

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:23

then

docker compose down

docker compose pull

docker compose up -d

and start monitoring the logs

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:21

In which file do you need to change what? And how to downgrade?

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 20:10

Don't see full error

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 20:03

Because no one reached 100% sync with SNAP

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 20:01

Node worked well on L1, you need to check L2 is running fine that is via besu

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:58

Personally i do not understand 1 more container to do basic healthcheck: https://github.com/deemru/Waves-L2-Testnet/blob/7ae069ff35bfe2605e23da38512e54e6956985cd/support/docker-compose.yml#L24

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:56

No logs... Node is not starts

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:51

check firewall rules and steps you follow

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:47

Problem is my server or my container?

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:46

I'm not node developer, just poor user like you :)

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:43

There is host (your server) and container (what is inside of docker). Network is controlled by your server, thats it

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:39

What’s network mode host?

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:32

Fine! I will clearly do it as in the official source!
But what if the node stops working altogether?
One minute! Now I’ll change everything!

Then I will need to do:

docker compose down

docker compose pull

docker compose up -d

I understand so?

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:29

You obviously don't follow latest changes in official nodes channel

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:26

Here is my docker-compose.yml

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:22

docker compose yml file, just remove snap

Waves Dev Jedi | RIDE for dApps

11 Jul 2024 19:20

Can you give more details?