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

TFTP Open Timeout

Scheduled Pinned Locked Moved
FOG Problems
6
31
26.8k
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
    Gavin Behrens
    last edited by Aug 17, 2013, 6:28 AM

    nothing in syslog … can you post the syslog ?

    1 Reply Last reply Reply Quote 0
    • T
      Tyler Wright
      last edited by Aug 17, 2013, 6:45 AM

      Syslog says this:

      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.0 to 10.120.100.41
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: error 0 TFTP Aborted received from 10.120.100.41
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: failed sending /tftpboot/pxelinux.0 to 10.120.100.41
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.0 to 10.120.100.41
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/c9a90b22-2b83-11dc-9346-00e01$
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/01-00-07-e9-1a-82-98 not found
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A786429 not found
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A78642 not found
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A7864 not found
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A786 not found
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A78 not found
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A7 not found
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A not found
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0 not found
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.cfg/default to 10.120.100.41
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/vesamenu.c32 to 10.120.100.41
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.cfg/default to 10.120.100.41
      Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/fog/bg.png to 10.120.100.41

      1 Reply Last reply Reply Quote 0
      • G
        Gavin Behrens
        last edited by Aug 17, 2013, 6:56 AM

        so it is proceesing the requests ok - try adding a simple task like mem test or inventory - should all work ok but to get it to boot local have a look at this [url]http://www.fogproject.org/wiki/index.php/Boot_looping_and_Chainloading[/url] - can you post the default file /tftpboot/pxelinux.cfg/default

        1 Reply Last reply Reply Quote 0
        • T
          Tyler Wright
          last edited by Aug 17, 2013, 6:59 AM

          Here is /tftpboot/pxelinux.cfg/default:

          DEFAULT vesamenu.c32
          MENU TITLE FOG Computer Cloning Solution
          MENU BACKGROUND fog/bg.png
          MENU MASTER PASSWD $1$0123456789
          \n
          menu color title 1;36;44 #ffffffff #00000000 std
          \n
          LABEL fog.local
          localboot 0
          MENU DEFAULT
          MENU LABEL Boot from hard disk
          TEXT HELP
          Boot from the local hard drive.
          If you are unsure, select this option.
          ENDTEXT
          \n
          LABEL fog.memtest
          kernel fog/memtest/memtest
          MENU LABEL Run Memtest86+
          TEXT HELP
          Run Memtest86+ on the client computer.
          ENDTEXT
          \n
          LABEL fog.reg
          MENU LABEL Quick Host Registration and Inventory
          TEXT HELP
          Automatically register the client computer,
          and perform a hardware inventory.
          ENDTEXT
          \n
          LABEL fog.reginput
          kernel fog/kernel/bzImage
          append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mode$
          MENU LABEL Perform Full Host Registration and Inventory
          TEXT HELP
          Perform a full host registration on the client
          computer, perform a hardware inventory, and
          optionally image the host.
          ENDTEXT
          \n
          LABEL fog.quickimage
          MENU PASSWD $1$0123456789
          kernel fog/kernel/bzImage
          append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
          MENU LABEL Quick Image
          TEXT HELP
          This mode will allow you to image this host quickly with
          it’s default assigned image.
          ENDTEXT
          \n
          LABEL fog.sysinfo
          kernel fog/kernel/bzImage
          append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
          MENU LABEL Client System Information
          TEXT HELP
          View basic client information such as MAC address
          and FOG compatibility.
          ENDTEXT
          LABEL fog.debug
          MENU PASSWD $1$0123456789
          kernel fog/kernel/bzImage
          append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
          MENU LABEL Debug Mode
          TEXT HELP
          Debug mode will load the boot image and load a prompt so
          you can run any commands you wish.
          ENDTEXT
          \n
          PROMPT 0
          TIMEOUT 30\n

          1 Reply Last reply Reply Quote 0
          • G
            Gavin Behrens
            last edited by Aug 17, 2013, 7:04 AM

            just try updating PXELINUX as described [url]http://www.fogproject.org/wiki/index.php/Boot_looping_and_Chainloading[/url]

            1 Reply Last reply Reply Quote 0
            • T
              Tyler Wright
              last edited by Aug 17, 2013, 7:18 AM

              I did. It had no effect.

              1 Reply Last reply Reply Quote 0
              • T
                Tyler Wright
                last edited by Aug 17, 2013, 7:21 AM

                On the subnet where I have my Fog server setup, it PXE boots just fine. On any other subnet, it will not get a DHCP address which leads it to be unable to PXE boot.

                1 Reply Last reply Reply Quote 0
                • G
                  Gavin Behrens
                  last edited by Aug 17, 2013, 7:25 AM

                  so if that subnet isn’t getting dhcp - is there a scope set on the windows box for that subnet with a pool set - is the pool exhausted ? check to see if the pool isn’t exhausted …

                  1 Reply Last reply Reply Quote 0
                  • G
                    Gavin Behrens
                    last edited by Aug 17, 2013, 7:27 AM

                    i was under the impression it was getting an ip address ??? you syslog post [B]“sent /tftpboot/fog/bg.png to 10.120.100.41” [/B]

                    right ?[B][/B]

                    1 Reply Last reply Reply Quote 0
                    • G
                      Gavin Behrens
                      last edited by Aug 17, 2013, 7:36 AM

                      also check to make sure you are able to route to your fog server …

                      1 Reply Last reply Reply Quote 0
                      • G
                        Gavin Behrens
                        last edited by Aug 17, 2013, 7:42 AM

                        firewall rules ???

                        1 Reply Last reply Reply Quote 0
                        • T
                          Tyler Wright
                          last edited by Aug 17, 2013, 12:14 PM

                          The pool is definitely not exhausted. If it boots to Windows, it gets its DHCP address.

                          Yes (to your second post).

                          In my internal network, there is no firewall whatsoever.

                          1 Reply Last reply Reply Quote 0
                          • G
                            Gavin Behrens
                            last edited by Aug 17, 2013, 1:05 PM

                            tftp on fog ok - running confirmed
                            dhcp - giving addresses options 66&67 set ok
                            routing ok
                            firewall rules (any,any) nothing should be blocked …ok
                            try from the windows box (10.120.100.x subnet right?) command prompt tftp [I]foghost[/I] get pxelinux.0 ?

                            1 Reply Last reply Reply Quote 0
                            • G
                              Gavin Behrens
                              last edited by Aug 17, 2013, 1:12 PM

                              sorry still won’t fix it anyways
                              the workstation in the pxe process isn’t being allocated an ip address but an up and running os can ?- can you post a screen shot?

                              1 Reply Last reply Reply Quote 0
                              • T
                                Tyler Wright
                                last edited by Aug 17, 2013, 3:57 PM

                                On a Windows box in the 10.110.100.x subnet, the OS pulls this from my DHCP server:

                                DHCP Enabled: Yes
                                Autoconfiguration Enabled: Yes
                                IPv4 Address: 10.110.100.92
                                Subnet Mask: 255.255.254.0
                                Default Gateway: 10.110.100.254
                                DHCP Server: 10.200.200.3

                                However, if I PXE boot, it never gets DHCP so it doesn’t continue into PXE.

                                I use to use Alitirs and it worked just fine. We had its PXE server set to “Use the DHCP port.”

                                1 Reply Last reply Reply Quote 0
                                • T
                                  Tyler Wright
                                  last edited by Aug 17, 2013, 4:03 PM

                                  Here’s something else that is interesting:

                                  When I’m booting a PC on the same subnet as my Fog server (10.200.200.203) and I choose to get IP information once I’m inside Fog, it shows that DHCP gave out the correct address.

                                  It has to be something to do with my other PCs being outside of that subnet. We divide each lab into a different subnet so there’s no way that I can really join them all together.

                                  1 Reply Last reply Reply Quote 0
                                  • T
                                    Tyler Wright
                                    last edited by Aug 17, 2013, 8:03 PM

                                    Alright, somehow, I made progress today. I can now successfully PXE boot in two out of eight labs.

                                    I’ve been attempting to upload an image and when it gets to mounting the NFS share, I get the error: Bad descriptor file and then it restarts. Once again, I’m lost.

                                    1 Reply Last reply Reply Quote 0
                                    • T
                                      Tyler Wright
                                      last edited by Aug 17, 2013, 8:38 PM

                                      I reinstalled Fog and put my DHCP server as the router’s address. This got me past the bad descriptor file error.

                                      Now, I get: “RPC remote system error connection refused.”

                                      Who knows if I’ll ever get this working. It’s just one error after another.

                                      1 Reply Last reply Reply Quote 0
                                      • W
                                        wrench1975
                                        last edited by Oct 1, 2013, 6:27 PM

                                        May Sound stupid but did you trying using

                                        sudo stop tftpd-hpa
                                        sudo start tftpd-hpa

                                        in the terminal

                                        1 Reply Last reply Reply Quote 0
                                        • L
                                          Lethal Kebab
                                          last edited by Oct 2, 2013, 12:16 PM

                                          hey guys…

                                          could possibly be unrelated… but…
                                          we were having issues with TFTP Timeout when it came to subnets other than the one fog was on… it turns out the switch needed configuration to allow spanning subnets (not sure on exact terminology but 5 minutes after the network guy worked on the core switch, it was working).

                                          the bad descriptor problem, I resolved by making sure that .mntcheck was in both the /images and in the /images/dev folder…

                                          good luck… let us know how you go…

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

                                          152

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project