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

connection timed out chainloading failed

Scheduled Pinned Locked Moved
FOG Problems
3
25
4.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 Mar 3, 2021, 5:01 PM

    @geardog Interesting that Nick doesn’t see the next server filed being populated. I am wondering if it’s just something tcpdump doesn’t print on the console? So can you please run tcpdump -i enp5s0 port 67 or port 68 -e -n -vv (maybe need a different network interface name) on your clearOS while PXE booting a machine? Post output here so we can all compare to what Nick posted in the other forum.

    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 Mar 3, 2021, 5:53 PM Reply Quote 0
    • G
      geardog @Sebastian Roth
      last edited by geardog Mar 3, 2021, 11:56 AM Mar 3, 2021, 5:53 PM

      @sebastian-roth said in connection timed out chainloading failed:

      tcpdump -i enp5s0 port 67 or port 68 -e -n -vv

      No mention of next server.

      [root@Clear0 etc]# tcpdump -i enp17s0f0 port 67 or port 68 -e -n -vv
      tcpdump: listening on enp17s0f0, link-type EN10MB (Ethernet), capture size 262144 bytes
      11:24:14.566873 1c:6f:65:83:a0:95 > Broadcast, ethertype IPv4 (0x0800), length 590: (tos 0x0, ttl 20, id 1, offset 0, flags [none], proto                                                                                                    UDP (17), length 576)
          0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 1c:6f:65:83:a0:95, length 548, xid 0x6783a095, secs 8,                                                                                                    Flags [Broadcast] (0x8000)
                Client-Ethernet-Address 1c:6f:65:83:a0:95
                Vendor-rfc1048 Extensions
                  Magic Cookie 0x63825363
                  DHCP-Message Option 53, length 1: Discover
                  Parameter-Request Option 55, length 36:
                    Subnet-Mask, Time-Zone, Default-Gateway, Time-Server
                    IEN-Name-Server, Domain-Name-Server, RL, Hostname
                    BS, Domain-Name, SS, RP
                    EP, RSZ, TTL, BR
                    YD, YS, NTP, Vendor-Option
                    Requested-IP, Lease-Time, Server-ID, RN
                    RB, Vendor-Class, TFTP, BF
                    Option 128, Option 129, Option 130, Option 131
                    Option 132, Option 133, Option 134, Option 135
                  MSZ Option 57, length 2: 1260
                  GUID Option 97, length 17: 0.49.67.54.70.54.53.56.51.65.48.57.53.255.255.255.255
                  ARCH Option 93, length 2: 0
                  NDI Option 94, length 3: 1.2.1
                  Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
      11:24:14.567192 00:15:17:c4:a9:92 > Broadcast, ethertype IPv4 (0x0800), length 366: (tos 0xc0, ttl 64, id 2182, offset 0, flags [none], pr                                                                                                   oto UDP (17), length 352)
          172.17.17.1.bootps > 255.255.255.255.bootpc: [bad udp cksum 0xbe6f -> 0x1006!] BOOTP/DHCP, Reply, length 324, xid 0x6783a095, secs 8,                                                                                                    Flags [Broadcast] (0x8000)
                Your-IP 172.17.17.191
                Server-IP 172.17.17.1
                Client-Ethernet-Address 1c:6f:65:83:a0:95
                Vendor-rfc1048 Extensions
                  Magic Cookie 0x63825363
                  DHCP-Message Option 53, length 1: Offer
                  Server-ID Option 54, length 4: 172.17.17.1
                  Lease-Time Option 51, length 4: 43200
                  RN Option 58, length 4: 21600
                  RB Option 59, length 4: 37800
                  Domain-Name Option 15, length 22: "xxx"
                  Domain-Name-Server Option 6, length 12: 172.17.17.16,172.17.17.17,172.17.17.1
                  Default-Gateway Option 3, length 4: 172.17.17.1
                  BR Option 28, length 4: 172.17.17.255
                  Subnet-Mask Option 1, length 4: 255.255.255.0
      11:24:14.574606 00:15:5d:02:0a:16 > Broadcast, ethertype IPv4 (0x0800), length 374: (tos 0xc0, ttl 64, id 10347, offset 0, flags [none], p                                                                                                   roto UDP (17), length 360)
          172.17.17.82.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 332, xid 0x6783a095, secs 8, Flags [Broadcast] (0                                                                                                   x8000)
                Server-IP 172.17.17.82
                Client-Ethernet-Address 1c:6f:65:83:a0:95
                file "undionly.kpxe"[|bootp]
      11:24:14.575555 00:15:5d:02:0a:16 > Broadcast, ethertype IPv4 (0x0800), length 374: (tos 0xc0, ttl 64, id 10348, offset 0, flags [none], p                                                                                                   roto UDP (17), length 360)
          172.17.17.82.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 332, xid 0x6783a095, secs 8, Flags [Broadcast] (0                                                                                                   x8000)
                Server-IP 172.17.17.82
                Client-Ethernet-Address 1c:6f:65:83:a0:95
                file "undionly.kpxe"[|bootp]
      11:24:22.585346 1c:6f:65:83:a0:95 > Broadcast, ethertype IPv4 (0x0800), length 590: (tos 0x0, ttl 20, id 2, offset 0, flags [none], proto                                                                                                    UDP (17), length 576)
      
      
      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by Mar 4, 2021, 1:46 PM

        @geardog said in connection timed out chainloading failed:

        No mention of next server.

        So I would expect tcpdump to just not print it on the direct verbose text output. We did see it in the PCAP file. Or you have played with things so much that clearOS doesn’t send it anymore. But then I would expect the PXE boot to work just fine (with dnsmasq on the FOG 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 2 Replies Last reply Mar 4, 2021, 2:06 PM Reply Quote 0
        • G
          geardog @Sebastian Roth
          last edited by Mar 4, 2021, 2:06 PM

          @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 Mar 10, 2021, 6:24 PM

            @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 Mar 10, 2021, 8:24 PM

              @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 Mar 10, 2021, 8:55 PM Reply Quote 0
              • G
                geardog @Sebastian Roth
                last edited by geardog Mar 10, 2021, 2:56 PM Mar 10, 2021, 8:55 PM

                @sebastian-roth

                aye, confirmed
                20210310_145208.jpg
                sticky slash key

                1 Reply Last reply Reply Quote 0
                • S
                  Sebastian Roth Moderator
                  last edited by Mar 11, 2021, 10:40 AM

                  @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 Mar 11, 2021, 4:15 PM Reply Quote 0
                  • G
                    geardog @Sebastian Roth
                    last edited by Mar 11, 2021, 4:15 PM

                    @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 Mar 11, 2021, 8:24 PM

                      @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 Mar 30, 2021, 2:28 PM Reply Quote 0
                      • G
                        geardog @Sebastian Roth
                        last edited by Mar 30, 2021, 2:28 PM

                        @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 Apr 1, 2021, 8:52 AM

                          @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 Apr 7, 2021, 9:14 PM Reply Quote 0
                          • G
                            geardog @Sebastian Roth
                            last edited by Apr 7, 2021, 9:14 PM

                            @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

                            156

                            Online

                            12.0k

                            Users

                            17.3k

                            Topics

                            155.2k

                            Posts
                            Copyright © 2012-2024 FOG Project