• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Storage Node Permission Denied

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    16
    1.9k
    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.
    • C
      CoxM @george1421
      last edited by

      @george1421 said in Storage Node Permission Denied:

      @coxm well that is where your access denied message is coming from.

      As a test, update /etc/exportfs to the real locations. And then run the export -a command. And finally run the showmount command again to ensure the proper directories are shared.

      Sorry, I dont follow. I dont have /etc/exportfs.

      The only thing like it in /etc is /exports

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @CoxM
        last edited by george1421

        @coxm ok so I have fat fingers. That is the right file. You should see the same shares in there as when you first ran the showmount command.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        1 Reply Last reply Reply Quote 0
        • C
          CoxM
          last edited by

          @george1421 I do indeed but with loads of options in (), do I need options?

          Also, whats the path to enter as a mount point? /data/images/*?

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @CoxM
            last edited by george1421

            @coxm whelp, if you look at the exports file it should look something like this:

            /images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
            /images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
            

            Knowing that a standard fog server places its images in /images and you placed the images files in /media/ubuntuadmin/Data/Images what might you think you need to update? Also watch the capitalization in the path.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            C 1 Reply Last reply Reply Quote 0
            • C
              CoxM @george1421
              last edited by

              @george1421
              Hi,
              I have updates the script as you suggested so it now looks like this when doing a showmount -e
              0_1519214424109_fog12.JPG

              but when I run a deply task against a remote machine, that is in the right location group to use the storage node rather than the main fog server it get this.

              0_1519214504619_fog13.JPG

              Notice the difference in path from the showmount output to the path in the image screen grab - this suggest that the path is being pulled from the path entered in the Fog UI, not the mount point.

              1 Reply Last reply Reply Quote 0
              • C
                CoxM
                last edited by

                Felt like the answer was obvious so changed the Fog UI path to match the mount point path.

                So both read Data not Data1.

                This is what we get.

                0_1519214855299_fog14.JPG

                george1421G S 2 Replies Last reply Reply Quote 0
                • george1421G
                  george1421 Moderator @CoxM
                  last edited by

                  @coxm While I would not have added the big disk like you did, you still should be able to make it work.

                  If you look in the exports file you should see two file share lines. You updated the one for /images but you missed the one for /images/dev.

                  FOG captures to /images/dev then moves the file to /images which is read only. This is done to protect the captured image from accidental deletion. You can see the ro vs rw access in the line below, its the first parameter.

                  /images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
                  /images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
                  

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sebastian Roth Moderator @CoxM
                    last edited by

                    @coxm Try sudo touch /media/ubuntuadmin/Data/images/.mntcheck and then try deploy again.

                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                    1 Reply Last reply Reply Quote 0
                    • C
                      CoxM
                      last edited by

                      Thanks @george1421 and @Sebastian-Roth with you help and some trial and error it is now working and the remote client try to image via the storage node.

                      george1421G 1 Reply Last reply Reply Quote 0
                      • george1421G
                        george1421 Moderator @CoxM
                        last edited by

                        @coxm Now that you have a working solution, I’ll tell you a bit easier way to go about this.

                        If you know ahead of time you will keep the OS on a thin image and have the /images on a separate disk then before you install fog create the /images directory and mount your image storage disk over /images and finally install FOG. There will be nothing to change post installation. If you see you need to add the disk after fog is install there are a few more steps involved but that’s basically it.

                        https://forums.fogproject.org/topic/11048/moving-fog-s-images-files-off-the-root-partition-2017-edition

                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

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

                        161

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.4k

                        Posts
                        Copyright © 2012-2024 FOG Project