@Razor_648 While I was writing my previous message, I have been reminded that there are also issues with LVHDoISCSI SR and CBT, you should disable CBT on your backup job and on all VDI on the SR. It might help with the issue.
@Danp said in Advanced VM settings Logs:
Hi Dustin,
Yes... these types of actions are recorded in the Audit log (Settings > Audit) if you have access to this feature and have enabled it.
Dan
Perfect, thanks!
@olivierlambert Understood, however, I'm failing to see what part of my posting was irrelevant to the topic at hand. I was merely sharing what I'd experienced as well and providing context.
I thought this was the kind of feedback expected of community members, who want to see this project flourish?
@StephenAOINS
This endpoint is not currently present in our REST API swagger, but we do plan to add it to the list of endpoints.
We are currently finalizing the migration of existing endpoints, the next step will be adding new ones.
We will keep you informed when it is available. Feel free to come back to us if you want to learn more and follow our blog posts.
have a good day
Just a quick FYI, XOA means "Xen Orchestra virtual Appliance" and it's only available via https://xen-orchestra.com or auto deploy. That's the only one with pro support
Okay so it's indeed a certificate issue on your side. Double check your certs. Sometimes, you need to have a cert file with the intermediate authority.
@jmccoy555 I updated both the XO deployments to current code just now. Both were the same BTW before.
one still asks for the SR on every migration. One does not.
[info] Updating xen-orchestra from '4bed8eb86' to '175be4482'
I would REALLY like to figure this out. Annoying.
Thanks
Tim
@olivierlambert Ok cool, iSCSI is on its own Network on a Direct connection with Multipathing. In the past i have had problems with VMs going in Read Only Mode.
Thanks for your reply.
That's the issue. Why they don't have it is the problem/mystery.
Try to check if new replicated VMs got it. If not, I would check if you are correctly up to date.
@joearnon The browser javascript logs may give you useful information about what issue happened during the import as seen from XO's side.
However the disappearing SR issue makes me think you should look at XCP-ng logs, in particular /var/log/SMLog for storage-related logs and /var/log/daemon.log.
@jsawyer77 Did you follow the documentation when building XO? If not, then what process did you use?
Also, check to see if libvhdi-utils is installed and which version.
@olivierlambert You inadvertently solved this one, too, n parallel with @tony .
So, basically, as suspected, a template is nothing more than populating stuff that's in the basic and advanced webforms on Orchestra, anyway.
@julien-f said in Warnings showing in system logs following each backup job:
We'll see how many reports we get regarding this
One more from me. But it was actually your tech support that discovered them in conjunction with a ticket we have open.
@olivierlambert said in Backup failure: HTTP request has been canceled:
It's a problem when XO tries to get address from your srv02.xxx.com.
It just makes no sense that DNS would be an issue on this network. I guess if XO momentarilly looses connection during DNS lookup it could cause this problem. I've noticed sometimes that the webui of XOA sometimes can show red ? if I start live several live migrations. Maybe unrelated?
