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

    Can't restore individual files

    Scheduled Pinned Locked Moved Xen Orchestra
    38 Posts 9 Posters 12.1k Views 3 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.
    • DanpD Offline
      Danp Pro Support Team
      last edited by

      Appears to be a known issue -- https://github.com/vatesfr/xen-orchestra/issues/4377

      john-arvid created this issue in vatesfr/xen-orchestra

      closed File restore not possible from older version #4377

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

        Please check the Logs and provide them

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

          For me, there's nothing in the XO logs. However, I did find an error in the browser console -

          Unhandled promise rejection TypeError: "invalid assignment to const `n'"
    _listFiles restore-file-modal.js:44
    i es6.promise.js:75
    R es6.promise.js:92
    u _microtask.js:18
es6.promise.js:110

          This seems to point to this line calling formatFilesOptions --

          https://github.com/vatesfr/xen-orchestra/blob/6d61e8efffc674cc41bfc62baa6db7581d9ece12/packages/xo-web/src/xo-app/backup-ng/file-restore/restore-file-modal.js#L96

          1 Reply Last reply Reply Quote 0
          • S Offline
            smschumacher
            last edited by

            I am still new to Xen-Orchestra. Which files do you need?

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

              1. Logs in the browser console when you try to access the files
              2. Settings/logs if there's anything
              1 Reply Last reply Reply Quote 0
              • A Offline
                apassler
                last edited by olivierlambert

                @olivierlambert
                console.PNG

                Just before the click on the partition i started journalctl -u xo-server -f -n 50

                root@XOCE:~# journalctl -u xo-server -f -n 50
-- Logs begin at Wed 2019-05-29 07:19:50 CEST. --
Aug 13 09:28:17 XOCE xo-server[31699]:   target:
Aug 13 09:28:17 XOCE xo-server[31699]:    WebSocket {
Aug 13 09:28:17 XOCE xo-server[31699]:      domain: null,
Aug 13 09:28:17 XOCE xo-server[31699]:      _events: {},
Aug 13 09:28:17 XOCE xo-server[31699]:      _eventsCount: 0,
Aug 13 09:28:17 XOCE xo-server[31699]:      _maxListeners: undefined,
Aug 13 09:28:17 XOCE xo-server[31699]:      readyState: 3,
Aug 13 09:28:17 XOCE xo-server[31699]:      protocol: '',
Aug 13 09:28:17 XOCE xo-server[31699]:      _binaryType: 'nodebuffer',
Aug 13 09:28:17 XOCE xo-server[31699]:      _closeFrameReceived: false,
Aug 13 09:28:17 XOCE xo-server[31699]:      _closeFrameSent: false,
Aug 13 09:28:17 XOCE xo-server[31699]:      _closeMessage: '',
Aug 13 09:28:17 XOCE xo-server[31699]:      _closeTimer: null,
Aug 13 09:28:17 XOCE xo-server[31699]:      _closeCode: 1006,
Aug 13 09:28:17 XOCE xo-server[31699]:      _extensions: {},
Aug 13 09:28:17 XOCE xo-server[31699]:      _receiver: null,
Aug 13 09:28:17 XOCE xo-server[31699]:      _sender: null,
Aug 13 09:28:17 XOCE xo-server[31699]:      _socket: null,
Aug 13 09:28:17 XOCE xo-server[31699]:      _isServer: false,
Aug 13 09:28:17 XOCE xo-server[31699]:      _redirects: 0,
Aug 13 09:28:17 XOCE xo-server[31699]:      url: 'ws://localhost:9001',
Aug 13 09:28:17 XOCE xo-server[31699]:      _req: null },
Aug 13 09:28:17 XOCE xo-server[31699]:   type: 'error',
Aug 13 09:28:17 XOCE xo-server[31699]:   message: 'connect ECONNREFUSED 127.0.0.1:9001',
Aug 13 09:28:17 XOCE xo-server[31699]:   error:
Aug 13 09:28:17 XOCE xo-server[31699]:    { Error: connect ECONNREFUSED 127.0.0.1:9001
Aug 13 09:28:17 XOCE xo-server[31699]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
Aug 13 09:28:17 XOCE xo-server[31699]:      errno: 'ECONNREFUSED',
Aug 13 09:28:17 XOCE xo-server[31699]:      code: 'ECONNREFUSED',
Aug 13 09:28:17 XOCE xo-server[31699]:      syscall: 'connect',
Aug 13 09:28:17 XOCE xo-server[31699]:      address: '127.0.0.1',
Aug 13 09:28:17 XOCE xo-server[31699]:      port: 9001,
Aug 13 09:28:17 XOCE xo-server[31699]:      [Symbol(originalCallSite)]: [ CallSite {} ],
Aug 13 09:28:17 XOCE xo-server[31699]:      [Symbol(mutatedCallSite)]: [ CallSite {} ] } }
Aug 13 09:28:17 XOCE xo-server[31699]: xo-server-cloud: next attempt in 973 ms
Aug 13 09:28:18 XOCE xo-server[31699]: xo-server-cloud: next attempt in 1019 ms
Aug 13 09:28:19 XOCE xo-server[31699]: xo-server-cloud: next attempt in 2067 ms
Aug 13 09:28:21 XOCE xo-server[31699]: xo-server-cloud: next attempt in 3095 ms
Aug 13 09:28:24 XOCE xo-server[31699]: xo-server-cloud: next attempt in 5121 ms
Aug 13 09:28:29 XOCE xo-server[31699]: xo-server-cloud: next attempt in 7906 ms
Aug 13 09:28:37 XOCE xo-server[31699]: xo-server-cloud: next attempt in 13166 ms
Aug 13 09:28:50 XOCE xo-server[31699]: xo-server-cloud: next attempt in 20079 ms
Aug 13 09:29:10 XOCE xo-server[31699]: xo-server-cloud: next attempt in 32386 ms
Aug 13 09:29:43 XOCE xo-server[31699]: xo-server-cloud: next attempt in 55447 ms
Aug 13 09:29:59 XOCE ntfs-3g[38727]: Version 2017.3.23 integrated FUSE 28
Aug 13 09:29:59 XOCE ntfs-3g[38727]: Mounted /dev/loop0 (Read-Only, label "", NTFS 3.1)
Aug 13 09:29:59 XOCE ntfs-3g[38727]: Cmdline options: ro,norecovery
Aug 13 09:29:59 XOCE ntfs-3g[38727]: Mount options: ro,norecovery,allow_other,nonempty,relatime,fsname=/dev/loop0,blkdev,blksize=4096
Aug 13 09:29:59 XOCE ntfs-3g[38727]: Ownership and permissions disabled, configuration type 7
Aug 13 09:29:59 XOCE ntfs-3g[38727]: Unmounting /dev/loop0 ()
Aug 13 09:30:19 XOCE ntfs-3g[38750]: Version 2017.3.23 integrated FUSE 28
Aug 13 09:30:19 XOCE ntfs-3g[38750]: Mounted /dev/loop0 (Read-Only, label "", NTFS 3.1)
Aug 13 09:30:19 XOCE ntfs-3g[38750]: Cmdline options: ro,norecovery
Aug 13 09:30:19 XOCE ntfs-3g[38750]: Mount options: ro,norecovery,allow_other,nonempty,relatime,fsname=/dev/loop0,blkdev,blksize=4096
Aug 13 09:30:19 XOCE ntfs-3g[38750]: Ownership and permissions disable
                1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by

                  @julien-f will take a look when he's back (next week). So far I can't reproduce on my end.

                  1 Reply Last reply Reply Quote 0
                  • A Offline
                    apassler
                    last edited by

                    I also tested a fresh installation on Ubuntu 18.04. I will check if i have the same problem on Debian 10.

                    1 Reply Last reply Reply Quote 0
                    • A Offline
                      apassler
                      last edited by

                      now i did a frech installation on a fresh debian 10 and got the same results. i installed xo with the following command:
                      sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh | bash

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

                        Try to check if you have the issue with XOA on stable and/or latest branch.

                        1 Reply Last reply Reply Quote 0
                        • J Offline
                          jmm
                          last edited by jmm

                          Hi olivier,
                          I have same problem.
                          What do you mean by stable branch.
                          In xo_install.sh it seems to be the master branch.
                          On https://github.com/vatesfr/xen-orchestra I can't find any stable or latest branch
                          Is there another repository were I can find xen-orchestra sources ?

                          Thanks

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

                            In XOA, there's two release channel: stable and latest. It's only in XOA. There's no hidden repository, XOA is a choice of specific commits for each parts to offer the best perfs/stability of Xen Orchestra (this work is done by a big QA pass before a new XOA update)

                            edit: also I have no idea where did you find this xo_install.sh, it's likely a 3rd party script, not something from us.

                            1 Reply Last reply Reply Quote 0
                            • J Offline
                              jmm
                              last edited by

                              Thanks for the reply
                              Sorry but I need to be sure that we are talking about the same thing.
                              I am talking about building from sources.
                              If I follow the instructions provided here https://xen-orchestra.com/docs/from_the_sources.html
                              I can find : git clone -b master http://github.com/vatesfr/xen-orchestra
                              It seems to mean that we clone master branch
                              Should I replace master with stable or latest ?

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

                                1. I wasn't talking about the build from the sources, I was asking about XOA behavior, which seems to work in both channels.
                                2. There's no branch other than master for the sources.

                                If you are using XO for production, I would strongly suggest to switch to XOA (to also get remote support and the updater).

                                Otherwise, on the sources, you might rebuild it from a commit that works for you. @julien-f will be back Monday and he'll take a look.

                                J 1 Reply Last reply Reply Quote 0
                                • J Offline
                                  jmm @olivierlambert
                                  last edited by

                                  @olivierlambert thank's

                                  borzelB 1 Reply Last reply Reply Quote 0
                                  • borzelB Offline
                                    borzel XCP-ng Center Team @jmm
                                    last edited by

                                    @jmm you can also build from a tag to get a consitsent state

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

                                      @borzel said in Can't restore individual files:

                                      @jmm you can also build from a tag to get a consitsent state

                                      Not really, we do our QA on various npm packages that can be at different versions (eg a plugin with an older version, on xo-server with a more recent one). Being on master is the best solution, because we use "feature branches" to avoid breaking everything (but bug still could appear indeed)

                                      1 Reply Last reply Reply Quote 0
                                      • J Offline
                                        jmm
                                        last edited by

                                        Hi @julien-f did you find something ?

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

                                          We'll have a release next week based on a more recent commits, so if there is any issues on XO code, our QA will spot it 🙂

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

                                            So after a discussion with our devs, the change you told us in the commit was already embed in latest release of XOA, and it works.

                                            Also we tested locally, it works even on an Ubuntu 18.04. So we can't reproduce.

                                            Please try to delete/reinstall your XO or try to find a way to reproduce it easily for everyone.

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