Revert this vm to this snapshot error
-
Hello,
I searched for the error but couldn't find it anywhere here.
When I made a snapshot and want to revert it I get an error message in xen orchestra no such object undefined.
I have already reconnected the server once but that didn't help.
What I also see at helth is that there are also a number of Orphaned VMs snapshots.
This scares me a little bit because it probably means that I have a lot of snapshots that are not usable.
But for now it is important to get the snapshots working again because I use them a lot and the backups use them too.Recognizable for someone and maybe someone knows a solution?
Thanks in advance
Regards,
Jan -
@ronivay Problem seems to have been solved by an update. Thanks for the tip.
-
XOA or XO from sources? Is it up to date?
-
xo-server 5.70.0
xo-web 5.74.0 -
So the answer is no, that is like couple years old. I assume it’s from sources installation then.
Start off by upgrading it to latest version. Instructed also here: https://xen-orchestra.com/docs/community.html
-
@ronivay ok going to have a go at that soon. Thank you
-
@ronivay Problem seems to have been solved by an update. Thanks for the tip.
-
This post is deleted! -
O olivierlambert marked this topic as a question on
-
O olivierlambert has marked this topic as solved on
-
Turns out that unfortunately it doesn't quite work yet. Updated the xoa but the version still say xo-server 5.70.0 and xo-web 5.74.0. As far as I understand it, this is the community version where the backup also works. But when I take a snapshot of a vm I immediately get an Orphaned VMs snapshot line at health. Also rebooted the host once just to be sure.
-
@JanP so you actually didn't update anything, probably just re-ran the installation on top of old codebase. See from sources installation instructions in: https://xen-orchestra.com/docs/installation.html#from-the-sources. Take note that it's perfectly possible that you also need to upgrade your nodejs version to latest LTS.
That'd be the first thing to solve as your installation is very old. It's therefore pointless to debug any issues until you get that XO to latest version as issue you're seeing could've very well be fixed long time ago.
-
@ronivay I understand that there is no point in troubleshooting error because apparently I am using an old config. Node is version v16.17.0. Maybe it is better to create a total new vm with latest version debian. And then install a clean version of xo community edition there. Is it then possible to import in that new installation of xoce the config of the current version?
Thanks for your patience. -
Okay, nodejs version is up to date then, so XO update will probably succeed as well without much of a hickup. Sure it’s safer if you can create a installation from scratch. XO gui has config export/import feature which you can use to migrate to new installation.
-
@ronivay Ok. In between jobs I did a new VM install of debian 11 and on it the XO community version.
Version numbers now:
xo-server 5.100.1
xo-web 5.101.1
I seem to have everything working again. Thanks for the help and tip. Now it seems really solved.
If I come across anything else, which I don't think I will, I will report back.
Greetings and thanks,
Jan
