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

    ipxe login after upgrading to latest trunk + no such file or directory

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    3
    27
    7.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.
    • ?
      A Former User @Tom Elliott
      last edited by

      @Tom-Elliott 0_1466007799051_TFTP.png

      1 Reply Last reply Reply Quote 0
      • ?
        A Former User @Wayne Workman
        last edited by

        @Wayne-Workman
        Fog serves DHCP on a separate network

        1 Reply Last reply Reply Quote 0
        • ?
          A Former User @Wayne Workman
          last edited by

          @Wayne-Workman said in ipxe login after upgrading to latest trunk + no such file or directory:

          @Cavender the ftp rename error would indicate most likely an FTP credentials issue. This article has everything you need to solve that: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

          I’ve gone through:
          cat /etc/vsftpd.conf
          sudo iptables -L
          sudo passwd fog
          /opt/fog/.fogsettings
          Interface = eth0
          FTP Path
          Permissions - set to 777 for testing
          Hide Menu is un-checked

          All looks good, though I know I’m completely missing something…just don’t currently see what it is.

          Wayne WorkmanW 1 Reply Last reply Reply Quote 0
          • Wayne WorkmanW
            Wayne Workman @A Former User
            last edited by

            @Cavender Well if all that has been set and verified, then it should be fixed. If you can upload successfully, then it’s fixed.

            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
            • ?
              A Former User @Wayne Workman
              last edited by

              @Wayne-Workman said in ipxe login after upgrading to latest trunk + no such file or directory:

              @Cavender Well if all that has been set and verified, then it should be fixed. If you can upload successfully, then it’s fixed.

              That’s why I’m stumped. Registration / Imaging still says “no such file or directory” and I still get a login prompt for the main menu.

              Wayne WorkmanW 1 Reply Last reply Reply Quote 0
              • Wayne WorkmanW
                Wayne Workman @A Former User
                last edited by

                @Cavender Well the two are separate issues. However in another thread we may be onto something… Another person is having the same issue: https://forums.fogproject.org/topic/7774/default-ipxe/2

                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
                • ?
                  A Former User @Wayne Workman
                  last edited by

                  @Wayne-Workman

                  0_1466009972639_WEB.png
                  0_1466009979805_NODE.png

                  The menu login is okay for now…just strange since that is un-checked in the web UI

                  1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User @Wayne Workman
                    last edited by

                    @Wayne-Workman said in [ipxe login after upgrading to latest trunk + no such file or directory](/topic/7763/ipxe-login-after-upgrading-

                    What boot file do you have set in DHCP?

                    subnet 172.16.0.0 netmask 255.255.255.0{
                    option subnet-mask 255.255.255.0;
                    range dynamic-bootp 172.16.0.10 172.16.0.254;
                    default-lease-time 21600;
                    max-lease-time 43200;
                    option routers 172.16.0.1;
                    option domain-name-servers 8.8.8.8;
                    next-server 172.16.0.33;
                    class “Legacy” {
                    match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00000”;
                    filename “undionly.kkpxe”;
                    }
                    class “UEFI-32-2” {
                    match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00002”;
                    filename “i386-efi/ipxe.efi”;
                    }
                    class “UEFI-32-1” {
                    match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00006”;
                    filename “i386-efi/ipxe.efi”;
                    }
                    class “UEFI-64-1” {
                    match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00007”;
                    filename “ipxe.efi”;
                    }
                    class “UEFI-64-2” {
                    match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00008”;
                    filename “ipxe.efi”;
                    }
                    class “UEFI-64-3” {
                    match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00009”;
                    filename “ipxe.efi”;

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

                      Any more information on this?

                      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
                      • Tom ElliottT
                        Tom Elliott
                        last edited by

                        Again? Anything to report for this?

                        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
                        • ?
                          A Former User @Tom Elliott
                          last edited by

                          @Tom-Elliott said in ipxe login after upgrading to latest trunk + no such file or directory:

                          Again? Anything to report for this?

                          I eventually went with a clean install of 14.04 and a new database and the problem went away. In that way it’s resolved on my end though I don’t know what was in my old database that could have caused this.

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

                          170

                          Online

                          12.1k

                          Users

                          17.3k

                          Topics

                          155.3k

                          Posts
                          Copyright © 2012-2024 FOG Project