Db mismatch version?

Node Operators troubleshooting
1

Hello,
I just restarted a docker container and my node started restarting…
It shows database mismatch or something like that, but before stopping it, it was working just fine?

Any ideas?

image
image1829×801 51.1 KB

Actually I just checked and I have another node that is doing the same thing… with the same message in logs

Is it possible maybe there was an update ongoing to v110 and when it got stopped something got corrupted? or something?

Actually no, these 2 just were updated few h ago and were 110.2 version…

Is it possible that they were v 110.2 and when it tries to get the newest docker image is still as 109? and its causing issues? cause I see on github v109 is tagged as the “latest” the 110.2 is tagged as “pre-release” and cause of that its causing issues?

OR

after restart it just downgraded to 109 for some reason, and now it can’t boot up…

#EDIT

Looks like it got fixed? I didn’t do anything, maybe you fixed it?

2

I feel like I should mark your own post as the solution.

1 Like
3

hehe, well, I didn’t do anything so it must’ve been a remote issue. Also I noticed that those nodes are now 110.3 version, previously they were 110.2, I guess there was some miniupdate and now they’re running smoothly.
You can close the topic

4

There were no errors related to a version mismatch, but seems the remote issue. Because the final error was “context canceled”, this is usually a timeout.