Snapshot failure

[sumansaha]

ECONNRESET when I'm attempting to take a snapshot. Can you please help on that how I can resolve the issue.

vm.snapshot
{
  "id": "f0a8e6be-3XXX-2XXX-b6ee-c86f7830f479"
}
{
  "errno": "ECONNRESET",
  "code": "ECONNRESET",
  "syscall": "write",
  "url": "https://192.168.196.99/jsonrpc",
  "call": {
    "method": "VM.get_record",
    "params": [
      "OpaqueRef:94f9af77-0baf-4799-bd0f-64a123d2d073"
    ]
  },
  "message": "write ECONNRESET",
  "name": "Error",
  "stack": "Error: write ECONNRESET
    at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:94:16)"
}

[sumansaha]

@sumansaha Even after that XOA can't connect with the XCP-NG . But from XOA we can SSH to the XCP-NG. Any help would be great.

[Darkbeldin]

@sumansaha
Hi,

When you go to Settings > Server in XOA do you have a warning on the host connection?

[sumansaha]

@Darkbeldin

Yes its showing the error as attached.But from XOA server we can SSH to XCP-NG without any issue.

[Darkbeldin]

@sumansaha Did you made an XCP update recently? rebooted recently? forgot to reboot after update?

[sumansaha]

@Darkbeldin It was not updated nor rebooted actually.

[olivierlambert]

@sumansaha said in Snapshot failure:

https://192.168.196.99

Check if your host is answering on this URL.

[sumansaha]

@olivierlambert suman@xoa:~$ wget --no-check-certificate https://192.168.196.99
--2023-06-27 17:34:59-- https://192.168.196.99/
Connecting to 192.168.196.99:443... connected.
WARNING: cannot verify 192.168.196.99's certificate, issued by ‘CN=xcp-ng-ohiphxpk’:
Self-signed certificate encountered.
WARNING: certificate common name ‘xcp-ng-ohiphxpk’ doesn't match requested host name ‘192.168.196.99’.
Failed writing HTTP request: Connection reset by peer.
Retrying.

It is not accessible through the URL.

[olivierlambert]

Try with a browser and see what you have

[sumansaha]

@olivierlambert BTW new finding is , we also can't connect the XCP-NG with XCP-NG center. That mean the issue is with the XCP-NG server.

[sumansaha]

@sumansaha As the issue is not only with XO. I can create the discussion again out of XO.

[sumansaha]

@sumansaha
Hello Team,
The issue has resolved after applying xe-toolstack-restart.
Thanks.