Ark node gets stuck when upgraded from 2.5.28 to 2.6.1

As I run in docker (kuberenetes), my upgrade process is very simple: I just stop the docker container with old @arkecosystem/core@2.5.28 and start new one with @arkecosystem/core@2.6.1 installed The start command is “ark relay:run --suffix=relay --env=production --token=ark --network=mainnet”

It results those logs:

[2020-02-11 21:57:09.195] INFO : Starting P2P Interface
[2020-02-11 21:57:18.777] INFO : Socket worker started, PID: 905
[2020-02-11 21:57:18.779] INFO : Socket worker started, PID: 912
[2020-02-11 21:57:19.081] INFO : Setting up core-magistrate-transactions.
[2020-02-11 21:57:20.085] INFO : Starting Database Manager
[2020-02-11 21:57:20.085] INFO : Establishing Database Connection

And nothing happens. As I see from my DB monitoring - connection indeed inititated, but there is no read/write operations. Also no CPU/RAM usage

[ksemaev]

Did work, TY @adrian69 Other nodes still stuck, but I’ll do some PG dumps to fix it

[adrian69]

@ksemaev that node forked. You need to rollback. Try running that inside the container:

pm2 stop all
ark snapshot:rollback --height=11270000
pm2 start all