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

    Default.IPXE...no such file or directory

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    14
    5.9k
    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.
    • P
      pencils
      last edited by

      0_1476358897557_Capture.PNG

      that…

      1 Reply Last reply Reply Quote 0
      • P
        pencils
        last edited by

        and yes. the IP address is …133

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

          @pencils well indeed default.ipxe is missing, why? All of the other stuff appears to be there? This is very strange.

          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!

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

            @george1421 while I don’t recommend this, because that file missing tells me something else is going on here that we are not aware of and that is a concern. You could recreate that file. Its just a text file with the permissions of 755.

            #!ipxe
            cpuid --ext 29 && set arch x86_64 || set arch i386
            params
            param mac0 ${net0/mac}
            param arch ${arch}
            param platform ${platform}
            param product ${product}
            param manufacturer ${product}
            param ipxever ${version}
            param filename ${filename}
            isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
            isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
            :bootme
            chain http://192.168.1.133/fog/service/ipxe/boot.php##params
            

            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
            • P
              pencils
              last edited by

              is the path relative. I guess i have to put the file in the folder /tftboot. But on the pxe screen its looking for the file in /IPSERVER/filename?

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

                @pencils yes it is relative. The tftp files are downloaded from /tftpboot that is the root of the tftp path.

                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
                • P
                  pencils
                  last edited by

                  THANK YOU THANK YOU!!

                  Finally got it to work!!

                  Cant wait to use it with gusto!

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

                    It blows my mind how default.ipxe would just be missing. Perhaps we need more validation in the installer?

                    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/

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

                      @Wayne-Workman Nope. Validation wasn’t the issue. Something else was edited which broke it. I’m nearly certain of it.

                      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

                      P 1 Reply Last reply Reply Quote 3
                      • P
                        pencils @Tom Elliott
                        last edited by

                        @Tom-Elliott I had edited one conf file. But at the very start from the initial install the DIR structure wasnt correct. EG the TFTPROOT/TFTPBOOT didnt exist where is should have been?

                        Nothing was changed at the point of install. And i re-installed Ubuntu 16.04 and FOG 1.3 several times with the same results.

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

                          @pencils Get a new copy of Ubuntu, because something is wrong with yours.

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

                          130

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project