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

    Imaging works in VM and not on bare metal

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    25
    2.5k
    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.
    • S
      Sebastian Roth Moderator
      last edited by

      @Claw22000 So what exactly is between bare metal and the FOG server? Host firewall in the VM server? Layer 7 switch with application layer gateway/firewall?

      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 Reply Quote 0
      • C
        Claw22000 @Sebastian Roth
        last edited by Sebastian Roth

        @sebastian-roth
        My setup is is this

        Hypervisor: VMware ESXi, 6.5.0, 14320405
        Model: PowerEdge R815
        Processor Type: AMD Opteron™ Processor 6276
        Logical Processors: 64
        Ram: 186 Gigs

        2 NICS are use and 1 DRAC
        1 NIC is directly to the Modem and only accessed by PFSense
        the other NIC is shared across all the the VMs PFSense feeding the internet.
        The DRAC and internal Network run to a SG 200-08 8-Port Gigabit Smart Switch (Spanning Tree is disabled)
        This runs to the other side of the lab to a Netgear JGS516 16 Port unmanaged switch

        All computers in the house are then wired to this switch.

        VM for the FOG server is
        4 CPU’s across 2 sockets with at least 1GHZ reservation
        8GB Ram with at least 4Gig Reservation
        HD is Thick provisioned with 300gigs. I will increase this once I document how this works and it will get a dedicated drive for this
        NIC Adapter Type is VMXNET 3

        Install steps of current server
        sudo -i
        wget https://github.com/FOGProject/fogproject/archive/1.5.9.tar.gz
        tar -xzvf 1.5.9.tar.gz
        rm 1.5.9.tar.gz
        cd fogproject-1.5.9/bin
        ./installfog.sh
        click button in browser
        press enter in termanal
        log in
        change default password
        create new user for self
        chmod -R 777 /images
        chown fogproject:nogroup /images

        Info after all this is done.
        sudo iptables -L
        Chain INPUT (policy ACCEPT)
        target prot opt source destination

        Chain FORWARD (policy ACCEPT)
        target prot opt source destination

        Chain OUTPUT (policy ACCEPT)
        target prot opt source destination

        /etc/hosts.deny
        # /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
        #                  See the manual pages hosts_access(5) and hosts_options(5).
        #
        # Example:    ALL: some.host.name, .some.domain
        #             ALL EXCEPT in.fingerd: other.host.name, .other.domain
        #
        # If you're going to protect the portmapper use the name "rpcbind" for the
        # daemon name. See rpcbind(8) and rpc.mountd(8) for further information.
        #
        # The PARANOID wildcard matches any host whose name does not match its
        # address.
        #
        # You may wish to enable this to ensure any programs that don't
        # validate looked up hostnames still leave understandable logs. In past
        # versions of Debian this has been the default.
        # ALL: PARANOID
        
        /etc/exports
        /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)
        
        ls -al /
        drwxr-xr-x  23 root       root          4096 Mar 20 22:50 .
        drwxr-xr-x  23 root       root          4096 Mar 20 22:50 ..
        lrwxrwxrwx   1 root       root             7 Jul 31  2020 bin -> usr/bin
        drwxr-xr-x   3 root       root          4096 Mar 20 18:57 boot
        drwxr-xr-x   2 root       root          4096 Mar 20 17:15 cdrom
        drwxr-xr-x  17 root       root          4000 Mar 20 18:51 dev
        drwxr-xr-x 102 root       root          4096 Mar 21 15:55 etc
        drwxr-xr-x   4 root       root          4096 Mar 20 22:41 home
        drwxrwxrwx   5 fogproject nogroup       4096 Mar 20 23:15 images
        lrwxrwxrwx   1 root       root             7 Jul 31  2020 lib -> usr/lib
        lrwxrwxrwx   1 root       root             9 Jul 31  2020 lib32 -> usr/lib32
        lrwxrwxrwx   1 root       root             9 Jul 31  2020 lib64 -> usr/lib64
        lrwxrwxrwx   1 root       root            10 Jul 31  2020 libx32 -> usr/libx32
        drwx------   2 root       root         16384 Mar 20 17:14 lost+found
        drwxr-xr-x   2 root       root          4096 Jul 31  2020 media
        drwxr-xr-x   2 root       root          4096 Jul 31  2020 mnt
        drwxr-xr-x   3 root       root          4096 Mar 20 22:41 opt
        dr-xr-xr-x 291 root       root             0 Mar 20 18:51 proc
        drwx------   5 root       root          4096 Mar 21 07:27 root
        drwxr-xr-x  36 root       root          1140 Mar 21 15:51 run
        lrwxrwxrwx   1 root       root             8 Jul 31  2020 sbin -> usr/sbin
        drwxr-xr-x   6 root       root          4096 Mar 20 18:52 snap
        drwxr-xr-x   4 root       root          4096 Mar 20 22:41 srv
        -rw-------   1 root       root    4294967296 Mar 20 17:18 swap.img
        dr-xr-xr-x  13 root       root             0 Mar 20 18:51 sys
        drwxr-xr-x   5 fogproject root          4096 Mar 20 22:50 tftpboot
        drwxr-xr-x   2 root       root          4096 Mar 20 22:50 tftpboot.prev
        drwxrwxrwt  15 root       root          4096 Mar 21 15:39 tmp
        drwxr-xr-x  14 root       root          4096 Jul 31  2020 usr
        drwxr-xr-x  14 root       root          4096 Mar 20 22:34 var
        
        ls -al /images
        -rwxrwxrwx  1 fogproject root       0 Mar 21 07:20 .mntcheck
        drwxrwxrwx  3 fogproject root    4096 Mar 20 23:15 dev
        drwxrwxrwx  2 fogproject root    4096 Mar 20 22:50 postdownloadscripts
        drwxrwxrwx  2 root       root    4096 Mar 20 23:15 win10basic
        
        ls -al /images/dev
        drwxrwxrwx 3 fogproject root    4096 Mar 20 23:15 .
        drwxrwxrwx 5 fogproject nogroup 4096 Mar 20 23:15 ..
        -rwxrwxrwx 1 fogproject root       0 Mar 20 22:50 .mntcheck
        drwxrwxrwx 2 fogproject root    4096 Mar 20 22:50 postinitscripts
        

        Hope this helps I really appreciate your help. Sorry it takes so long to get back some times I work 50 - 60 hours a week so get wrapped up alot

        Claw

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

          @Claw22000 Can’t see anything obvious causing the described issue.

          When you boot up a machine (bare metal), are you able to ping the FOG server and access it’s web interface in the browser from that machine?

          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 Reply Quote 0
          • C
            Claw22000 @Sebastian Roth
            last edited by

            @sebastian-roth Yes you can access the HTML side and ping the server. I’m stumped. I would be glad to let you see it your self if you have time. I’m a mid to low level linux user so I might be missing something obvious.

            Claw

            1 Reply Last reply Reply Quote 0
            • C
              Claw22000 @Sebastian Roth
              last edited by

              @sebastian-roth Ok some progress today. I tried the following commands and it failed

              mkdir /images
              mkdir /images/dev
              mount -o nolock,proto=tcp,rsize=32768,intr,noatime x.x.x.x:/images /images
              mount -o nolock,proto=tcp,rsize=32768,intr,noatime x.x.x.x:/images/dev/ /images/dev

              However the following command worked

              mount -o nolock,proto=udp,rsize=32768,intr,noatime x.x.x.x:/images /images
              mount -o nolock,proto=udp,rsize=32768,intr,noatime x.x.x.x:/images/dev/ /images/dev

              I am able to list the files in the folder and it works correctly.

              So now the issue is why TCP doesn’t work on the bare metal and does work on the VM.

              Suggestions?

              Claw

              Tom ElliottT 1 Reply Last reply Reply Quote 0
              • Tom ElliottT
                Tom Elliott @Claw22000
                last edited by

                @claw22000 so I presume there is a firewall between the fog server vm and the bare metal machines.

                The reason vm to vm works is because they reside on the same side of the switch within the same subnet that the fog vm does. Your firewall likely allows port 80/443 from bare metal to the fog vm network. UDP may be fully allowed on the firewall? Not 100% sure of the network layout but this seems like a firewall issue. The only reason I think udp is working is because maybe an assumption was made that the fog server needed multicast capabilities?

                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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                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
                  Claw22000
                  last edited by

                  I appreciate the help. When you say firewall are you talking about my PFsense Box or are we talking about something that resides in the FogServer?

                  Claw

                  S Tom ElliottT 2 Replies Last reply Reply Quote 0
                  • S
                    Sebastian Roth Moderator @Claw22000
                    last edited by

                    @claw22000 said in Imaging works in VM and not on bare metal:

                    I appreciate the help. When you say firewall are you talking about my PFsense Box or are we talking about something that resides in the FogServer?

                    From what you posted so far (Debian 10 and output iptables command) I would not think this is an issue on the FOG server itself.

                    While I would not think the SG 200-08 (Cisco, right?) or the Netgear JGS516 do block such traffic it’s still worth to try and rule those out one by one. Please connect one of the bare metal machines directly to the SG 200-08 and see if that makes a difference. If NFS in TCP mode still doesn’t work, then could you take out the Cisco switch of the setup by connecting the Netgear uplink cable to your ESXi directly - just for a quick test I mean.

                    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
                    • Tom ElliottT
                      Tom Elliott @Claw22000
                      last edited by

                      @claw22000 The unfortunate part is we don’t know. Could it be the PFSense box? Yes. Could it be a switch misconfiguration? Possibly.

                      Based on the information you’ve given us so far, though, it really seems to be a firewall type thing. Does this mean it absolutely is? No. As @sebastian-roth has alluded to, we have to take out and replace variables to more definitively get to the root of the issue.

                      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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                      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
                      • S
                        Sebastian Roth Moderator
                        last edited by

                        @Tom-Elliott From the description so far I wouldn’t think that pfSense is connected in between.

                        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 Reply Quote 0
                        • C
                          Claw22000 @Sebastian Roth
                          last edited by

                          @sebastian-roth Great info guys I ordered an unmanaged switch to replace the managed on to see if that corrects the issue. I don’t use any of its features since Its just My family and I. I just like to nerd out and this was a gift to play with. Haven’t change a thing on it since the day I received it. I will report back as soon as I am able to test. Should be here Tuesday.

                          Claw

                          1 Reply Last reply Reply Quote 1
                          • C
                            Claw22000 @Sebastian Roth
                            last edited by

                            @sebastian-roth Great news the unmanaged switch showed up and its solved the issue I was having. I have had that thing for going on a decade and never had an issue with it. Well I learned a big lesson if you don’t need a managed switch and your not using VLANs your better off with an unmanaged switch.

                            Crazy thing is never had any other issues with it.

                            Thank you all for helping me trouble shoot this. If any one comes across this a cheap Netgear unmanaged switch from amazon will let you test to see if this was also your issue!

                            Claw

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

                              @Claw22000 Great to hear!! So did swapping out the Cisco or the Netgear switch solve the issue? You saying better use an unmanaged is somehow confusing.

                              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 Reply Quote 0
                              • C
                                Claw22000 @Sebastian Roth
                                last edited by

                                @sebastian-roth Sorry about the confusion. The Cisco is managed and the new Netgear is unmanaged. taking the Cisco out of the mix fixed the issue.

                                Claw

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

                                  @Claw22000 So probably the Cisco SG 200-8 has some kind of upper network layer “security” features that prevent NFS over TCP. Strange but good to know.

                                  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
                                  • 1
                                  • 2
                                  • 1 / 2
                                  • First post
                                    Last post

                                  197

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project