itservices

itservices

@RobWhalley
That worked for me as well.

I created a new XenOrchestra VM with commit 3c543.

Enabling and disabling NBD on the backup job did the trick.

Thank you and everyone else for your efforts and digging into the matter.

Regards
Marc

itservices

I am giving a short "report", when there is new version out and I have tested it.

Nice weekend @y'all

Regards,
Marc

itservices

Hi @McHenry .

You should obfuscate the IP address in your first screenshot. Also check your profile and private chat

Hope everyone had a joyful Christmas and I wish everyone the best for 2026.

Regards,
Marc

itservices

Just to give an update.

I still am having the issue with current commit 090ce.

Regards,
Marc

itservices

Evening @pierrebrunet

My bad.

I am now on commit b440f and the issue persist.

I have written you a message with the link to the file.

Regards,
Marc

itservices

Hi @pierrebrunet

With commit c74a8 the problem is still present but the transfer was completed again.

Unfortunately my installation does not recognize the "xen-bugtool" command. And both log files are not present.

Is this something that needs enabling after install of XCP-NG?

Unfortunately and unnoticed my syslog-server did not receive any messages from XCP-NG in the last 30 days.

Other inputs work

**Edit:

I have deleted and re-added the syslog-server with port and now logs are being send to Graylog.**

Thanks for your assistance y'all.

Regards,
Marc

itservices

With commit caa17 the transfer did not happen again and fails the with the known message.

Regards,
Marc

itservices

Quick Update:

Was looking good with commit cf26d.

After the transfer completed the VDI of that particular VM was still in use, according to XO.

So still failure on the job.

Regards,
Marc

itservices

Hi @pierrebrunet.

I have deleted the "parentless" VDIs and snapshots.

So the "Unhealthy VDI" page is empty for me.

So everytime I retry with the VM in question it is creating a new (full) backup-chain.

Regards,
Marc

itservices

Problem still present in commit 04deb.

Here is the log from the XO6 interface:

"XapiError: VDI_IN_USE(OpaqueRef:ce1e2c1b-9b52-d813-88fc-18513a51306f, destroy)\n    
at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/_XapiError.mjs:16:12)\n    
at default (file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/_getTaskResult.mjs:13:29)\n    
at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/index.mjs:1078:24)\n    
at file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/index.mjs:1112:14\n   
at Array.forEach (<anonymous>)\n    
at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/index.mjs:1102:12)\n    
at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202606131310/packages/xen-api/index.mjs:1275:14)\n   
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)"

Thanks for your assistance ! ! !

Regards,
Marc

itservices

I am giving a short "report", when there is new version out and I have tested it.

Nice weekend @y'all

Regards,
Marc

itservices

Problem still persists with commit e9b66.

Thanks for the support!

Regards,
Marc

itservices

Commit 1ba82 did change something. It transferred the VDI but then fails with the VDI_IN_USE on that particular machine.

Regards,
Marc

itservices

@itservices