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

    Continuous Replication Schedul backup Error: Expected values to be strictly equal: 430 !== 512

    Scheduled Pinned Locked Moved Xen Orchestra
    29 Posts 3 Posters 3.1k Views 1 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.
    • P Offline
      polyaks @olivierlambert
      last edited by olivierlambert

      @olivierlambert said in Continuous Replication Schedul backup Error: Expected values to be strictly equal: 430 !== 512:

      It shows the current steps while it progress, eg while clicking on a "In progress" backup log, you can see the current step (progress, merge etc.) and the steps done (snapshot step for example).

      Sorry for my English.
      The problem is different.
      When the backup process is started, I can’t create new and edit already created "Backup jobs", because information about VM and SR is not displayed.
      But as soon as backup is completed all information becomes available.

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates πŸͺ Co-Founder CEO
        last edited by

        So this is a bug. Please try to reproduce with XOA on latest channel πŸ™‚

        P 1 Reply Last reply Reply Quote 0
        • P Offline
          polyaks @olivierlambert
          last edited by

          @olivierlambert
          Installed a trial version of XOA from the latest channel.
          The problem persists.

          12fa799e-c58b-4261-8928-acead530f923-image.png

          bee2feae-ac19-4188-9356-c8206b584b86-image.png

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates πŸͺ Co-Founder CEO
            last edited by

            There's a problem fetching objects from your hosts. Please open a support tunnel so I can take a look when I can.

            P 1 Reply Last reply Reply Quote 0
            • P Offline
              polyaks @olivierlambert
              last edited by

              @olivierlambert
              Server XOA behind the proxy
              4071907b-6a83-4987-a89c-367fd03706f4-image.png

              1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates πŸͺ Co-Founder CEO
                last edited by

                So please configure your proxy in the update view.

                P 1 Reply Last reply Reply Quote 0
                • P Offline
                  polyaks @olivierlambert
                  last edited by

                  @olivierlambert
                  Proxy settings are already persists on the Updates tab

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO Offline
                    olivierlambert Vates πŸͺ Co-Founder CEO
                    last edited by

                    Please check:

                    1. /etc/resolv.conf to be able to resolv tunnel.xen-orchestra.com
                    2. that your proxy settings are OK and you can ask for updates on your XOA

                    Without that, we won't be able to take a look remotely.

                    P 1 Reply Last reply Reply Quote 0
                    • P Offline
                      polyaks @olivierlambert
                      last edited by

                      @olivierlambert
                      add tunnel.xen-orchestra.com 159.69.135.93 to /etc/resolv.conf and /etc/hosts

                      92da936a-b54f-4367-92cf-12f37f91d4ae-image.png

                      But error exist
                      Warning: Failing to resolve tunnel.xen-orchestra.com, falling back to 212.129.28.35

                      Update - OK
                      2a40e4fe-4e8d-45dd-9c8e-b8f32af4a079-image.png

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO Offline
                        olivierlambert Vates πŸͺ Co-Founder CEO
                        last edited by

                        We changed the DNS record from the old IP to the new one 1 week ago. So please check your internal DNS to be sure they are refreshed correctly.

                        P 1 Reply Last reply Reply Quote 0
                        • P Offline
                          polyaks @olivierlambert
                          last edited by

                          @olivierlambert
                          According to information from proxy admins, the XOA server does not connect to the proxy during the creation of the support tunnel.
                          The netstat command showed that the server is creating a NAT connection.
                          tcp 0 1 10.44.71.176:43312 159.69.135.93:443 SYN_SENT

                          This means that the Support tunnel does not use proxy settings.

                          1 Reply Last reply Reply Quote 0
                          • olivierlambertO Offline
                            olivierlambert Vates πŸͺ Co-Founder CEO
                            last edited by

                            Ping @julien-f

                            P 1 Reply Last reply Reply Quote 0
                            • P Offline
                              polyaks @olivierlambert
                              last edited by

                              @olivierlambert
                              [06:08 15] xoa@xoa:~$ ping tunnel.xen-orchestra.com
                              PING shelter.vates.fr (159.69.135.93) 56(84) bytes of data.

                              1 Reply Last reply Reply Quote 0
                              • julien-fJ Offline
                                julien-f Vates πŸͺ Co-Founder XO Team
                                last edited by

                                @polyaks Hi, at this moment, xoa support tunnel does not use the proxy configuration defined for the update, you will need to also set the configuration in /etc/xo-server/config.toml.

                                P 1 Reply Last reply Reply Quote 0
                                • P Offline
                                  polyaks @julien-f
                                  last edited by

                                  @julien-f @olivierlambert
                                  The support tunnel has been created.

                                  Do not stop this command before the intervention is over!
                                  Give this id to the support: 41699

                                  1 Reply Last reply Reply Quote 0
                                  • olivierlambertO Offline
                                    olivierlambert Vates πŸͺ Co-Founder CEO
                                    last edited by

                                    Thanks, we'll take a look when we can πŸ™‚

                                    P 1 Reply Last reply Reply Quote 0
                                    • julien-fJ Offline
                                      julien-f Vates πŸͺ Co-Founder XO Team
                                      last edited by

                                      @polyaks FYI, it looks like a corrupted (truncated) file issue.

                                      You can take a look at this post where I explain succinctly how to check XO backup files πŸ™‚

                                      1 Reply Last reply Reply Quote 1
                                      • P Offline
                                        polyaks @olivierlambert
                                        last edited by

                                        @olivierlambert
                                        "Expected values to be strictly equal: 430 !== 512" is not the result of using a GFS2 drive.
                                        On an XOA (non-source) server, the delta backup on the GFS2 drive completed with a successful result
                                        10f8a362-2640-4eaa-99a9-46988b5e7bf3-image.png

                                        Clarification
                                        During the backup process, I can edit and crate Backup tasks, only to display information about VMs and SRs I need to wait about 5 minutes.

                                        1 Reply Last reply Reply Quote 0
                                        • olivierlambertO Offline
                                          olivierlambert Vates πŸͺ Co-Founder CEO
                                          last edited by olivierlambert

                                          Delta will fail as soon you'll make a delta. So only the first delta backup on GFS2 will work. Not any other.

                                          See https://xen-orchestra.com/docs/delta_backups.html#continuous for how it works.

                                          P 1 Reply Last reply Reply Quote 0
                                          • P Offline
                                            polyaks @olivierlambert
                                            last edited by

                                            @olivierlambert
                                            I was able to reproduce the problem on the lastest XOA server.
                                            Give this id to the Support tunnel : 41699

                                            Backup Task settings:
                                            f39ebe1e-09ad-47cf-ae5f-094e11e7dd58-image.png

                                            XOA work correct if vCPU settings are 1socket= 1 core
                                            ac2b5bf6-3ec0-4fd9-9ab8-b1e2e851a252-image.png
                                            fc0c9a10-0ab0-4a1c-92ec-8f64808de85f-image.png

                                            If I change vCPU to 1 socket = 2 cores or 1socket= 4 core
                                            a0ccd48e-f6b8-4769-94cd-a1ebce158ca0-image.png

                                            Received error when starting the same task
                                            898bf25e-5d37-40ff-a91c-229614dd7894-image.png

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