MESSAGE_METHOD_UNKNOWN(OpaqueRef:***.get_record)
-
Dear @olivierlambert I updated many times in the last 2 weeks and the problem persist.
The master changes so frequently that it's hard to keep it updated.
Anyway I will try to update now and run again the backup and let you know. -
If you updated before creating this thread, you would have see it working… "It's moving too fast": use XOA if you want an easier solution to stay up to date
-
@olivierlambert XOA it's too expensive..
-
Then don't complain to keep up on
masterbefore reporting a bug. You can't have both -
After updating and restarting xo server I get this error: no opaque ref found
Attaching log file
-
Because your XO isn't connected anymore to the pool when you started the backup.
-
No, that's not the problem. XO can reach the servers without problems, I see the list of VMs
What else could be?
-
Any suggestion??
DELTA Backups are working without any problem, Disaster Recovery backups are giving Error: no opaque ref found
-
Sounds like a bug to me. Does it also occur if you run a backup on a new job instead of an existing one?
-
It happens in both situations. If I run a new backup job, I get that error on most VMs, on other I get "write ECONNRESET" error.
The strange thing is that the schedulet delta backups on the same storage worked without issues.
There seems to be a problem with Disaster Recovery backups.. And it all happened after I updated to the latest master commit and restarting.. -
There are a few things that you could try --
-
Try to locate the problematic commit using
git bisect. See this post for more details. -
Try to replicate the problem using XOA. I'm sure @olivierlambert would extend your trial if needed. Just ask nicely.
. -
Build a new XO VM and retest to see if the problem persists.
FWIW, I ran a DR backup on a single VM the other day and it worked as expected. In my case, the source and destination SR was the same.
-
-
I was getting this same error for full backups, updated to latest version in our lab when doing full backups. I updated to the latest commit db99a and the problem was solved.
-
@lawrencesystems I’m already at the latest commit
Thanks anyway
-
@runfi85
Are you using this https://github.com/ronivay/XenOrchestraInstallerUpdater to do the builds and if so have you pulled the latest as that also has some recent updates for the build. -
@lawrencesystems yes I’m using that bash script and the build is up to date to the latest commit
-
I was getting the same thing, after updating to the latest XO the issue was resolved. I will note my 8.3 beta system did not have this problem. Only our production 8.2 servers in the office.
-
XO is updated and rebooted, but still getting the same error:
-
Hello, I updated XO to the latest commit 7af08 but still getting the same error.
Is this really happening only to me?
-
Seems like, yes. That's why I bet on a build issue on environment issue on your side. Please try to build it following our documentation, from a fresh folder to be sure you are directly on the latest commit (you can check that in the About view)
-
@olivierlambert Done but still not working. Any way to install a trial of xenorchestra to troubleshoot the problem?
