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.8k 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 @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
        • DustinB3403D
          DustinB3403
          last edited by

          One sec, realized I was only on NR for xo-server and not xo-web, just did a checkout for web, and running the update.

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

            There we go, now it's

            cd /opt/xo-server && git rev-parse --abbrev-ref HEAD
next-release
            1 Reply Last reply Reply Quote 0
            • DanpD
              Danp
              last edited by

              Should have used the update script. 😛

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

                Building mine now on next-release to test

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

                  I do use the update script to perform the update, but you added flags didnt you... dang it I keep forgetting about those lol...

                  Anyways the file level backups still list 1970 as the creation date.

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

                    @DustinB3403 My dates are correct after rebuilding on next-release.

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

                      @Danp Hrm...

                      Mine are still clustered. . . .
                      0_1482335635343_XenCenterMain_2016-12-21_10-53-47.png

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

                        Try with a force rebuild -- sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f

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

                          @Danp Trying now

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

                            Now I've got actual dates. Progress!

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

                              Ok so (office party atm) but did you get your fuse issue corrected?

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

                                @DustinB3403 I haven't experienced the fuser error

                                Edit: Fixed missing negative

                                travisdh1T DustinB3403D 2 Replies Last reply Reply Quote 0
                                • travisdh1T
                                  travisdh1 @Danp
                                  last edited by

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

                                  @DustinB3403 I have experienced the fuser error

                                  Totally off topic: How can you not love Linux/UNIX, especially when we have errors telling us fuser.

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

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

                                    @DustinB3403 I haven't experienced the fuser error

                                    Edit: Fixed missing negative

                                    So are you able to restore files?

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

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

                                      So are you able to restore files?

                                      Nope. Either getting errors in the log like this --

                                      
Dec 21 11:27:23 xo-5 xo-server[26997]: { Error: Command failed: mount --options=loop,ro,offset=1048576,noload --source=/tmp/tmp-269977KZDUzPQPshd/vhdi1 --target=/tmp/tmp-26997NWHkKW0eSCVg
Dec 21 11:27:23 xo-5 xo-server[26997]: mount: wrong fs type, bad option, bad superblock on /dev/loop0,
Dec 21 11:27:23 xo-5 xo-server[26997]:        missing codepage or helper program, or other error
Dec 21 11:27:23 xo-5 xo-server[26997]:        In some cases useful info is found in syslog - try
Dec 21 11:27:23 xo-5 xo-server[26997]:        dmesg | tail or so.
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Promise.all.then.arr (/opt/xo-server/node_modules/execa/index.js:170:11)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at tryCatcher (/opt/xo-server/node_modules/bluebird/js/release/util.js:16:23)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Promise._settlePromiseFromHandler (/opt/xo-server/node_modules/bluebird/js/release/promise.js:510:31)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Promise._settlePromise (/opt/xo-server/node_modules/bluebird/js/release/promise.js:567:18)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Promise._settlePromise0 (/opt/xo-server/node_modules/bluebird/js/release/promise.js:612:10)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Promise._settlePromises (/opt/xo-server/node_modules/bluebird/js/release/promise.js:691:18)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Promise._fulfill (/opt/xo-server/node_modules/bluebird/js/release/promise.js:636:18)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at PromiseArray._resolve (/opt/xo-server/node_modules/bluebird/js/release/promise_array.js:125:19)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at PromiseArray._promiseFulfilled (/opt/xo-server/node_modules/bluebird/js/release/promise_array.js:143:14)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Promise._settlePromise (/opt/xo-server/node_modules/bluebird/js/release/promise.js:572:26)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Promise._settlePromise0 (/opt/xo-server/node_modules/bluebird/js/release/promise.js:612:10)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Promise._settlePromises (/opt/xo-server/node_modules/bluebird/js/release/promise.js:691:18)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Async._drainQueue (/opt/xo-server/node_modules/bluebird/js/release/async.js:138:16)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Async._drainQueues (/opt/xo-server/node_modules/bluebird/js/release/async.js:148:10)
Dec 21 11:27:23 xo-5 xo-server[26997]:     at Immediate.Async.drainQueues (/opt/xo-server/node_modules/bluebird/js/release/async.js:17:14)
Dec 21 11:27:23 xo-5 xo-server[26997]:   code: 32,
Dec 21 11:27:23 xo-5 xo-server[26997]:   killed: false,
Dec 21 11:27:23 xo-5 xo-server[26997]:   stdout: '',
Dec 21 11:27:23 xo-5 xo-server[26997]:   stderr: 'mount: wrong fs type, bad option, bad superblock on /dev/loop0,\n       missing codepage or helper program, or other error\n\n       In some cases useful info is found in syslog - try\n       dmesg | tail or so.\n',
Dec 21 11:27:23 xo-5 xo-server[26997]:   failed: true,
Dec 21 11:27:23 xo-5 xo-server[26997]:   signal: null,
Dec 21 11:27:23 xo-5 xo-server[26997]:   cmd: 'mount --options=loop,ro,offset=1048576,noload --source=/tmp/tmp-269977KZDUzPQPshd/vhdi1 --target=/tmp/tmp-26997NWHkKW0eSCVg' }
Dec 21 11:27:23 xo-5 xo-server[26997]: Wed, 21 Dec 2016 17:27:23 GMT xo:api dan@mydomain.com | backup.scanFiles(...) [233ms] =!> Error: Command failed: mount --options=loop,ro,offset=1048576,noload --source=/tmp/tmp-269977KZDUzPQPshd/vhdi1 --target=/tmp/tmp-26997NWHkKW0eSCVg
Dec 21 11:27:23 xo-5 xo-server[26997]: mount: wrong fs type, bad option, bad superblock on /dev/loop0,
Dec 21 11:27:23 xo-5 xo-server[26997]:        missing codepage or helper program, or other error
Dec 21 11:27:23 xo-5 xo-server[26997]:        In some cases useful info is found in syslog - try
Dec 21 11:27:23 xo-5 xo-server[26997]:        dmesg | tail or so.

                                      or else this

                                      Dec 21 11:51:40 xo-5 xo-server[26997]: Wed, 21 Dec 2016 17:51:40 GMT xo:api dan@mydomain.com | backup.scanDisk(...) [17ms] =!> Error: EROFS: read-only file system, mkdir '/tmp/tmp-26997k3oduVxLfSa8'
                                      1 Reply Last reply Reply Quote 0
                                      • DanpD
                                        Danp
                                        last edited by

                                        Probably should restart the VM to see if that changes anything with the read-only issue.

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

                                          Yeah I'm still getting that fusermount error...

                                          Dec 21 12:59:25 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:25 GMT xo:api admin@domain.com | remote.getAll(...) [2ms] ==> array
Dec 21 12:59:28 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:28 GMT xo:api admin@domain.com | resourceSet.getAll(...) [2ms] ==> array
Dec 21 12:59:28 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:28 GMT xo:api admin@domain.com | acl.getCurrentPermissions(...) [2ms] ==> object
Dec 21 12:59:30 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:30 GMT xo:api admin@domain.com | remote.getAll(...) [2ms] ==> array
Dec 21 12:59:31 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:31 GMT xen-api root@192.168.101.50: event.from(...) [30s] ==> object
Dec 21 12:59:31 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:31 GMT xen-api root@192.168.101.50: event.from(...) [14ms] ==> object
Dec 21 12:59:33 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:33 GMT xo:api admin@domain.com | resourceSet.getAll(...) [3ms] ==> array
Dec 21 12:59:33 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:33 GMT xo:api admin@domain.com | acl.getCurrentPermissions(...) [3ms] ==> object
Dec 21 12:59:35 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:35 GMT xo:api admin@domain.com | backup.scanDisk(...) [887ms] =!> Error: spawn fusermount ENOENT
Dec 21 12:59:35 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:35 GMT xo:api admin@domain.com | remote.getAll(...) [3ms] ==> array
Dec 21 12:59:38 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:38 GMT xo:api admin@domain.com | resourceSet.getAll(...) [3ms] ==> array
Dec 21 12:59:38 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:38 GMT xo:api admin@domain.com | acl.getCurrentPermissions(...) [3ms] ==> object
Dec 21 12:59:40 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:40 GMT xen-api root@192.168.100.216: event.from(...) [1m] ==> object
Dec 21 12:59:40 xo-test-debian-3 xo-server[5648]: Wed, 21 Dec 2016 17:59:40 GMT xo:api admin@domain.com | remote.getAll(...) [2ms] ==> array
                                          DanpD 1 Reply Last reply Reply Quote 0
                                          • DanpD
                                            Danp
                                            last edited by

                                            There was definitely something wrong with the VM's state. Whoami returned unknown uid. Had to forcibly reboot from within XO.

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