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

    TFTP PXE File Not Found after Upgrade

    Scheduled Pinned Locked Moved
    FOG Problems
    7
    15
    5.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.
    • D
      deadturtle
      last edited by

      Been beating my head against a wall for too long on this one. Upgraded from .33b to 1.0 Everything went swimmingly until TFTP time. Specifically if I try and connect from a network computer I get:

      [CODE]TFTP.
      PXE-T01: File not found
      PXE-E3B: TFTP Error-File not found
      PXE-MOF: Exiting Intel PXE ROM[/CODE]

      I’ve update my DHCP server to say Option 67: undionly.kpxe.
      I’ve followed this [URL=‘http://fogproject.org/wiki/index.php?title=Upgrade_to_1.0.0’]Upgrade to 1.0.0[/URL] to ensure that my Fog TFTP settings are in line
      I’ve changed my fog management password to reflect the local user password, and I’ve tested FTP to ensure that I can connect via FTP

      My tftpd-hpa looks as such:
      [CODE]TFTP_USERNAME=“fog”
      TFTP_DIRECTORY=“/tftpboot”
      TFTP_ADDRESS=“10.1.2.2:69”
      TFTP_OPTIONS=“-s”[/CODE]

      If I try and connect from my desktop to the TFTP server I get:
      [CODE]F:>tftp 10.1.2.2 GET undionly.kpxe
      Timeout occurred
      Connect request failed[/CODE]

      (but I can ping, http and SSH to the server from my desk)

      I’ve ensured that TFTP-HPA is running and pointed at the right spot:

      [CODE]root 3258 0.0 0.0 14808 304 ? Ss 13:36 0:00 /usr/sbin/in.tftpd --listen --user fog --address 10.1.2.2:69 -s /tftpboot[/CODE]

      The TFTP boot folder is owned by fog:

      [CODE]drwxr-xr-x 3 fog root 4.0K 2014-05-13 11:41 tftpboot[/CODE]

      This is on Ubuntu 10. Obviously I’m missing something stupid, but I can’t figure out what.

      1 Reply Last reply Reply Quote 0
      • S
        snoopsean
        last edited by

        what are permissions on the actual undionly.kpxe file which is in the tftpboot folder?

        make sure its has read and execute for anyone. the pxe client doesnt connect as fog, it connects to the tftp service as anonymous, and the tftp service needs to be able to read the endionly.kpxe file

        1 Reply Last reply Reply Quote 0
        • D
          deadturtle
          last edited by

          I tried changing it to 777 across the board with no effect.
          -D

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

            F:>tftp 10.1.2.2 GET undionly.kpxe
            Timeout occurred
            Connect request failed

            That’s the part i’m worried about. It sounds to me like tftpd-hpa server isn’t working.

            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 0
            • W
              Wolfbane8653 Developer
              last edited by

              what happens when you do a:

              [CODE]sudo restart tftpd-hpa[/CODE]

              ???

              1 Reply Last reply Reply Quote 0
              • D
                deadturtle
                last edited by

                I’m beginning to think the issue is either with Ubuntu or with our network environment. I installed a squeaky clean empty Fog server onto Ubuntu 14. I still had 1.0.0 in my folder, but I upgraded to 1.0.1 and I am getting the exact same errors. To re-iterate out-of-the-box Ubuntu install, clean Fog install 1.0.0 -> 1.0.1 can’t TFTP from my desktop to the client, can’t PXE boot from a workstation.

                (Prevision version was Ub 10 with .33b -> 1.0.0)

                @Wolf if I restart I get: tftpd-hpa start/running, process 24585
                -D

                1 Reply Last reply Reply Quote 0
                • L
                  linuxares
                  last edited by

                  I had the same problem.

                  I installed PHPMyadmin, exported seperate SQL databases that I wanted to keep (images and host for me) and did a clean install of 1.0.1. Not a problem anymore.

                  1 Reply Last reply Reply Quote 0
                  • D
                    deadturtle
                    last edited by

                    Yeah that was my thought, but its still not working. Strangely I CAN tftp from a workstation on the same vmware host as the FOG server, but still not from my workstation

                    @TE I’ve searched google/forums pretty hard, and I’ve verified all the steps in the Wiki.

                    1 Reply Last reply Reply Quote 0
                    • D
                      deadturtle
                      last edited by

                      Ok I figured it out (Finally!) Netware 6.5 DHCP can’t/doesn’t pass the undionly.kpxe var correctly. Not sure if its because our scope is messed up, or if there is something deeper that is causing the issues… I bounced a temporary Windows DHCP server and things lit up (phew!)

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

                        [S]Is your scope options setup? Meaning, do you have options 67/66 set to point at the FOG Server IP and undionly.kpxe file?[/S]

                        Disregard!

                        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 0
                        • Jaymes DriverJ
                          Jaymes Driver Developer
                          last edited by

                          [quote=“deadturtle, post: 27096, member: 24155”]Ok I figured it out (Finally!) Netware 6.5 DHCP can’t/doesn’t pass the undionly.kpxe var correctly. Not sure if its because our scope is messed up, or if there is something deeper that is causing the issues… I bounced a temporary Windows DHCP server and things lit up (phew!)[/quote]

                          If you would have said you were Novell sooner, I would have had a suggestion for you.

                          I as well, am a Novell Network, I am not proud of it, and you must prepare to jump through many hoops.

                          To solve your issues with iPXE booting, you will want to install DNSMASQ service. Look at this guide here [url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]

                          this service offers a proxy dhcp for booting during iPXE/PXE booting and help to resolve the tftp server and the boot file name. I thought the cause of the issue was the ip address helpers and the funky way my network is laid out. Glad to know it’s Novell!

                          WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

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

                            Found out the issue you Jaymes, and deadturtle were/are having with switching to undionly.kpxe in the scope options is simply a numerical setting of the number of characters option 67 can contain. Novel 6.5 (not SP2) will not allow characters over 12 in the options field. This means (undionly.kpxe at 13 characters) does not fit the scope. So you where on the right track of having to create a symbolic link. Best suggestion I can come up with is change the name from undionly.kpxe to ipxe.kpxe. Or do so with a symbolic link.

                            Thanks to deadturtle for showing the issue and knowing about this character limitation.

                            Hope this helps.

                            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 0
                            • Jaymes DriverJ
                              Jaymes Driver Developer
                              last edited by

                              DeadTurtle, do you find that using DNSMASQ on your version of linux causes any issues with the boot file?

                              I’m using an older version of linux and that might be my entire problem, its more or less just for testing purposes anyway, but I have found that while issuing the boot command dnsmasq wants to append .0 to the file making the file either undionly.kpxe.0 or undionly.0

                              I can circumvent this issue with a symlink
                              [code]sudo ln -s undionly.kpxe undionly.0[/code]

                              but I am curious to find if there is a better way to serve the file without symlinking, and figuring out WHY dnsmasq appends said 0.

                              WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

                              1 Reply Last reply Reply Quote 0
                              • A
                                AllenP
                                last edited by

                                I don’t know if you found a solution to this but after goggling the problem for days and days. I thought to myself what could have changed between .32 and 1.2. So I looked at the boot setting in the DHCP server and saw that the file name had changed from .32 to 1.2 so make sure you check DHCP settings edit option 067. I really hope this helps someone else bc it drove me nuts. I wish that someone would big red flags and fireworks going off anything to draw more attention to the change in the file name.
                                [FONT=Ubuntu][COLOR=#444444][SIZE=14px]Open up the scope of your DHCP server and edit these settings:[/SIZE][/COLOR][/FONT]
                                [LIST]
                                []Edit option 066 and enter the IP address of your FOG server.
                                [
                                ]Edit option 067 and put a string value of[COLOR=#ff0000] undionly.kpxe[/COLOR] or undionly.kpxe.INTEL
                                [/LIST]

                                1 Reply Last reply Reply Quote 0
                                • Jaymes DriverJ
                                  Jaymes Driver Developer
                                  last edited by

                                  [quote=“AllenP, post: 41471, member: 24073”]I don’t know if you found a solution to this but after goggling the problem for days and days. I thought to myself what could have changed between .32 and 1.2. So I looked at the boot setting in the DHCP server and saw that the file name had changed from .32 to 1.2 so make sure you check DHCP settings edit option 067. I really hope this helps someone else bc it drove me nuts. I wish that someone would big red flags and fireworks going off anything to draw more attention to the change in the file name.
                                  [FONT=Ubuntu][COLOR=#444444][SIZE=14px]Open up the scope of your DHCP server and edit these settings:[/SIZE][/COLOR][/FONT]
                                  [LIST]
                                  []Edit option 066 and enter the IP address of your FOG server.
                                  [
                                  ]Edit option 067 and put a string value of[COLOR=#ff0000] undionly.kpxe[/COLOR] or undionly.kpxe.INTEL
                                  [/LIST]
                                  [/quote]

                                  Part of the installation script that tells you that you need to update your DHCP Scope.

                                  WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

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

                                  205

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project