MESSAGE_METHOD_UNKNOWN(OpaqueRef:***.get_record)

[olivierlambert]

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

[runfi85]

@olivierlambert XOA it's too expensive..

[olivierlambert]

Then don't complain to keep up on master before reporting a bug. You can't have both

[runfi85]

After updating and restarting xo server I get this error: no opaque ref found

Attaching log file

xa-error-backup.txt

[olivierlambert]

Because your XO isn't connected anymore to the pool when you started the backup.

[runfi85]

No, that's not the problem. XO can reach the servers without problems, I see the list of VMs

What else could be?

[runfi85]

Any suggestion??

DELTA Backups are working without any problem, Disaster Recovery backups are giving Error: no opaque ref found

[Danp]

Sounds like a bug to me. Does it also occur if you run a backup on a new job instead of an existing one?

[runfi85]

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..

[Danp]

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.

[lawrencesystems]

@runfi85

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.

[runfi85]

@lawrencesystems I’m already at the latest commit

Thanks anyway

[lawrencesystems]

@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.

[runfi85]

@lawrencesystems yes I’m using that bash script and the build is up to date to the latest commit

[caponate]

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.

[runfi85]

XO is updated and rebooted, but still getting the same error:

[runfi85]

Hello, I updated XO to the latest commit 7af08 but still getting the same error.

Is this really happening only to me?

[olivierlambert]

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)

[runfi85]

@olivierlambert Done but still not working. Any way to install a trial of xenorchestra to troubleshoot the problem?

[runfi85]

I think I found the issue, it seems that xen cannot connect to the SMB Storagebox used for backup destination. I need to investigate further, thank you