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

DHCP problems on storage nodes

Scheduled Pinned Locked Moved Solved
FOG Problems
4
62
15.1k
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.
  • G
    Greg Plamondon Testers @george1421
    last edited by Greg Plamondon Jan 16, 2018, 11:36 AM Jan 16, 2018, 5:36 PM

    @george1421

    10.21.40.39 is the storage node for that location.
    192.168.10.238 is the main fog server that is the management interface.

    G 1 Reply Last reply Jan 16, 2018, 5:37 PM Reply Quote 0
    • G
      george1421 Moderator @Greg Plamondon
      last edited by george1421 Jan 16, 2018, 11:38 AM Jan 16, 2018, 5:37 PM

      @greg-plamondon ok run the query I posted in red below against your fog master server.

      I did amend my previous post with the WTF comment. You have Ip addresses all over the place.

      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!

      G 1 Reply Last reply Jan 16, 2018, 5:38 PM Reply Quote 0
      • G
        Greg Plamondon Testers @george1421
        last edited by Jan 16, 2018, 5:38 PM

        @george1421
        run it from the client i am trying to image? or from any workstation?

        G 1 Reply Last reply Jan 16, 2018, 5:42 PM Reply Quote 0
        • G
          Greg Plamondon Testers
          last edited by Jan 16, 2018, 5:40 PM

          #!ipxe
          set fog-ip 192.168.10.238
          set fog-webroot fog
          set boot-url http://${fog-ip}/${fog-webroot}
          cpuid --ext 29 && set arch x86_64 || set arch i386
          goto get_console
          :console_set
          colour --rgb 0x00567a 1 ||
          colour --rgb 0x00567a 2 ||
          colour --rgb 0x00567a 4 ||
          cpair --foreground 7 --background 2 2 ||
          goto MENU
          :alt_console
          cpair --background 0 1 ||
          cpair --background 1 2 ||
          goto MENU
          :get_console
          console --picture http://10.21.40.39/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
          :MENU
          menu
          colour --rgb 0x00567a 0 ||
          cpair --foreground 1 1 ||
          cpair --foreground 0 3 ||
          cpair --foreground 4 4 ||
          item --gap Host is registered as PC3181!
          item --gap -- -------------------------------------
          item fog.local Boot from hard disk
          item fog.memtest Run Memtest86+
          item fog.keyreg Update Product Key
          item fog.deployimage Deploy Image
          item fog.multijoin Join Multicast Session
          item fog.quickdel Quick Host Deletion
          item fog.sysinfo Client System Information (Compatibility)
          item fog.iso Boot from ISO CD
          item fog.Nuke Fast wipe Hard Disk
          choose --default fog.local --timeout 5000 target && goto ${target}
          :fog.local
          chain -ar ${boot-url}/service/ipxe/grub.exe --config-file="rootnoverify (hd0);chainloader +1" || goto MENU
          :fog.memtest
          kernel http://10.21.40.39/fog/service/ipxe/memdisk initrd=http://10.21.40.39/fog/service/ipxe/memtest.bin iso raw
          initrd http://10.21.40.39/fog/service/ipxe/memtest.bin
          boot || goto MENU
          :fog.keyreg
          login
          params
          param mac0 ${net0/mac}
          param arch ${arch}
          param username ${username}
          param password ${password}
          param keyreg 1
          isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
          isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
          param sysuuid ${uuid}
          :fog.deployimage
          login
          params
          param mac0 ${net0/mac}
          param arch ${arch}
          param username ${username}
          param password ${password}
          param qihost 1
          isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
          isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
          param sysuuid ${uuid}
          :fog.multijoin
          login
          params
          param mac0 ${net0/mac}
          param arch ${arch}
          param username ${username}
          param password ${password}
          param sessionJoin 1
          isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
          isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
          param sysuuid ${uuid}
          :fog.quickdel
          login
          params
          param mac0 ${net0/mac}
          param arch ${arch}
          param username ${username}
          param password ${password}
          param delhost 1
          isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
          isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
          param sysuuid ${uuid}
          :fog.sysinfo
          kernel http://10.21.40.39/fog/service/ipxe/bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://192.168.10.238/fog/ consoleblank=0 rootfstype=ext4 storage=10.21.40.39:/images/ storageip=10.21.40.39 loglevel=4 mode=sysinfo
          imgfetch http://10.21.40.39/fog/service/ipxe/init_32.xz
          boot || goto MENU
          :fog.iso
          menu passwd 707376
          :MENU
          menu
          item --gap -- ---------------- iPXE boot menu ----------------
          item CENTOS6532 CentOS-6.5 Net Install 32BIT
          item CENTOS6564 CentOS-6.5 Net Install 64BIT
          item CENTOS7MIN64 CentOS-7.0 Minimal 64BIT
          item CENTOS7NET64 CentOS-7.0 Net Install 64BIT
          item KaliLinux Kali Linux 2016 64BIT
          item RocksCluster Rocks Cluster 64BIT
          item SpinRite6 SprinRite 6
          item return return to previous menu
          choose --default return --timeout 5000 target && goto ${target}
          :CENTOS6532
          initrd http://${fog-ip}/ISO/CentOS-6.5-i386-netinstall.iso
          chain memdisk iso raw ||
          goto MENU
          :CENTOS6564
          initrd http://${fog-ip}/ISO/CentOS-6.5-x86_64-netinstall.iso
          chain memdisk iso raw ||
          goto MENU
          :CENTOS7MIN64
          initrd http://${fog-ip}/ISO/CentOS-7.0-1406-x86_64-Minimal.iso
          chain memdisk iso raw ||
          goto MENU
          :CENTOS7NET64
          initrd http://${fog-ip}/ISO/CentOS-7.0-1406-x86_64-NetInstall.iso
          chain memdisk iso raw ||
          goto MENU
          :KaliLinux
          initrd http://${fog-ip}/ISO/kali-linux-2016.2-amd64.iso
          chain memdisk iso raw ||
          goto MENU
          :RocksCluster
          initrd http://${fog-ip}/ISO/RocksCluster.iso
          chain memdisk iso raw ||
          goto MENU
          :SpinRite6
          initrd http://${fog-ip}/ISO/SpinRite6.iso
          chain memdisk iso raw ||
          goto MENU
          :return
          chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
          prompt
          goto MENU
          autoboot
          param sysuuid ${uuid}
          :fog.Nuke
          kernel http://10.21.40.39/fog/service/ipxe/bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://192.168.10.238/fog/ consoleblank=0 rootfstype=ext4 storage=10.21.40.39:/images/ storageip=10.21.40.39 loglevel=4 capone=1 mode=wipe wipemode=fast mac=00:00:00:00:00:00
          imgfetch http://10.21.40.39/fog/service/ipxe/init_32.xz
          boot || goto MENU
          :bootme
          chain -ar http://10.21.40.39/fog/service/ipxe/boot.php##params ||
          goto MENU
          autoboot```
          1 Reply Last reply Reply Quote 0
          • G
            george1421 Moderator @Greg Plamondon
            last edited by Jan 16, 2018, 5:42 PM

            @greg-plamondon as long as you still have the job scheduled from any computer that can reach the master fog server.

            also just because your network is a bit more complex than it appears on the surface. You are sure that the 10.21.100.x subnet can physically reach the master fog server at 192.168.10.238. I’m going to say yes because we see that in the pxe booting process. But during FOS startup it has to be able to connect via http to the fog server.

            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!

            G 1 Reply Last reply Jan 16, 2018, 5:42 PM Reply Quote 0
            • G
              Greg Plamondon Testers @george1421
              last edited by Jan 16, 2018, 5:42 PM

              @george1421
              oops i canceled the job…

              G 1 Reply Last reply Jan 16, 2018, 5:46 PM Reply Quote 0
              • G
                george1421 Moderator @Greg Plamondon
                last edited by Jan 16, 2018, 5:46 PM

                @greg-plamondon if you are going to reschedule the job, tick the check box that says debug and then pxe boot the target computer. Let see if that gives us any new info.

                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!

                G 1 Reply Last reply Jan 16, 2018, 5:48 PM Reply Quote 0
                • G
                  Greg Plamondon Testers @george1421
                  last edited by george1421 Jan 16, 2018, 11:49 AM Jan 16, 2018, 5:48 PM

                  @george1421

                  #!ipxe
                  set fog-ip 192.168.10.238
                  set fog-webroot fog
                  set boot-url http://${fog-ip}/${fog-webroot}
                  kernel http://10.21.40.39/fog/service/ipxe/bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://192.168.10.238/fog/ consoleblank=0 rootfstype=ext4 mac=c0:3f:d5:9d:e9:50 ftp=10.21.40.39 storage=10.21.40.39:/images/ storageip=10.21.40.39 osid=9 irqpoll hostname=PC3181 chkdsk=0 img=Win10x64-1703-R1 imgType=n imgPartitionType=all imgid=124 imgFormat=0 PIGZ_COMP=-6 adon=1 addomain="MTSTRANS.COM" adou="" aduser="Administrator" adpass="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" isdebug=yes type=down
                  imgfetch http://10.21.40.39/fog/service/ipxe/init_32.xz
                  boot
                  
                  G 1 Reply Last reply Jan 16, 2018, 5:52 PM Reply Quote 0
                  • S
                    Sebastian Roth Moderator
                    last edited by Jan 16, 2018, 5:49 PM

                    @Greg-Plamondon Take a look at the Storage Settings in your FOG web UI. I am fairly sure you’ll find the old IP there.

                    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

                    G G 2 Replies Last reply Jan 16, 2018, 5:50 PM Reply Quote 0
                    • G
                      george1421 Moderator @Sebastian Roth
                      last edited by Jan 16, 2018, 5:50 PM

                      @sebastian-roth Am I missing something, what he just posted looks correct with a master fog server and a storage node.

                      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
                      • G
                        george1421 Moderator @Greg Plamondon
                        last edited by Jan 16, 2018, 5:52 PM

                        @greg-plamondon This looks right.

                        So a little bit more background on this. Are all target computers at this location doing this or only just this one computer?

                        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!

                        G 1 Reply Last reply Jan 16, 2018, 5:53 PM Reply Quote 0
                        • G
                          Greg Plamondon Testers @george1421
                          last edited by Jan 16, 2018, 5:53 PM

                          @george1421

                          Its doing this at all locations. I have 30 locations

                          1 Reply Last reply Reply Quote 0
                          • G
                            Greg Plamondon Testers @Sebastian Roth
                            last edited by Jan 16, 2018, 5:58 PM

                            @sebastian-roth

                            alt text

                            Sorry it took so long it takes a good 5 minutes for the page to display.

                            1 Reply Last reply Reply Quote 0
                            • S
                              Sebastian Roth Moderator
                              last edited by Sebastian Roth Jan 16, 2018, 12:05 PM Jan 16, 2018, 6:04 PM

                              @Greg-Plamondon Sorry my fault. Take a look at FOG Configurations -> FOG Settings -> Web Server -> WEB HOST…

                              And check /opt/fog/.fogsettings before running the installer 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

                              G 2 Replies Last reply Jan 16, 2018, 6:22 PM Reply Quote 0
                              • G
                                Greg Plamondon Testers @Sebastian Roth
                                last edited by Jan 16, 2018, 6:22 PM

                                @sebastian-roth

                                alt text

                                1 Reply Last reply Reply Quote 0
                                • G
                                  Greg Plamondon Testers
                                  last edited by Jan 16, 2018, 6:58 PM

                                  I have a tech @ the remote location but he will be heading to the Airport at 3PM Eastern Time. Testing will be limted after that, if anyone has a fix or suggestion please dont hesitate 😉

                                  1 Reply Last reply Reply Quote 0
                                  • G
                                    Greg Plamondon Testers
                                    last edited by Greg Plamondon Jan 16, 2018, 1:07 PM Jan 16, 2018, 7:03 PM

                                    i have backup folders:
                                    “fog_web_1.5.0-RC-9.BACKUP”
                                    "fog_web_1.4.4.BACKUP "
                                    “fog_web_1.5.0-RC-10.BACKUP”

                                    how do I roll back to this with GIT?
                                    and what one should I roll back to?

                                    1 Reply Last reply Reply Quote 0
                                    • G
                                      Greg Plamondon Testers @Sebastian Roth
                                      last edited by Jan 16, 2018, 7:39 PM

                                      @sebastian-roth
                                      If I set the “Location” to use the main management fogserver it works but I am pulling a lot of data across the wire consuming the entire circuit.

                                      W G 2 Replies Last reply Jan 17, 2018, 12:21 AM Reply Quote 0
                                      • W
                                        Wayne Workman @Greg Plamondon
                                        last edited by Jan 17, 2018, 12:21 AM

                                        @greg-plamondon I just got done skimming through this thread, I’m unsure of the problem now? Is it still DHCP related or what?

                                        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!
                                        Daily Clean Installation Results:
                                        https://fogtesting.fogproject.us/
                                        FOG Reporting:
                                        https://fog-external-reporting-results.fogproject.us/

                                        G 1 Reply Last reply Jan 17, 2018, 2:26 PM Reply Quote 0
                                        • G
                                          george1421 Moderator @Greg Plamondon
                                          last edited by george1421 Jan 16, 2018, 7:12 PM Jan 17, 2018, 1:05 AM

                                          @greg-plamondon Sorry for the delay on this, I needed some time to research this issue. I think I have a test for us to understand what is going on here.

                                          Hopefully you have a virtualization environment at one of the remote locations. Assuming you do, this is what I want to test.

                                          1. Create a new (tiny) virtual machine. This just needs to be the bare minimum, it needs to be able to pxe boot.
                                          2. Manually register that virtual machine with fog.
                                          3. Schedule a capture / deploy (doesn’t matter) but be sure to enable the debug option.
                                          4. PXE boot that target computer. It should boot to a command prompt. It may complain about the same ip address thing but it should display a bunch of commands and then drop you at a linux command prompt.
                                          5. At the linux command prompt I want you to key in the following command. set | grep web. The hope is the response will be web=http://192.168.10.238/fog/
                                          6. Now try to ping your main fog server ip address at 192.168.10.238

                                          Something should fail above. I looked at the script where its going sideways in FOS. That script is here: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/etc/init.d/S40network specifically at line 40. FOS will make a curl call back to your master FOG server to test if the link is up. FOS uses this command
                                          curl -Ikfso /dev/null "${web}"/index.php --connect-timeout 5
                                          Expanded the command is
                                          curl -Ikfso /dev/null http://192.168.10.238/fog/index.php --connect-timeout 5

                                          curl flags decoded
                                          -I Doc Info
                                          -k allow ssl connection, ignore cert
                                          -f fail silently
                                          -s silent
                                          -o output file /dev/null

                                          The other thing that could be stopping the works could be the 5 second timeout. But I would hope your fog server can respond within 5 seconds…

                                          Wait didn’t you comment it was taking a long time to call up a web page? If your master fog server is overloaded and doesn’t respond with the index.php page within 5 seconds the remote clients will give up pxe booting. The curl command calls up a web page and not just a simple ping to see if it can reach the fog server.

                                          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!

                                          G 1 Reply Last reply Jan 17, 2018, 2:17 PM Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 4
                                          • 1 / 4
                                          1 / 4
                                          • First post
                                            18/62
                                            Last post

                                          154

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project