What have I done this time? 1.33.0 unable to start

In the process of upgrading to 1.33.0

However, it’s been 12 hours since first restarting the relay and it’s still “starting”.

I read on Issues between relay and BP on 1.33.0 - #16 by jeremyisme that updating BP before relay has finished may cause this issue. So I deleted the db off relay but no luck.

Is it right that there are no peers?
Checking on pool.vet I get errors:

Relay node

Can’t reach relay node

Check manually that the topology for relay node is configured

Relay node is missing in topology.json

Screenshot 2022-01-15 at 23.46.35

update: pool.vet now shows Relay node is in [topology.json] but still unable to reach it
Screenshot 2022-01-16 at 00.18.09

can you have a look at what the journalctl is showing?

Can u share the glive now? How is the node? Syncing?

This is normal, especially when using the hosting company where the relay is. I know other people for whom it took longer.
If you are using a good (but more expensive hosting), the first restart when upgrading to 1.33.0 will take between 2 and 4 hours.
The shortest time I’ve heard about is around 90 minutes, with some very good nvme disks.
I assume by now the service started (if you did not interrupt it in the mean time).

Thanks for the reply guys. Yeh seems it was a waiting game.
The plan is to upgrade once the pool gets at least one block (hopefully will now we’re above 100kADA.
Long term goal is to build a server and run it from our solar panels but need the council to instal the fibre internet that was planned for Q1 2021!!!

Is it correct that my producer has two incoming connections? It’s my relay but on two ports…

Also, any thoughts on why the relay node is missing from topology.json?

Screenshot 2022-01-16 at 10.18.35
Screenshot 2022-01-16 at 10.19.18
Screenshot 2022-01-16 at 10.21.45