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

    connection timed out chainloading failed

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    25
    4.6k
    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
      geardog @Sebastian Roth
      last edited by

      @sebastian-roth
      No adjustments have been made. I was waiting for this to play out.

      1 Reply Last reply Reply Quote 0
      • G
        geardog @Sebastian Roth
        last edited by

        @sebastian-roth

        so a montage of my poking around
        In short, after chainloading fails and I run config, there is no proxydhcp listed
        when I run dhcp net0 from shell
        I then get fog popping up in proxydhcp with the correct ip

        What does this mean?

        1.jpg
        3.jpg
        7.jpg
        8.jpg
        net0
        9.jpg
        11.jpg
        12.jpg
        net0
        13-.jpg
        proxydhcp
        15.jpg

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

          @geardog said in connection timed out chainloading failed:

          In short, after chainloading fails and I run config, there is no proxydhcp listed
          when I run dhcp net0 from shell
          I then get fog popping up in proxydhcp with the correct ip

          So it looks like proxydhcp is not set on the first round of DHCP done by iPXE. Quite strange. Could you please verify by printing the variable when you get to the iPXE shell right after chainloading fails:

          iPXE> echo ${proxydhcp/next-server}
          ...
          iPXE> dhcp net0
          ...
          iPXE> echo ${proxydhcp/next-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

          G 1 Reply Last reply Reply Quote 0
          • G
            geardog @Sebastian Roth
            last edited by geardog

            @sebastian-roth

            aye, confirmed
            20210310_145208.jpg
            sticky slash key

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

              @geardog I am at a loss on why it would not populate the proxydhcp information on the first (successful) round of DHCP. May it’s something to do with timing. We have iPXE binaries that wait for 10 seconds before it does DHCP. Find those in /tftpboot/10secdelay/ directory on your FOG server. Either modify your dnsmasq configuration to point to the iPXE binary in that subdirectory or rename the one in /tftpboot/ and copy the delay binary there for testing.

              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 1 Reply Last reply Reply Quote 0
              • G
                geardog @Sebastian Roth
                last edited by

                @sebastian-roth
                Well, I made the following edit in ltsp.conf

                
                # Set the root directory for files available via FTP.
                tftp-root=/tftpboot/10secdelay
                
                

                rebooted the fog vm
                no apparent change in behavior…
                Chainloading still fails, and shell>config output shows no proxydhcp section

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

                  @geardog Too bad. Well then the next step is to build your custom iPXE binary. Use our script as base and just change those lines:

                  :proxycheck
                  isset ${proxydhcp/next-server} && set next-server ${proxydhcp/next-server} || goto nextservercheck
                  

                  to

                  :proxycheck
                  dhcp net0
                  isset ${proxydhcp/next-server} && set next-server ${proxydhcp/next-server} || goto nextservercheck

                  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 1 Reply Last reply Reply Quote 0
                  • G
                    geardog @Sebastian Roth
                    last edited by

                    @sebastian-roth
                    What does this get me into? Will I have to recreate/replace these when I reinstall fog? I may be ham fisted, as I’ve probably reinstalled fog 15 times during my use of it. I’d like to be aware of complications in SOP, moving forward.

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

                      @geardog Yes sure, building your custom iPXE binaries needs manual steps every time you run the FOG installer.

                      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 1 Reply Last reply Reply Quote 0
                      • G
                        geardog @Sebastian Roth
                        last edited by

                        @sebastian-roth So I’m not sure what has changed, as I’ve had to focus on other things, but now it works. I didn’t follow the most recent direction, but I’m booting various boxes via pxe successfully. No idea. …

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

                        191

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project