XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. mguimond
    3. Posts
    M
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 13
    • Groups 0

    Posts

    Recent Best Controversial
    • Mirror incremental backup timeout option not working

      95d78a5c-fbd4-41fa-b4c5-a310c955d130-image.png

      Hello, I'm running a mirror incremental backup and my timeout option is set to 20 hours but even if the backup run longer it never timeout.

      It is me that doesn't understand that option correctly or I'm doing something wrong.

      Thank You.

      posted in Backup
      M
      mguimond
    • RE: Backblaze as Remote error Unsupported header 'x-amz-checksum-mode' received for this API call.

      @florent Sorry for the delay. I was able to make it work with the change you posted. Thank You.

      posted in Xen Orchestra
      M
      mguimond
    • RE: Backblaze as Remote error Unsupported header 'x-amz-checksum-mode' received for this API call.

      @DustinB That is correct.

      posted in Xen Orchestra
      M
      mguimond
    • RE: Backblaze as Remote error Unsupported header 'x-amz-checksum-mode' received for this API call.

      @DustinB when i disable it I can't connect it.

      I use the from source version
      9d3de8d8-44f4-4883-8e94-3db9f0a6fa09-image.png

      This one work correctly. this is another customer with a older version.
      Xen Orchestra, commit fa974
      Master, commit b3d66
      You are not up to date with master. 221 commits behind

      posted in Xen Orchestra
      M
      mguimond
    • RE: Backblaze as Remote error Unsupported header 'x-amz-checksum-mode' received for this API call.

      @DustinB Yes the bucket exist. I'm able to connect and create folder.

      posted in Xen Orchestra
      M
      mguimond
    • Backblaze as Remote error Unsupported header 'x-amz-checksum-mode' received for this API call.

      When im trying to connect to my backblaze to configure a remote in xen orchestra I'm getting the following message. I'm able to connect with my credentiel with cyberduck.

      {
        "name": "InvalidArgument",
        "$fault": "client",
        "$metadata": {
          "httpStatusCode": 400,
          "requestId": "4c022d6f8b1e258a",
          "extendedRequestId": "aNHQx6DCwZa1j6jhRM8s3OjQNYk0zvDkM",
          "attempts": 1,
          "totalRetryDelay": 0
        },
        "Code": "InvalidArgument",
        "message": "Unsupported header 'x-amz-checksum-mode' received for this API call."
      }
      

      Can anynome help me solved this ?

      Thank You.

      posted in Xen Orchestra
      M
      mguimond
    • RE: Mirror Incremental Bkp - Error Maximum call stack size exceeded

      @olivierlambert

      Do you know what would cause this issue with a specific vm backup ?

      {
        "data": {
          "mode": "delta",
          "reportWhen": "failure"
        },
        "id": "1714518000004",
        "jobId": "3c8de440-0a66-4a95-a201-968d1993bd8b",
        "jobName": "Main - Delta - BRO-NAS-001 - VM1SQLSRV2012_PROD",
        "message": "backup",
        "scheduleId": "41094424-a841-4a75-bb74-edd0c5d72423",
        "start": 1714518000004,
        "status": "failure",
        "infos": [
          {
            "data": {
              "vms": [
                "a23bacfb-543d-0ed7-cf90-902288f59ed6"
              ]
            },
            "message": "vms"
          }
        ],
        "tasks": [
          {
            "data": {
              "type": "VM",
              "id": "a23bacfb-543d-0ed7-cf90-902288f59ed6",
              "name_label": "VM1SQLSRV2012_PROD"
            },
            "id": "1714518001609",
            "message": "backup VM",
            "start": 1714518001609,
            "status": "failure",
            "tasks": [
              {
                "id": "1714518001617",
                "message": "clean-vm",
                "start": 1714518001617,
                "status": "failure",
                "tasks": [
                  {
                    "id": "1714518005435",
                    "message": "merge",
                    "start": 1714518005435,
                    "status": "failure",
                    "end": 1714518010534,
                    "result": {
                      "errno": -5,
                      "code": "Z_BUF_ERROR",
                      "message": "unexpected end of file",
                      "name": "Error",
                      "stack": "Error: unexpected end of file\n    at BrotliDecoder.zlibOnError [as onerror] (node:zlib:189:17)\n    at BrotliDecoder.callbackTrampoline (node:internal/async_hooks:128:17)"
                    }
                  }
                ],
                "end": 1714518010534,
                "result": {
                  "errno": -5,
                  "code": "Z_BUF_ERROR",
                  "message": "unexpected end of file",
                  "name": "Error",
                  "stack": "Error: unexpected end of file\n    at BrotliDecoder.zlibOnError [as onerror] (node:zlib:189:17)\n    at BrotliDecoder.callbackTrampoline (node:internal/async_hooks:128:17)"
                }
              },
              {
                "id": "1714518010549",
                "message": "snapshot",
                "start": 1714518010549,
                "status": "success",
                "end": 1714518014388,
                "result": "bfce73a6-ea5b-d498-f3d8-d139b9fe29d5"
              },
              {
                "data": {
                  "id": "b99d8af6-1fc0-4c49-bbe8-d7c718754070",
                  "isFull": true,
                  "type": "remote"
                },
                "id": "1714518014392",
                "message": "export",
                "start": 1714518014392,
                "status": "success",
                "tasks": [
                  {
                    "id": "1714518015575",
                    "message": "transfer",
                    "start": 1714518015575,
                    "status": "success",
                    "end": 1714530612896,
                    "result": {
                      "size": 1668042162176
                    }
                  },
                  {
                    "id": "1714530613148",
                    "message": "clean-vm",
                    "start": 1714530613148,
                    "status": "success",
                    "end": 1714530617953,
                    "result": {
                      "merge": true
                    }
                  }
                ],
                "end": 1714530618039
              }
            ],
            "end": 1714530618039
          }
        ],
        "end": 1714530618040
      }
      
      posted in Backup
      M
      mguimond
    • RE: Mirror Incremental Bkp - Error Maximum call stack size exceeded

      @olivierlambert any news on this ? Thank You.

      posted in Backup
      M
      mguimond
    • RE: Mirror Incremental Bkp - Error Maximum call stack size exceeded

      @olivierlambert Node v18.20.2

      posted in Backup
      M
      mguimond
    • RE: Mirror Incremental Bkp - Error Maximum call stack size exceeded

      @olivierlambert I did the update and I'm getting the same error.

      Herer are the log 2024-04-11T11_47_11.366Z - backup NG.txt

      Sense my mirror incremental backup take a while to do the copy because of internet speed. I had to do update to another commit this morning. I will retest de backup job but still getting the error on the latest commit from last week.

      a53def8c-1827-494e-afbd-88b94f1b7a35-image.png

      posted in Backup
      M
      mguimond
    • RE: Mirror Incremental Bkp - Error Maximum call stack size exceeded

      @olivierlambert Perfect, I will work on this and come back to you.

      posted in Backup
      M
      mguimond
    • RE: Mirror Incremental Bkp - Error Maximum call stack size exceeded

      Xen Orchestra commit ec166

      XCP-NG 8.2.1 (only one host)

      Let me know what specific information you need if I'm missing some.

      posted in Backup
      M
      mguimond
    • Mirror Incremental Bkp - Error Maximum call stack size exceeded

      bkp_log.txt
      Here are the log.

      My mirror incremental bkp always get stuck with one specific vm.

         "result": {
                  "message": "Maximum call stack size exceeded",
                  "name": "RangeError",
                  "stack": "RangeError: Maximum call stack size exceeded\n    at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:418:7)\n    at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n    at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n    at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n    at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n    at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n    at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n    at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n    at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n    at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)"
      =============
      posted in Backup
      M
      mguimond