[Solved] This node's version is behind, please upgrade


#1

Got this little nugget while lxd is starting. How to resolve?
t=2019-02-08T09:23:48-0600 lvl=info msg=“LXD 3.9 is starting in normal mode” path=/var/snap/lxd/common/lxd
t=2019-02-08T09:23:50-0600 lvl=info msg=“Initializing global database”
t=2019-02-08T09:23:50-0600 lvl=eror msg=“Failed to start the daemon: failed to open cluster database: failed to ensure schema: this node’s version is behind, please upgrade”
t=2019-02-08T09:23:50-0600 lvl=info msg=“Starting shutdown sequence”
t=2019-02-08T09:23:50-0600 lvl=info msg=“Stopping REST API handler:”


#2

One of my other servers:
t=2019-02-07T19:30:00-0600 lvl=info msg=“LXD 3.10 is starting in normal mode” path=/var/snap/lxd/common/lxd
t=2019-02-07T19:30:00-0600 lvl=info msg=“Kernel uid/gid map:”
t=2019-02-07T19:30:00-0600 lvl=info msg=" - u 0 0 4294967295"
t=2019-02-07T19:30:00-0600 lvl=info msg=" - g 0 0 4294967295"
t=2019-02-07T19:30:00-0600 lvl=info msg=“Configured LXD uid/gid map:”
t=2019-02-07T19:30:00-0600 lvl=info msg=" - u 0 1000000 1000000000"
t=2019-02-07T19:30:00-0600 lvl=info msg=" - g 0 1000000 1000000000"
t=2019-02-07T19:30:00-0600 lvl=warn msg=“CGroup memory swap accounting is disabled, swap limits will be ignored.”
t=2019-02-07T19:30:00-0600 lvl=info msg=“Kernel features:”
t=2019-02-07T19:30:00-0600 lvl=info msg=" - netnsid-based network retrieval: no"
t=2019-02-07T19:30:00-0600 lvl=info msg=" - uevent injection: no"
t=2019-02-07T19:30:00-0600 lvl=info msg=" - unprivileged file capabilities: yes"
t=2019-02-07T19:30:00-0600 lvl=info msg=“Initializing local database”
t=2019-02-07T19:30:00-0600 lvl=info msg=“Starting /dev/lxd handler:”
t=2019-02-07T19:30:00-0600 lvl=info msg=" - binding devlxd socket" socket=/var/snap/lxd/common/lxd/devlxd/sock
t=2019-02-07T19:30:00-0600 lvl=info msg=“REST API daemon:”
t=2019-02-07T19:30:00-0600 lvl=info msg=" - binding Unix socket" inherited=true socket=/var/snap/lxd/common/lxd/unix.socket
t=2019-02-07T19:30:00-0600 lvl=info msg=" - binding TCP socket" socket=snip1:8443
t=2019-02-07T19:30:00-0600 lvl=info msg=“Initializing global database”
t=2019-02-07T19:30:00-0600 lvl=info msg=“Wait for other cluster nodes to upgrade their versions”
t=2019-02-08T08:51:34-0600 lvl=warn msg=“Raft: Heartbeat timeout from “snip2:8443” reached, starting election”
t=2019-02-08T08:51:39-0600 lvl=warn msg=“Raft: Election timeout reached, restarting election”
t=2019-02-08T08:51:43-0600 lvl=warn msg=“Raft: Election timeout reached, restarting election”
t=2019-02-08T08:51:48-0600 lvl=warn msg=“Raft: Election timeout reached, restarting election”


#3

obviously my running server is a newer version of lxd. I see that now, odd that the others didn’t update as well though.


#4

I guess I’m testing the candidate branch =)


(Stéphane Graber) #5

LXD clusters detect version mismatch at runtime and self-trigger a refresh, this does require all node to be on the same channel though, I wonder if you may have had one node on the candidate channel and the rest on the stable channel, which would explain why the self-refresh didn’t work in your case.

You can check that with snap info lxd on all nodes, making sure that the current channel is the same on all of them. We obviously don’t recommend having production systems on the candidate channel, but you won’t be able to switch back to stable until we release 3.10 to stable early next week (as downgrades aren’t supported).


#6

Yeah, one was. All good, just a slight heart attack early in the morning. I thought I had switched them all back. Maybe on this next go around.