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

    iPXE timeout after upgrade to trunk

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    6
    11
    4.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.
    • T
      templink
      last edited by

      OK self-resolved.
      I modified /tftpboot/default.ipxe and restarted tftpd-hpa service
      it’s working now

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

        I’m a bit confused on your current setup. Your FOG server IS 192.168.1.1? Where does 192.168.1.207 come into play? It looks like your target computer thinks the fog server is there.

        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
        • george1421G
          george1421 Moderator @templink
          last edited by george1421

          @templink said:

          OK self-resolved.
          I modified /tftpboot/default.ipxe and restarted tftpd-hpa service
          it’s working now

          While its working I wonder how many pains it will give you the next time you upgrade your FOG server. There is a setting inside the FOG management console you need to update. Its in the FOG settings section that has the wrong IP address.

          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!

          T 1 Reply Last reply Reply Quote 1
          • T
            templink @george1421
            last edited by

            @george1421

            thx i’ll look there.
            My FOG server is a laptop with 2 IPs: (eth1 192.168.1.1 static) and (wlan 192.168.1.207 dhcp)

            I checked the settings in FOG web GUI, they appear correct for TFTP server IP. = 192.168.1.1

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

              @templink This may be a place to start: https://forums.fogproject.org/topic/6348/wrong-ip-on-pxe-boot/9

              But I though there was a variable in that file and not hard coded, so I may be a bit confused on this. I’ll have to power on my dev box and see if there is a static value in there.

              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!

              Wayne WorkmanW 1 Reply Last reply Reply Quote 0
              • JunkhackerJ
                Junkhacker Developer
                last edited by Junkhacker

                default.ipxe is hard coded because the file is retrieved over tftp and cannot be easily generated on request. it’s value is based on answers given during install, or retrieved from the file .fogsettings in /opt/fog/ that is used for upgrade installs. it is here that you should edit ipaddress= setting to prevent the default.ipxe file from being incorrect after future installs.

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

                1 Reply Last reply Reply Quote 1
                • Wayne WorkmanW
                  Wayne Workman @george1421
                  last edited by

                  @george1421 said:

                  But I though there was a variable in that file and not hard coded

                  I think that’s the only place it’s hard coded. The installer builds the file.

                  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/

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

                    That was my bad sorry im an idiot sometimes.

                    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

                    E 1 Reply Last reply Reply Quote 0
                    • E
                      EAHarvey @Tom Elliott
                      last edited by

                      @Tom-Elliott lol Tom.

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

                        I’ve solved the thread.

                        The timeout was because this system is on an isolated network.

                        The isolated network IP is 192.168.1.1, but the wifi lan is set to 192.168.1.207 (which gives the device internet for upgraded/updating).

                        To enable the installation to operate, I changed the IP address to 192.168.1.207 as the DB settings were already set.

                        This ipaddress was used to generate the default.ipxe file which was what was causing the problem and I over looked it.

                        Sorry 😞

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

                        237

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project