XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Backup failures: Undefined errors

    Scheduled Pinned Locked Moved Backup
    9 Posts 3 Posters 351 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Z Offline
      Zululander
      last edited by

      I am getting the following errors:

      For Metadata and Config backup

      {
        "data": {
          "reportWhen": "never"
        },
        "id": "1703240400635",
        "jobId": "50bfaad4-b0bb-4912-94f4-a0231adb504e",
        "jobName": "Weekly - Config & Metadata",
        "message": "backup",
        "scheduleId": "d4aa065c-02a3-4ee6-83b0-e4962921143b",
        "start": 1703240400635,
        "status": "failure",
        "end": 1703240401220,
        "result": {
          "message": "Cannot convert undefined or null to object",
          "name": "TypeError",
          "stack": "TypeError: Cannot convert undefined or null to object\n    at metadataBackup.executor [as _executor] (file:///opt/xo/xo-builds/xen-orchestra-202312210650/packages/xo-server/src/xo-mixins/metadata-backups.mjs:47:7)\n    at Jobs.apply (file:///opt/xo/xo-builds/xen-orchestra-202312210650/packages/xo-server/src/xo-mixins/jobs/index.mjs:294:28)\n    at Jobs._runJob (/opt/xo/xo-builds/xen-orchestra-202312210650/node_modules/golike-defer/src/index.js:85:19)\n    at Jobs.runJobSequence (file:///opt/xo/xo-builds/xen-orchestra-202312210650/packages/xo-server/src/xo-mixins/jobs/index.mjs:334:18)\n    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202312210650/packages/xo-server/src/xo-mixins/api.mjs:445:20)"
        }
      }
      

      And for full backups

      {
        "data": {
          "mode": "full",
          "reportWhen": "never"
        },
        "id": "1703239217011",
        "jobId": "e404831a-9dea-47a6-89d7-87a179017030",
        "jobName": "Weekly Backups",
        "message": "backup",
        "scheduleId": "2b860522-46d9-4499-b300-fd517dd3398e",
        "start": 1703239217011,
        "status": "failure",
        "end": 1703239217019,
        "result": {
          "message": "Cannot read properties of undefined (reading 'healthCheckSr')",
          "name": "TypeError",
          "stack": "TypeError: Cannot read properties of undefined (reading 'healthCheckSr')\n    at executor (file:///opt/xo/xo-builds/xen-orchestra-202312210650/packages/xo-server/src/xo-mixins/backups-ng/index.mjs:201:41)\n    at file:///opt/xo/xo-builds/xen-orchestra-202312210650/packages/xo-server/src/xo-mixins/jobs/index.mjs:265:30\n    at Jobs._runJob (file:///opt/xo/xo-builds/xen-orchestra-202312210650/packages/xo-server/src/xo-mixins/jobs/index.mjs:294:22)\n    at Jobs.runJobSequence (file:///opt/xo/xo-builds/xen-orchestra-202312210650/packages/xo-server/src/xo-mixins/jobs/index.mjs:334:7)\n    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202312210650/packages/xo-server/src/xo-mixins/api.mjs:445:20)"
        }
      }
      

      I have tested my remote storage and that is working.

      Not sure where to from here.

      1 Reply Last reply Reply Quote 0
      • Z Offline
        Zululander
        last edited by

        Changed retention from 5 to 3 and it worked.

        1 Reply Last reply Reply Quote 0
        • olivierlambertO Online
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          Hi @Zululander

          We need more context before assisting you. Like the version of XO you are using and such 🙂

          Z 1 Reply Last reply Reply Quote 0
          • Z Offline
            Zululander @olivierlambert
            last edited by

            @olivierlambert I have just updated it using the XenOrchestraInstallerUpdater script with XCP-Ng 8.2.1

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Online
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              Is your current commit matches with the latest one on master? (should be visible in the about view)

              Z 1 Reply Last reply Reply Quote 0
              • Z Offline
                Zululander @olivierlambert
                last edited by

                @olivierlambert Ah, that might be it, "Xen Orchestra, commit 5cf5d" with a warning "You are not up to date with master. 23 commits behind". Going to google how I update it.

                DanpD 1 Reply Last reply Reply Quote 1
                • DanpD Offline
                  Danp Pro Support Team @Zululander
                  last edited by

                  @Zululander You should be able to simply rerun the same update script you previously used.

                  Z 1 Reply Last reply Reply Quote 1
                  • Z Offline
                    Zululander @Danp
                    last edited by

                    @Danp Yes, I thought that would be the case but not sure how. If I remember correctly, I installed
                    my homelab using https://docs.xcp-ng.org/installation/install-xcp-ng/

                    XCP-ng release 8.2.1 (xenenterprise)
                    NAME="XCP-ng"
                    VERSION="8.2.1"
                    ID="xenenterprise"
                    ID_LIKE="centos rhel fedora"
                    VERSION_ID="8.2.1"
                    PRETTY_NAME="XCP-ng 8.2.1"
                    ANSI_COLOR="0;31"
                    HOME_URL="http://xcp-ng.org/"
                    BUG_REPORT_URL="https://github.com/xcp-ng/xcp"
                    XCP-ng release 8.2.1 (xenenterprise)
                    XCP-ng release 8.2.1 (xenenterprise)

                    https://docs.xcp-ng.org/installation/upgrade/ talks about upgrading but I am just wanting to update to the latest commit. Do I just do an upgrade from 8.2 to 8.2 and that will then do it?

                    1 Reply Last reply Reply Quote 0
                    • DanpD Offline
                      Danp Pro Support Team
                      last edited by

                      It seems like you are confusing xcp-ng (the virtualization server) with XO (the VM for managing xcp-ng). Based on your earlier post, you needed to update XO, not xcp-ng. Therefore, you should be able to rerun your XenOrchestraInstallerUpdater script to update XO to the latest source commits.

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post