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

    XO Remote mount.nfs: access denied by server while mounting

    Scheduled Pinned Locked Moved Xen Orchestra
    26 Posts 7 Posters 11.4k Views 5 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.
    • M Offline
      mjtbrady @daninmanchester
      last edited by

      @daninmanchester

      What is the IP address of the host that is running XO?

      The docker container will need the SYS_ADMIN capability to do NFS mounts.

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

        @daninmanchester I would think Docker is involved, as well. I was going to suggest to create a "standard" test VM ans see if you can connect storage to it. If so, that would put the blame on something specific to the VM that has that Docker container.

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

          @mjtbrady That seems right, because the Docker instanceis independent and internal to the VM that otherwise is part of the XCP-ng networking structure and wouldn't have the necessary access permissions on it's own.

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

            Could this be due to a missing package (nfs-common)?

            1 Reply Last reply Reply Quote 0
            • daninmanchesterD Offline
              daninmanchester
              last edited by

              I setup another VM as someone suggested and the NFS share mounted and worked. So there is something I am not understanding about docker permissions / requirements.

              In the end, following a permissions reset and forcing the NFS share to squash and use my user/group ID I think I have progress. I can see it is writing to the NFS share.

              Then I got : EEXIST: file already exists, open '/run/xo-server/mounts/6299d107-2aa2-41bf-bfd7-2f487ff5422f/xo-vm-backups/801e2b10-5c7d-b7af-ad5e-fbcc83e47d5b/.20220930T221548Z.xva'

              A quick google led me to this being related to nfs 3. I switched to NFS 4 then I got path not found.

              Not sure why, but I tried removing "export" from the path and it worked.

              It does appear now to be running a backup job .... fingers crossed.

              What a mine field!

              Thanks for all the pointers.

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

                @daninmanchester Yes, a mine field is about right. Super good ou have made so much progress!

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

                  Now you understand why we sell/distribute XO in a virtual appliance we can test 😉

                  daninmanchesterD 1 Reply Last reply Reply Quote 0
                  • daninmanchesterD Offline
                    daninmanchester @olivierlambert
                    last edited by

                    @olivierlambert I think the intricacies of NFS, my seemingly borked NFS permissions were likely the real issue. I rarely have real problems with XO. I tried proxmox but didn't get on with it so switched back.

                    I'm just a home / homelab user, but always impressed with the community around XCP-NG too and have learnt a huge amount from Lawrence Systems.

                    Anyway this morning I have a successful backup completed :

                    c3c60198-2937-4e62-af46-3373173fa89c-image.png

                    Thanks again.

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

                      Great news! Enjoy 🙂

                      1 Reply Last reply Reply Quote 0
                      • P Offline
                        parallax @daninmanchester
                        last edited by

                        @daninmanchester Thanks so much - this is the exact same problem I had, which was further complicated by running XO in Docker running on the OMV host exporting the NFS shares.

                        So basically you just built a small XO VM instead of running it in Docker? I had originally been thinking of making a small VM to run XO in a container there - just because Docker containers are super easy to keep updated and I could run some other orchestration-y stuff there too, like Rancher - but if you're saying that's a non-starter I'll just bite the bullet and build a tiny VM dedicated to XO and be very grateful to you for having saved me a lot of frustration. 😊

                        1 Reply Last reply Reply Quote 0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better 💗

                        Register Login
                        • First post
                          Last post