XO Team group | XCP-ng and XO forum

pierrebrunet

Hi,
This was fixed in Latest. But if you need to stay on Stable, you can open a ticket to have a patch.

julienXOvates

Just discussed this with @nathanael-h; I would strongly recommend using the load balancer plugin in XO and create some VM-to-host affinity rules, so that your CP VMs are running on different hosts ! So when the RPU comes you would have minimum impact.

julienXOvates

@coolsport00 I think I had this from time to time since a few. I could resolve it by closing my browser completely (not only the XO tab). Can you give a try ? We'll investigate this issue anyway. Thanks

julienXOvates

@coolsport00 can you try if issue is fixed in branch xo6/fix-opening-console-in-new-tab ?

julienXOvates

@coolsport00 sorry for late reply, we can reproduce this issue, so we're going to investigate and get back to you. Thanks for raising this !

pierrebrunet

@johnnezero You can use the docs directly in /rest/v0/docs. You just have to connect and fill in the uuid you need. It will work

mpiton

@jr-m4

Hi, your journalctl output has the answer: vectura: data plane: could not connect: timed out.

With a vCenter as source, the login and the CBT query go through the vCenter on port 443, but the disk itself is read directly from the ESXi host running the VM, on port 902. Your new XO reaches the vCenter fine, it just can't open a connection to that ESXi on 902. The stream has ended without data error is only the side effect of vectura exiting. CBT has nothing to do with it.

The old instance works because it can reach that host (VDDK needed the same port). I'd check firewall/VLAN rules or DNS on the new VM. From the new XO, using the ESXi name as vCenter shows it for that VM:

  getent hosts <esxi-host>
  nc -vz -w 5 <esxi-host> 902

and compare with the old instance.

~Mathieu

pierrebrunet

@johnnezero Hi,
Sorry, it seems it is only in Rest API for now:
You can check it here:

<xoa-url>/rest/v0/docs/#/backup-repositories/ReclaimSpaceBackupRepository

MathieuRA

Issue identified.

@spelon If you're using XO from source, you can try this mra-fix-undici-xen-api branch, otherwise, feel free to open a tunnel so I can fix your XOA.

pierrebrunet

@johnnezero It just came out with the release... now
Just one thing, you may have empty directories even after the reclaimSpace task but they should be empty

XO Team

Posts

Member List