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

    Backup fail Unable to get the true granularity: 60 & worker exited with code null

    Scheduled Pinned Locked Moved Xen Orchestra
    7 Posts 4 Posters 507 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.
    • Spunky_SurveyorS Offline
      Spunky_Surveyor
      last edited by

      I am getting some strange errors with a backup job which i had running for few months with little issue..

      Any ideas what can be the issue.

      Unable to get the true granularity: 60

      {
        "id": "e03a39e3-9546-957d-6e01-4ab40a9cca72"
      }
      {
        "message": "Unable to get the true granularity: 60",
        "name": "FaultyGranularity",
        "stack": "FaultyGranularity: Unable to get the true granularity: 60
          at XapiStats._getAndUpdateStats (file:///usr/local/lib/node_modules/xo-server/src/xapi-stats.mjs:353:13)"
      }
      

      worker exited with code null

      backupNg.runJob
      {
        "id": "f375c1ca-e526-4b0d-b6dd-61eeb6a7498b",
        "schedule": "edc353a4-8237-4a16-aea4-d3906fb07051",
        "vms": [
          "8a698e9e-abe8-168d-eefc-12cfbf62ff1b",
          "c0959e5a-3e1f-b159-297d-b1e9e3389abe",
          "a43e7f1c-a96e-b08e-8695-c0f18b4dba2d",
          "1fa82ed0-1e50-eb6b-97d3-e71725312c54"
        ]
      }
      {
        "message": "worker exited with code null",
        "name": "Error",
        "stack": "Error: worker exited with code null
          at ChildProcess.<anonymous> (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/backups/runBackupWorker.js:15:38)
          at ChildProcess.emit (node:events:513:28)
          at ChildProcess.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:135:17)
          at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
          at Process.callbackTrampoline (node:internal/async_hooks:130:17)"
      }
      
      tjkreidlT 1 Reply Last reply Reply Quote 0
      • DanpD Online
        Danp Pro Support Team
        last edited by

        Not much to go on here. You should include additional details about your environment, XOA or XO from sources, release channel / commit, backup job details, etc.

        Spunky_SurveyorS 1 Reply Last reply Reply Quote 0
        • tjkreidlT Offline
          tjkreidl Ambassador @Spunky_Surveyor
          last edited by

          Spunky_Surveyor said in Backup fail Unable to get the true granularity: 60 & worker exited with code null:

          nable to get the true granularity: 60

          See also: https://xcp-ng.org/forum/topic/2682/should-the-audit-logs-functionality-work-in-the-sources-xoa

          1 Reply Last reply Reply Quote 0
          • Spunky_SurveyorS Offline
            Spunky_Surveyor @Danp
            last edited by

            Danp

            Some more details about my setup/environment
            Version i am running is xoa 7.77.2 and I am on the stable channel

            xo-server 5.107.3

            • node: 18.12.1
            • npm: 8.19.2
            • xen-orchestra-upload-ova: 0.1.4
            • xo-server: 5.107.3
            • xo-server-auth-github-enterprise: 0.2.2
            • xo-server-auth-google-enterprise: 0.2.2
            • xo-server-auth-ldap-enterprise: 0.10.6
            • xo-server-auth-saml-enterprise: 0.10.1
            • xo-server-backup-reports-enterprise: 0.17.2
            • xo-server-netbox-enterprise: 0.3.5
            • xo-server-telemetry: 0.5.0
            • xo-server-transport-email-enterprise: 0.6.0
            • xo-server-transport-icinga2-enterprise: 0.1.1
            • xo-server-transport-nagios-enterprise: 1.0.0
            • xo-server-transport-slack-enterprise: 0.0.0
            • xo-server-transport-xmpp-enterprise: 0.1.1
            • xo-server-usage-report-enterprise: 0.10.2
            • xo-server-xoa: 0.17.1
            • xo-web-enterprise: 5.108.0
            • xoa-cli: 0.33.0
            • xoa-updater: 0.45.1

            Details of the Problematic Backup Job

            • Backing up 13 VMS running in in the same server pool as xoa
            • Daily Backup job set for 11:15 PM
            • Retention = 30
            • backup to an NFS Remote

            I have other delta backup jobs for other vms in this environment which seem to not fail. I do not think the time has much to do with this issue because it seems to fail if i disable all other backup jobs and keep only this one enabled. I started to get these errors but I don't really know what the error means in this context.

            Thanks

            1 Reply Last reply Reply Quote 0
            • Spunky_SurveyorS Offline
              Spunky_Surveyor
              last edited by

              I also just checked the console for xoa and seems to have some memory issues. I am running this xoa with 6 vcpu and 8gb memory.

              19c0637d-995e-4968-a5ec-e92ffcd2a92c-image.png

              DanpD 1 Reply Last reply Reply Quote 0
              • DanpD Online
                Danp Pro Support Team @Spunky_Surveyor
                last edited by

                Spunky_Surveyor Since you are running XOA, I would suggest opening a support ticket.

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

                  +1, that's the way to go 🙂

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