Restoring from backup error: self-signed certificate
-
@KS Did you try running "xe task-list" to identify the process and then "xe task-cancel force=true uuid=(UUID-of-process)"?
-
@StormMaster thank you. This workaround did exactly what i needed.
-
Thank you @StormMaster
-
A abudef referenced this topic on
-
Ditto the fix from @StormMaster worked for me - many thanks.
-
The command "xe task-cancel force-true ..." with the uuid of the pending tasks did not do anything for me. After trying it on the 3 tasks I had, issuing a "xe task-list" still show me the pending tasks. It it only by rebooting the host that the pending tasks disappear.
-
Going back to an older version of XO source also did the trick for me.
I was in the process of pushing in production a couple VM that were previously in test and that I had backed up a couple of days ago. I was very surprised not to be able to do anything with these VMs stuck on my SR used for VM backup -
@utmoab Strange, but I've seen some tasks "stuck" that could not be cancelled for some reason or aanother. A reboot is a drastic measure, but unfortunate;y sometimes the only recourse.
-
I'm on commit 1b515 and the error still exists.
Pending tasks can be cancelled with "restart toolstack" on host.
-
The BRANCH="0ccfd4b" revert worked for me, backups are working again in the lab.
-
@StormMaster said in Restoring from backup error: self-signed certificate:
BRANCH="0ccfd4b"
This worked for me also, thank you.But after this change, I have tried to run update few times but it seems my commits are falling behind and do not update to the latest.
Am I missing something?
-
@Bub said in Restoring from backup error: self-signed certificate:
Am I missing something?
No, you're "stuck" on commit 0ccfd4b until you revert the change in the config file. It doesn't make sense to do that now, because then you will encounter the issues with backups / restores again. Once a fix has been pushed to the Github repo, then you can switch back to the master branch.
-
@Danp Got you, thanks for the clarification!
-
@Danp Is it safe to say this is being worked on? I don't want to assume anything.
-
@dsiminiuk I would assume so, but I don't know the specifics.
-
M Mathieu referenced this topic on
-
M manilx referenced this topic on
-
@StormMaster
I dont see a PR or even an issue posted on the github. I can add one to the board for ronivay unless someones working on it. -
@michmoor0725 Sure!
I don't think that it is a ronivay issue as it appears to be occurring with any self-signed certificate. Regardless of what was used to compile it.
That said, if some people check there instead of here, it mays good sense to have something posted there as well.
-
U uwood referenced this topic on
-
According to a closed issue from Ronivay the problem looks to be resolved.
https://github.com/ronivay/XenOrchestraInstallerUpdater/issues/227
I've just updated to latest from Branch="Master" and successfully performed a health check.
closed Backup jobs - Health check fails #227
-
D Danp has marked this topic as solved on
-
Thank you for the update Andy.
