@florent increasing the timeout value was the solution. Thank you.
Best posts made by blueh2o
-
RE: Restore job went off the rails. How to fix it?
Latest posts made by blueh2o
-
RE: Restore job went off the rails. How to fix it?
@florent increasing the timeout value was the solution. Thank you.
-
RE: Restore job went off the rails. How to fix it?
@florent Thank you, I will try this.
-
RE: Restore job went off the rails. How to fix it?
@DustinB XOCE commit 9b6d1, XCP-ng 8.3.0, backup remote is NFS on Synlology.
-
Restore job went off the rails. How to fix it?
I started a restore yesterday, and it said it was going to take some hours so I left it running.. When I came back to XO today, there are no pool tasks listed for importing, there is a API call: backupNg.importVmBackup task that is "started," and under Restore shows as started as well but there is no traffic between the system and the remote. It seems this backup will never complete, and I can't cancel it either. The raw data for the restore shows "transfer" is "pending."
-
RE: Async.VBD.eject always gets stuck
Additional info:
uuid ( RO) : 127a8a7b-e277-27dc-802f-7f779676e18e
name-label ( RO): Async.VBD.eject
name-description ( RO):
subtask_of ( RO): <not in database>
subtasks ( RO):
resident-on ( RO): 74e89397-c334-43f5-8322-5331c31ae368
status ( RO): pending
progress ( RO): 0.000
type ( RO): <none/>
result ( RO):
created ( RO): 20251106T19:44:14Z
finished ( RO): 19700101T00:00:00Z
error_info ( RO):
allowed_operations ( RO):
current_operations ( RO):
other-config (MRW): debug_info:cancel_points_seen: 1 -
RE: Async.VBD.eject always gets stuck
@acebmxer Will try at the next opportunity.
-
RE: Async.VBD.eject always gets stuck
@olivierlambert Yes it is. I currently have one eject task at 0% for 19 hours...
-
Async.VBD.eject always gets stuck
I'm moving some VMs from ESXi to XCP-ng, and it seems that whenever I eject the tools iso, the Async.VBD.eject task never goes away unless I restart the toolstack. How can I get these tasks to complete?
-
RE: CPU radio buttons on usage graph
@DustinB Still there in commit d77d6. The deselected CPU disappears from the graph but reappears when it refreshes.