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

Storage Node Pxe not working

Scheduled Pinned Locked Moved Unsolved
FOG Problems
6
21
10.0k
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.
  • A
    abstert @Wayne Workman
    last edited by Aug 26, 2015, 5:11 PM

    @Wayne-Workman

    Hello Wayne,

    I am aware of Tom and who he is and I greatly appreciate the work he has done with FOG as it has helped us out greatly.

    I tried the solution suggested and the PXE/TFTP services are installed, however, the client systems are still getting the error “http://10.X.X.X.X/fog/services/ipxe/boot.php no such file or directory. Could not boot ipxe.org/2d12603b” then booting into their normal HD’s OS.

    @ch3i I created a storage group for site B and added the new storage node to this new storage group. I clicked on the “Is Master Node” checkbox for Site B’s new storage node as well. I’m still getting the error mentioned above in that the host will begin the PXE boot and you can see the message about iPXE. Here is a screenshot:
    image001.jpeg

    W 1 Reply Last reply Aug 26, 2015, 5:17 PM Reply Quote 0
    • W
      Wayne Workman @abstert
      last edited by Aug 26, 2015, 5:17 PM

      @abstert To what is that an IP for? 10.63.10.107 ? is that the master storage node in your new storage group, or is that the primary FOG server?

      And what happens if you go to that address?

      http://10.63.10.107/fog/service/ipxe/boot.php

      If that IP is a storage node or the main server, can you verify this file actually exists on the server? i.e. go to the CLI of that server and go to /var/www/html/fog/service/ipxe or /var/www/fog/service/ipxe

      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/

      A 1 Reply Last reply Aug 26, 2015, 5:22 PM Reply Quote 0
      • A
        abstert @Wayne Workman
        last edited by Aug 26, 2015, 5:22 PM

        @Wayne-Workman That IP is for the site B storage node, which is now the master node for site B’s storage group. I can view the contents of the directory via CLI /var/www/html/fog/service/ipxe or /var/www/fog/service/ipxe which contain:
        advanced.php bg.png boot.php bzImage bzImage32 grub.exe init_32.xz init.xz memdisk memtest.bin

        If I go to the website http://10.63.10.107/fog/service/ipxe/boot.php there is nothing that shows up on my browser.

        W 1 Reply Last reply Aug 26, 2015, 5:30 PM Reply Quote 0
        • W
          Wayne Workman @abstert
          last edited by Aug 26, 2015, 5:30 PM

          @abstert is Apache running? it’s the httpd service on redhat systems.

          If you go to 10.63.10.107 you ought to get the Apache test page.

          Or check the status on Fedora/CentOS/RHEL with

          systemctl status httpd
          

          or on Debian/Ubuntu like this:

          service httpd status
          

          Also - see if your firewall is off or not for that 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!
          Daily Clean Installation Results:
          https://fogtesting.fogproject.us/
          FOG Reporting:
          https://fog-external-reporting-results.fogproject.us/

          A 1 Reply Last reply Aug 26, 2015, 5:44 PM Reply Quote 0
          • A
            abstert @Wayne Workman
            last edited by Aug 26, 2015, 5:44 PM

            @Wayne-Workman Apache is running:
            service httpd status
            httpd (pid 23626) is running…

            Firewall is completely disabled and turned off with no rules set.

            1 Reply Last reply Reply Quote 0
            • J
              Junkhacker Developer
              last edited by Junkhacker Aug 27, 2015, 6:49 PM Aug 27, 2015, 8:19 PM

              in the default.ipxe file on your storage node (it is a plain text file) edit the IP to be that of your primary fog server

              signature:
              Junkhacker
              We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

              A 1 Reply Last reply Sep 7, 2015, 7:28 PM Reply Quote 2
              • A
                abstert @Junkhacker
                last edited by Sep 7, 2015, 7:28 PM

                @Junkhacker
                This is what the default.ipxe has. We did modify the line beginning with “chain” to be the IP of our primary fog server and now our remote PCs can PXE boot as well as work using the registration/imaging capability of FOG.

                !ipxe
                cpuid --ext 29 && set arch x86_64 || set arch i386
                params
                param mac0 ${net0/mac}
                param arch ${arch}
                isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                :bootme
                chain http://changedthisIP/fog/service/ipxe/boot.php##params

                Can you please provide the details as to why this was the fix?

                Thanks

                1 Reply Last reply Reply Quote 1
                • J
                  Junkhacker Developer
                  last edited by Sep 8, 2015, 3:58 PM

                  for whatever reason the fog/service/ipxe/boot.php web address on your storage node wasn’t working correctly. there are a lot of reasons that might be happening (apache config problems, php config problems, db connection problems, firewalls, etc…), but if your hosts can reach the primary fog server they can just load up the one there. this url is the php file that dynamically generates the text used in the pxe boot menu

                  signature:
                  Junkhacker
                  We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                  A 1 Reply Last reply Sep 8, 2015, 9:49 PM Reply Quote 1
                  • A
                    abstert @Junkhacker
                    last edited by Sep 8, 2015, 9:49 PM

                    @Junkhacker

                    I should add that the change to the default.ipxe file took me to the “Full Registration…” menu and allowed me to run through the prompts, but would not let me image a system. It wasn’t until i copied over the /var/www/html/fog/service/ipxe file over to the storage node that I was able to successfully image a system.

                    I’m going to document the exact steps to get a storage node setup at another branch office and have it image systems locally using the storage node instead of the master fog server. I should have this up by end of week.

                    T 1 Reply Last reply Sep 8, 2015, 11:05 PM Reply Quote 1
                    • T
                      Tom Elliott @abstert
                      last edited by Sep 8, 2015, 11:05 PM

                      @abstert Are the nodes on the same version/revision as the “main server”? I ask this because all of the nodes and servers should have the files they need in the respective /var/www/fog/service/ipxe (or whatever path it really is) by default. Copying the folder from one to the other should not need to happen. What this tells me is either the nodes were not updated, or the nodes had been altered in some way.

                      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

                      A 1 Reply Last reply Sep 8, 2015, 11:49 PM Reply Quote 2
                      • A
                        abstert @Tom Elliott
                        last edited by Sep 8, 2015, 11:49 PM

                        @Tom-Elliott
                        Yes all the nodes are on the same version as the main server. They had the files/folder in the path /var/www/html/fog/service/ipxe, but the clients booting from one of the storage nodes would not display the menu until we copied over the folder from the main server. We did make some modifications to the main server’s FOG_TFTP_PXE_KERNEL so that is why I had to copy it over to the clients.

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

                        189

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project