1. Home
  2. Popular
Log in to post
  • pkgwP

    Rolling Pool Update fails with HOST_NOT_ENOUGH_FREE_MEMORY, when it really ought to be fine

    Management
    14
    1
    0 Votes
    14 Posts
    294 Views
    acebmxerA
    So if i set VMs to Best-effort or disabled for HA i get not enough memory. @pkgw Do you have Twinstore configured and/or HA enabled? If no I will continue my issues at the twinstore post. If i set to restart i get this.... host.setMaintenanceMode { "id": "35233210-4e37-4703-9bf6-9e8a9c24df9f", "maintenance": true } { "code": "HA_OPERATION_WOULD_BREAK_FAILOVER_PLAN", "params": [], "call": { "duration": 5, "method": "host.disable", "params": [ "* session id *", "OpaqueRef:d9bd976f-445c-8244-1b56-879f446efc12" ] }, "message": "HA_OPERATION_WOULD_BREAK_FAILOVER_PLAN()", "name": "XapiError", "stack": "XapiError: HA_OPERATION_WOULD_BREAK_FAILOVER_PLAN() at XapiError.wrap (file:///opt/xen-orchestra/packages/xen-api/_XapiError.mjs:16:12) at file:///opt/xen-orchestra/packages/xen-api/transports/json-rpc.mjs:38:21 at runNextTicks (node:internal/process/task_queues:65:5) at processImmediate (node:internal/timers:472:9)" }
  • stormiS

    XCP-ng 8.3 updates announcements and testing

    Pinned News
    611
    1 Votes
    611 Posts
    374k Views
    F
    @andriy.sultanov Thanks I ran that second script on the master and it did indeed find entries: ./snapshot-fixer.py rewrite INFO:root:Check HA... INFO:root:Shutting down xapi... INFO:root:Regenerating database... INFO:root:The VM d6befe36-fea7-04f3-25f1-feada684702b has Ref:9 as its "snapshot_of" value, changing to null. INFO:root:The VM e013d9ed-63b1-9c9f-a228-d48a6047688c has Ref:89 as its "snapshot_of" value, changing to null. INFO:root:The VM 060df7ee-8af4-4c93-8265-bfa3024ccacd has Ref:1 as its "snapshot_of" value, changing to null. INFO:root:The VM da7b6ff6-d722-2120-7cc4-a1e0038a216e has Ref:307 as its "snapshot_of" value, changing to null. INFO:root:The VM 4178b057-efee-427e-bcad-67323419ac7a has Ref:9 as its "snapshot_of" value, changing to null. INFO:root:The VM 8d624e49-ca99-4af6-b17c-38cad0646194 has Ref:1 as its "snapshot_of" value, changing to null. INFO:root:The VM dc72da43-f144-3343-5ee5-a0dbffd209f6 has Ref:251 as its "snapshot_of" value, changing to null. INFO:root:The VM e8c6376b-49e1-422b-551a-35420f70af2a has Ref:8 as its "snapshot_of" value, changing to null. INFO:root:The VM 25eb14ab-e943-0d18-2137-c681e1191346 has Ref:11 as its "snapshot_of" value, changing to null. INFO:root:The VM 6f819166-b008-4a03-a692-fcbd75018be9 has Ref:1 as its "snapshot_of" value, changing to null. INFO:root:The VM 9d1a57e8-3531-4b55-9682-f775215866df has Ref:1 as its "snapshot_of" value, changing to null. INFO:root:The VM 0ac88f7c-d79b-281e-cf1f-a2392ba594ed has Ref:29 as its "snapshot_of" value, changing to null. INFO:root:The VM 1f3541c4-8c81-4959-9cbe-edbec9481220 has Ref:1 as its "snapshot_of" value, changing to null. INFO:root:Writing database to /var/lib/xcp/state.db INFO:root:Starting up xapi... after which it shows clean now: ./snapshot-fixer.py dry-run INFO:root:Regenerating database... However i am still getting the same error when trying to run leaked_vbs: ./leaked_vbds Traceback (most recent call last): File "./leaked_vbds", line 23, in <module> snap = xapi.VM.get_parent(snap) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 317, in __call__ return self.__send(self.__name, args) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 198, in xenapi_request result = _parse_result(getattr(self, methodname)(*full_params)) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 292, in _parse_result raise Failure(result['ErrorDescription']) XenAPI.Failure: ['HANDLE_INVALID', 'VM', 'Ref:29']
  • A

    XenOrchestra not showing VM Disks on Pool (on single Server working) - XCP-ng Center is showing them

    Xen Orchestra
    22
    2
    0 Votes
    22 Posts
    2k Views
    poddingueP
    @kagbasi-wgsdac , thank you so much for the issue creation and the details, that will help for sure!
  • itservicesI

    XO Backup Error: VDI_IN_USE(OpaqueRef:.., destroy)

    Backup
    25
    2
    0 Votes
    25 Posts
    2k Views
    itservicesI
    Hi @simonp. The problem is gone with commit 44e5b!!! Up-to-date XCP-NG host and XenOrchestra VM were restarted after updating XenOrchestra. I just initiated a full backup and all VMs - including my problematic machine - were backed up successfully without error. Awesome! I will wait with closing until the scheduled delta backup is completed successfully, too. Thanks for all your work and assistance Regards, Marc
  • mistercutterM

    Host status in xcp-ng center

    Solved Compute
    6
    1
    0 Votes
    6 Posts
    3k Views
    P
    @jedimarcus solution work, thanks, We had server working 100% since last two weeks but error didn't disappear, after clean logs was ok thank you.
  • H

    Potential bug with Windows VM backup: "Body Timeout Error"

    Backup
    96
    3
    2 Votes
    96 Posts
    15k Views
    G
    @poddingue My three hosts are all EDT, drift on mine is pretty small because I have a local NTP server with GNSS. So it could be a timezone issue and might be worth looking into.