ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Xen Orchestra - Permissions Issue - File level restore

    Scheduled Pinned Locked Moved IT Discussion
    xen orchestrapermissionsdebian 8
    74 Posts 4 Posters 9.1k Views
    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.
    • DustinB3403D
      DustinB3403
      last edited by

      Systemctl is operating the server service.

      systemctl status xo-server.service
      รข xo-server.service - XO Server
        Loaded: loaded (/etc/systemd/system/xo-server.service; enabled)
         Active: active (running) since Tue 2016-12-20 16:13:31 EST; 7min ago
       Main PID: 414 (node)
         CGroup: /system.slice/xo-server.service
                 รขรข414 /usr/local/bin/node ./bin/xo-server
      
      1 Reply Last reply Reply Quote 0
      • DanpD
        Danp @DustinB3403
        last edited by Danp

        @DustinB3403 Details please! ๐Ÿ˜‰ I know you're on Debian 8. Is the process different than on Unbuntu where we used systemctl to create a service?

        Edit: Thanks!

        1 Reply Last reply Reply Quote 0
        • DustinB3403D
          DustinB3403
          last edited by DustinB3403

          I'm stretching my memory here, now only god knows what I did to get this working.... ๐Ÿ˜„

          FML.... the service has to be started with my user account, it's the only thing that makes any sense. So I'm curious if I can get the service to start with root instead...

          travisdh1T 1 Reply Last reply Reply Quote 0
          • travisdh1T
            travisdh1 @DustinB3403
            last edited by

            @DustinB3403 said in Xen Orchestra - Permissions Issue - File level restore:

            I'm stretching my memory here, now only god knows what I did to get this working.... ๐Ÿ˜„

            FML.... the service has to be started with my user account, it's the only thing that makes any sense. So I'm curious if I can get the service to use root instead...

            Did you use the instructions on Mangolassi here to get everything installed and running? If so, it's running under systemd.

            DustinB3403D 1 Reply Last reply Reply Quote 0
            • DustinB3403D
              DustinB3403 @travisdh1
              last edited by

              @travisdh1 said in Xen Orchestra - Permissions Issue - File level restore:

              @DustinB3403 said in Xen Orchestra - Permissions Issue - File level restore:

              I'm stretching my memory here, now only god knows what I did to get this working.... ๐Ÿ˜„

              FML.... the service has to be started with my user account, it's the only thing that makes any sense. So I'm curious if I can get the service to use root instead...

              Did you use the instructions on Mangolassi here to get everything installed and running? If so, it's running under systemd.

              I wrote the instructions!

              1 Reply Last reply Reply Quote 0
              • DustinB3403D
                DustinB3403
                last edited by

                ps aux | grep xo-server
                root       414  1.6  9.3 295696 192600 ?       Ssl  16:13   0:14 /usr/local/bin/node ./bin/xo-server
                xoadmin   1407  0.0  0.1   4564  2232 pts/0    S+   16:28   0:00 grep xo-server
                
                DanpD 1 Reply Last reply Reply Quote 0
                • DanpD
                  Danp @DustinB3403
                  last edited by

                  @DustinB3403 The 2nd line is just your current command. So it appears that node / xo-server are running as root.

                  DustinB3403D 1 Reply Last reply Reply Quote 1
                  • DustinB3403D
                    DustinB3403 @Danp
                    last edited by

                    @Danp said in Xen Orchestra - Permissions Issue - File level restore:

                    @DustinB3403 The 2nd line is just your current command. So it appears that node / xo-server are running as root.

                    Then the issues isn't a permission one, as @julian said in the OP..... which means it's something else to be able to mount the VHD..

                    1 Reply Last reply Reply Quote 0
                    • DustinB3403D
                      DustinB3403
                      last edited by

                      This is what I currently get from logging while trying to select a VHD to mount.

                      Dec 20 16:35:56 xo-test-debian-3 xo-server[414]: Tue, 20 Dec 2016 21:35:56 GMT xo:api admin@eagleproductivity.com | remote.getAll(...) [2ms] ==> array
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: Tue, 20 Dec 2016 21:35:57 GMT xo:perf blocked for 108ms
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: Tue, 20 Dec 2016 21:35:57 GMT xo:api admin@eagleproductivity.com | backup.scanDisk(...) [311ms] =!> Error: Command failed: vhdimount /run/xo-server/mounts/remote-17/vm_delta_qlik-exchange_0d05dd84-91eb-473b-d11d-7864049430b5/vdi_c143c2e0-5149-455b-9730-73e08585e09a/20161214T030158Z_delta.vhd /tmp/tmp-4144UyM2UZtgAHO
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: Unable to open source file.
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: libcfile_file_open_with_error_code: no such file: /run/xo-server/mounts/remote-17/vm_delta_qlik-exchange_0d05dd84-91eb-473b-d11d-7864049430b5/vdi_c143c2e0-5149-455b-9730-73e08585e09a/20161214T030158Z_delta.vhd.
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: libcfile_file_open: unable to open file.
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: libbfio_file_open: unable to open file: /run/xo-server/mounts/remote-17/vm_delta_qlik-exchange_0d05dd84-91eb-473b-d11d-7864049430b5/vdi_c143c2e0-5149-455b-9730-73e08585e09a/20161214T030158Z_delta.vhd.
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: libcfile_file_get_size: invalid file - missing descriptor.
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: libbfio_file_get_size: unable to retrieve size of file: /run/xo-server/mounts/remote-17/vm_delta_qlik-exchange_0d05dd84-91eb-473b-d11d-7864049430b5/vdi_c143c2e0-5149-455b-9730-73e08585e09a/20161214T030158Z_delta.vhd.
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: libbfio_handle_get_size: unable to retrieve size.
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: libvhdi_file_open_read: unable to retrieve file size.
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: libvhdi_file_open_file_io_handle: unable to read from file handle.
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: libvhdi_file_open: unable to open file: /run/xo-server/mounts/remote-17/vm_delta_qlik-exchange_0d05dd84-91eb-473b-d11d-7864049430b5/vdi_c143c2e0-5149-455b-9730-73e08585e09a/20161214T030158Z_delta.vhd.
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: mount_handle_open_input: unable to open input file.
                      Dec 20 16:35:57 xo-test-debian-3 xo-server[414]: vhdimount 20150110
                      
                      DanpD 1 Reply Last reply Reply Quote 0
                      • DustinB3403D
                        DustinB3403
                        last edited by DustinB3403

                        I'm also seeing this.... fusermount issue but for a different backup.

                        Dec 20 16:40:09 xo-test-debian-3 xo-server[414]: Tue, 20 Dec 2016 21:40:09 GMT xo:api admin@domain.com | backup.scanDisk(...) [214ms] =!> Error: spawn fusermount ENOENT
                        
                        1 Reply Last reply Reply Quote 0
                        • DanpD
                          Danp
                          last edited by

                          I wonder if any of the items described here apply to your situation?

                          1 Reply Last reply Reply Quote 0
                          • DanpD
                            Danp @DustinB3403
                            last edited by

                            Check to see if the path and file actually exist.

                            DustinB3403D 1 Reply Last reply Reply Quote 0
                            • DustinB3403D
                              DustinB3403 @Danp
                              last edited by

                              @Danp I'll take a look for the file first thing tomorrow when I'm back at the office, I have some errands I have to run this afternoon.

                              1 Reply Last reply Reply Quote 0
                              • DustinB3403D
                                DustinB3403
                                last edited by

                                I don't have the VHD (20161214T030158Z_delta.vhd) listed from the 14th (it's at my rotation schedule) so that doesn't mean much...

                                Once the dates are fixed testing this will be a bit easier.

                                DanpD 1 Reply Last reply Reply Quote 0
                                • DanpD
                                  Danp @DustinB3403
                                  last edited by

                                  @DustinB3403 You could temporarily build from next-release. ๐Ÿ˜

                                  DustinB3403D 1 Reply Last reply Reply Quote 1
                                  • DustinB3403D
                                    DustinB3403 @Danp
                                    last edited by

                                    @Danp yeah...

                                    Guess I have too..

                                    1 Reply Last reply Reply Quote 0
                                    • DustinB3403D
                                      DustinB3403
                                      last edited by

                                      All backups are still listed as being created on January 17th 1970....

                                      1 Reply Last reply Reply Quote 0
                                      • DanpD
                                        Danp
                                        last edited by

                                        Post the output from the following command --
                                        cd /opt/xo-server && git rev-parse --abbrev-ref HEAD

                                        DustinB3403D 1 Reply Last reply Reply Quote 0
                                        • DustinB3403D
                                          DustinB3403 @Danp
                                          last edited by

                                          @Danp 8827f8e940e0f0bc73230e772855640e6cbd8d27

                                          DanpD 1 Reply Last reply Reply Quote 0
                                          • DanpD
                                            Danp @DustinB3403
                                            last edited by

                                            @DustinB3403 Was expecting stable or next-release. How did you perform the update?

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 4 / 4
                                            • First post
                                              Last post