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

After update to 1.5.3 node offline and unable to PXE boot.

Scheduled Pinned Locked Moved Solved
Windows Problems
5
17
1.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.
  • S
    Sebastian Roth Moderator
    last edited by Sebastian Roth Jun 11, 2018, 10:28 PM Jun 12, 2018, 4:28 AM

    @Snaggel Please be more specific to where or how exactly clients fail to PXE boot. There are several different cases how PXE can fail and they all have different reasons. Best if you can take a picture of the error(s) on screen and post here.

    As well follow Wayne’s advise and update to 1.5.4.

    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
    • S
      Snaggel
      last edited by Jun 13, 2018, 1:26 PM

      I will update to 1.5.4 and see if im able to see node offline anymore and if im able to PXE boot. as of now there is no errors. it sees the media using ipV4 then gives me three option f1 to retry and f2 to boot into setup. and i forgot what the third one said. thats all that is happening. i can ping back and forth from server to client.

      1 Reply Last reply Reply Quote 0
      • S
        Snaggel
        last edited by Jun 13, 2018, 8:05 PM

        I upgraded and still have the same error. when booting into PXE it fails no errors. It just takes me to a menu to reboot into boot menu or bios setup or run onboard diagnostics? i even tried running through a dumb switch still get nothing.

        1 Reply Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Jun 13, 2018, 8:43 PM

          @snaggel said in After update to 1.5.3 node offline and unable to PXE boot.:

          I upgraded and still have the same error.

          Which error exactly is it?? Please take a picture and post here.

          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
          • S
            Snaggel
            last edited by Jun 14, 2018, 5:08 PM

            the error is the image already posted. I’m also unable to PXE to the fog server. when the Pxe boot starts i get this. wow when i took the pic i was actual able to get the error i was unable to see it before. here it is. Looks like my PXE file has O bytes. should i just add this again?
            0_1528995960698_fog error.jpg
            After that i get this.
            0_1528996108629_fog error 2.jpg

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Jun 14, 2018, 6:01 PM

              @Snaggel I think we need to take a look at the network packets being transfered when this issue is happening. Follow the instructions here: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

              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
              • S
                Snaggel
                last edited by Jun 19, 2018, 5:59 PM

                ok here is the PCAP.0_1529431172975_output619.pcap

                G 1 Reply Last reply Jun 19, 2018, 6:32 PM Reply Quote 0
                • G
                  george1421 Moderator @Snaggel
                  last edited by george1421 Jun 19, 2018, 12:33 PM Jun 19, 2018, 6:32 PM

                  @snaggel Looking at you pcap from I see the client asking for the size 10.10.61.254 for a file size. BTW all 3 dhcp servers give this system as your boot server. But I don’t see a response from that host. Is that IP your fog server?

                  The reset of the dhcp process looks good. The process just falls down at the request tftp file from 10.10.61.254. Typically you should see the request for file size, then the tftp server should respond, then the client should ask for the file. We are not seeing that in your pcap.

                  On a side note I do see dhcp servers responding to the initial discover packet [10.10.60.11, 10.10.60.240, and 10.10.60.248]. This is not abnormal, just a little uncommon.

                  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
                  • S
                    Sebastian Roth Moderator
                    last edited by Jun 20, 2018, 6:00 PM

                    @Snaggel Reviewing the PCAP and your pictures I saw that it says NBP filesize is 0 bytes…
                    I read that this can be caused by many different things that seem to be kind of unrelated on first sight. Search the web for the message and you will find many things. But I would start with the obvious: run ls -al /tftpboot/ipxe.efi on your FOG server to see if the binary has been populated properly.

                    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
                    • S
                      Snaggel
                      last edited by Jun 20, 2018, 8:28 PM

                      yes the 10.10.61.254 is my fog server. i will run the command and let you know.

                      1 Reply Last reply Reply Quote 0
                      • S
                        Snaggel
                        last edited by Jun 21, 2018, 11:30 AM

                        i ran that command the was no such file or directory. however there is one for /tftpboot/ipxe.efi

                        G 1 Reply Last reply Jun 21, 2018, 11:46 AM Reply Quote 0
                        • G
                          george1421 Moderator @Snaggel
                          last edited by Jun 21, 2018, 11:46 AM

                          @snaggel said in After update to 1.5.3 node offline and unable to PXE boot.:

                          i ran that command the was no such file or directory. however there is one for /tftpboot/ipxe.efi

                          @Sebastian-Roth said in After update to 1.5.3 node offline and unable to PXE boot.:

                          I would start with the obvious: run ls -al /tftpboot/ipxe.efi on your FOG server to see if the binary has been populated properly

                          What am I missing here?? Sebastian’s command should have listed that file out and its file size.

                          As a test if you install the tftp client feature in windows, you can test download that file to your windows computer via command line too. The command would be something like tftp <fog_server_ip> get ipxe.efi . to transfer the ipxe.efi boot file to your computer. We are only interested in knowing if the file is transferred or not.

                          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 1
                          • S
                            Snaggel
                            last edited by Jun 21, 2018, 4:09 PM

                            so this is what happened when i ran the commands on the fog server.0_1529597253104_IPXE-FOG server.PNG

                            Here is what happened on a windows client trying to download the file from my fog server.
                            0_1529597305035_windows client.PNG

                            I can Ping back and forth fine.

                            1 Reply Last reply Reply Quote 0
                            • T
                              Tom Elliott
                              last edited by Jun 21, 2018, 4:44 PM

                              @snaggel have you ensured selinux is set to permissive or disabled? Firewalls similarly?

                              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 1
                              • S
                                Snaggel
                                last edited by Jun 25, 2018, 2:37 PM

                                @tom-elliott said in After update to 1.5.3 node offline and unable to PXE boot.:

                                selinux is set to permissive or disabled

                                well that was it. it was disabled before never thought of looking at that. i turned it to permissive mode. i was able to boot to my fog Server. we had a power outage it must of defaulted back to enforcing. thanks appreciate it.

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

                                251

                                Online

                                12.1k

                                Users

                                17.3k

                                Topics

                                155.3k

                                Posts
                                Copyright © 2012-2024 FOG Project