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

capturing image issue

Scheduled Pinned Locked Moved Unsolved
FOG Problems
issue capturing image could not mount images
3
13
2.7k
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
    Charlie
    last edited by Apr 30, 2018, 2:48 PM

    Hello everyone,
    I’ve seen some posts talking about similar issues to mine but none of them helped me, so I’m asking here.
    When I try to capture an image, this happen :
    0_1525097215724_187a4921-6312-4bfd-a1a2-7576639e6262-image.png

    I tried to upload a Windows 10 and 7 image, and tried with fresh install on Fog 1.5.0 and 1.4.4 : same issue.
    When I do a ls - la on /images I got this :
    0_1525098893176_20b91d62-efcd-4679-b4e8-019ccc5736f7-image.png but when I try to mannually mount /images/dev on /images I got this :
    0_1525098920862_273befe2-aadd-4301-93ab-6516ef595348-image.png I did a lot of things that I saw on other posts without success (like modifying nfs parameters, etc…).
    I’m running on Proxmox VE 5.1, and the Vm for the fog service is a debian 8.0. All my network is on 192.168.12.XXX.
    Thanks in advance for your help.

    G 1 Reply Last reply Apr 30, 2018, 3:03 PM Reply Quote 0
    • G
      george1421 Moderator @Charlie
      last edited by Apr 30, 2018, 3:03 PM

      @charlie Can you post the output of this command: showmount -e 127.0.0.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
      • C
        Charlie
        last edited by Apr 30, 2018, 5:38 PM

        Thanks for your answer, it gave me this message :
        0_1525109673906_8206b2e0-1d57-44e1-bf0e-55c2c7fb3fc1-image.png
        does it have a relation with the nfs service ? Sorry i’m a beginner with Linux.

        G 1 Reply Last reply Apr 30, 2018, 10:26 PM Reply Quote 0
        • G
          george1421 Moderator @Charlie
          last edited by Apr 30, 2018, 10:26 PM

          @charlie Yes, this tells us that the nfs service is not running on your fog server, or you did not disable the native linux firewall.

          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 May 1, 2018, 12:28 PM Reply Quote 0
          • C
            Charlie @george1421
            last edited by May 1, 2018, 12:28 PM

            @george1421 Thanks again, I tried this
            0_1525176987916_68df4e0e-17b8-42b2-84b3-d358cc3c5739-image.png
            and then
            0_1525177015058_ec7fe3c3-f911-4ade-b04f-7511f712c664-image.png
            and I got this
            0_1525177035600_8a0e3342-435e-4572-978f-57e2e7315dbb-image.png
            but I’ve still the “Programm not registred” when I do the showmount.
            So, i tried to start the nfs service :
            0_1525177522592_ee92bb74-f365-4f53-8c51-e77bdcb2dba2-image.png
            Should I update something or did I missed something when I installed ? Sorry again I’m not familiar with linux.

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Sebastian Roth May 2, 2018, 1:30 AM May 2, 2018, 7:24 AM

              @charlie said in capturing image issue:

              I’m running on Proxmox VE 5.1, and the Vm for the fog service is a debian 8.0.
              …
              Not starting NFS kernel daemon: no support in current kernel. ... (warning).

              I’ve had that too back when using FOG in a Proxmox container. First you need to check if the nfsd module is installed and loaded in your Proxmox host system (not the VM but the underlaying system!):

              # modprobe nfsd
              # lsmod | grep nfsd
              nfsd                  312315  14
              # grep nfsd /proc/filesystems
              nodev   nfsd
              

              Then you need to sort of activate that module for the VM as well:

              # vzctl stop $CONTAINER_ID
              # vzctl set $CONTAINER_ID --feature  nfsd:on --save
              # vzctl start $CONTAINER_ID
              

              Now when the VM is back up you should see a proper output running showmount -e 127.0.0.1…

              LXC Containers

              For those take a look at the forum post here: https://forums.fogproject.org/topic/7978/fog-in-lxc-container-how-to-configure-nfs-server

              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

              C 2 Replies Last reply May 2, 2018, 5:37 PM Reply Quote 0
              • C
                Charlie @Sebastian Roth
                last edited by May 2, 2018, 5:37 PM

                @sebastian-roth Hello and thanks for your answer. I followed your instructions so I got :
                0_1525282498476_395ce3fa-58c9-4d58-b770-dee0d037fdb3-image.png
                0_1525282508872_a43946ed-0c68-4926-828a-129e863479bd-image.png
                but then I got this :
                0_1525282522004_b948ef1b-363b-4d71-8f5d-a4784871f8d1-image.png
                Do I need to download or update something for this command to be recognized ?
                Thanks in advance.

                1 Reply Last reply Reply Quote 0
                • C
                  Charlie @Sebastian Roth
                  last edited by May 2, 2018, 6:22 PM

                  @sebastian-roth I also did edit the file /etc/apparmor.d/lxc/lxc-default-cgns as shown in your link.

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sebastian Roth Moderator
                    last edited by May 2, 2018, 9:07 PM

                    @Charlie What kind of VMs/containers do you use on your Proxmox server?

                    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

                    C 1 Reply Last reply May 3, 2018, 6:58 AM Reply Quote 0
                    • C
                      Charlie @Sebastian Roth
                      last edited by May 3, 2018, 6:58 AM

                      @sebastian-roth I’m using LXC containers.

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by May 3, 2018, 5:28 PM

                        @Charlie Maybe this would help? https://forum.proxmox.com/threads/is-it-possible-to-run-a-nfs-server-within-a-lxc.24403/

                        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

                        C 1 Reply Last reply May 4, 2018, 8:48 AM Reply Quote 0
                        • C
                          Charlie @Sebastian Roth
                          last edited by May 4, 2018, 8:48 AM

                          @sebastian-roth Thanks again for your help, I’ll try this when I’ll go back to work. I’ll keep you informed about it.

                          1 Reply Last reply Reply Quote 0
                          • C
                            Charlie
                            last edited by May 10, 2018, 3:45 PM

                            hello,
                            I couldn’t find a solution to unlock my situation, I tried many things on promox and on fog, without succes again. So I decided to start a new install on another post, separated from the proxmox and it’s working fine. I think I’ll keep this solution so, thanks for your help and sorry to leave an unsolved issue, see you later !

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

                            149

                            Online

                            12.0k

                            Users

                            17.3k

                            Topics

                            155.2k

                            Posts
                            Copyright © 2012-2024 FOG Project