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

IPXE Issues

Scheduled Pinned Locked Moved
FOG Problems
5
15
2.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.
  • J
    Junkhacker Developer
    last edited by Junkhacker May 18, 2017, 8:56 AM May 18, 2017, 2:52 PM

    first thing i’m going to recommend is that you upgrade to fog version 1.4.0. so many many things have been fixed or improved.

    have you migrated your images and database info from the old server to the new? if you get the new server working, will you need the old one at all?

    quick and dumb solution for a lot of your issues: put a copy of the default.ipxe file from the new server in the /tftpboot folder of your FOG 0.32 server so that it can always be found and loaded. that file just loads the next file from http. it doesn’t technically need to be on the new server.

    oh, and btw, your images didn’t load

    signature:
    Junkhacker
    We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

    1 Reply Last reply Reply Quote 0
    • Q
      Quazz Moderator
      last edited by May 18, 2017, 3:01 PM

      Does your FOG server also function as DHCP server?

      1 Reply Last reply Reply Quote 0
      • J
        jaoyer
        last edited by jaoyer May 18, 2017, 9:29 AM May 18, 2017, 3:27 PM

        Sorry, should have included that. One of our Windows servers handle dhcp.

        I tried to update to 1.40 and it went through most of the installation ok, but it failed at the very end connecting to the database and then the webui wouldn’t load (The page isn’t working. Currently unable to handle this request. HTTP ERROR 500). I was reading about php5 vs php7 and assumed there was something in the upgrade from 5 to 7 that caused the webui not to work. I took a snapshot of our server before upgrading so was able to rollback to 1.30RC 10.

        That was going to be my next issue that I was going to post. Just for kicks and grins I created a brand new Fog Server and installed 1.40. The install went fine, the webpage loaded , but I still had the same issue booting to default.ipxe with the undionly.kpxe boot file.

        I have not migrated all of our images and database yet. That is on my list of things to do this summer. I wanted to get the new server working first. Once I get this working, I do not believe we would need the old server.

        Sorry about the images. I can see them in my post, but I am not sure how to make them show up for everyone else. Here are links to them. Can you see these?

        Picture 1: Failing using the old server address
        https://lh4.googleusercontent.com/v8XwHa7EvGmlAc-9NqToHtVtsfdfcbDoKR-Q-y0feAsv0D-ahsZHipQqqP77P5y2BJ1WeycTgJyMFs4SpaqKDG64f-YfxHhxPAY6=w1920-h941-rw

        Picture 2: Failing with undionly.kpxe.INTEL with 5 “dots”
        https://lh5.googleusercontent.com/iJWYg7W-TOIvJDVcCRDWuGBFcQRXxDrxpyFf3WfgxGJxiZl8cVd-PVGSSLde3PSz15sHYOZeq9DhzT4z6YIFs-n0YsobzVgoISkH=w1920-h941-rw

        Picture 3: Working undionly.kpxe.INTEL
        https://lh5.googleusercontent.com/TepDSUE2fgfP3X-73oCdM3RhF9frvxi32xkRI1vTmAzG7ocUjHEeuBxYnjeEEp0PiJ3vTeoVdWs9wEHFSDy4OQRZOoG2fFnMnNba=w1920-h941-rw

        I will try copying the default.ipxe file to the old server this afternoon and report back.

        Thanks!

        J 1 Reply Last reply May 18, 2017, 3:31 PM Reply Quote 0
        • J
          Junkhacker Developer @jaoyer
          last edited by May 18, 2017, 3:31 PM

          @jaoyer

          Your client does not have permission to get URL /v8XwHa7EvGmlAc-9NqToHtVtsfdfcbDoKR-Q-y0feAsv0D-ahsZHipQqqP77P5y2BJ1WeycTgJyMFs4SpaqKDG64f-YfxHhxPAY6=w1920-h941-rw from this server.(Client IP address: <retracted>)
          
          Forbidden That’s all we know. 
          

          signature:
          Junkhacker
          We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

          J 1 Reply Last reply May 18, 2017, 4:36 PM Reply Quote 0
          • J
            jaoyer @Junkhacker
            last edited by May 18, 2017, 4:36 PM

            @Junkhacker

            3rd time’s the charm…try these:

            Picture 1: Failing using the old server address
            https://drive.google.com/open?id=0B6yrqHh_joc2d20tWEZzdWcwMVBhckk4V1dZb0Z4MlVvMkpr

            Picture 2: Failing with undionly.kpxe.INTEL with 5 “dots”
            https://drive.google.com/file/d/0B6yrqHh_joc2aENyMnJtRE16aFE/view?usp=sharing

            Picture 3: Working undionly.kpxe.INTEL
            https://drive.google.com/open?id=0B6yrqHh_joc2WnBhWUdEemFIQVNqZ1dybzk4RTlOeFFmSENn

            J 1 Reply Last reply May 18, 2017, 4:40 PM Reply Quote 0
            • J
              Junkhacker Developer @jaoyer
              last edited by May 18, 2017, 4:40 PM

              @jaoyer those worked. any luck with default.ipxe?

              signature:
              Junkhacker
              We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

              J 1 Reply Last reply May 18, 2017, 5:11 PM Reply Quote 0
              • J
                jaoyer @Junkhacker
                last edited by May 18, 2017, 5:11 PM

                @Junkhacker

                Copying the file over has worked consistently the last 5 times I booted a test machine, so I am fairly certain that that works. However, I am still concerned why it is pointing at the old server. It is my intention to decommission our old server at some point, and am afraid that it will still look to the old server for the default.ipxe file. To test this, I took our old fog server down so that it was completely shut off and booted my test machine . It was still looking for the the default.ipxe file on our old server even though it was down and it eventually timed out.

                https://drive.google.com/open?id=0B6yrqHh_joc2bWdYWkZobTlHSmV3TXQyNk9IcklnRG5YLTZv

                Is there any cache or anything that I have to clear out on our switches?

                How does the “next-server” part of the script work? Is it something as simple as giving the new server an address that comes before the old server?

                J 1 Reply Last reply May 18, 2017, 5:25 PM Reply Quote 0
                • J
                  Junkhacker Developer @jaoyer
                  last edited by May 18, 2017, 5:25 PM

                  @jaoyer whatever is serving out options 66/67 dhcp options is providing the next-server address.

                  signature:
                  Junkhacker
                  We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                  1 Reply Last reply Reply Quote 0
                  • T
                    Tom Elliott
                    last edited by May 18, 2017, 5:53 PM

                    So option 66/67 of the DHCP server are set to point at the New fog server?

                    The Old fogserver’s IP Address in the 66 option would cause the problem. YOu would need to update the option 66 to point at the new fog server.

                    What’s the contents of:

                    cat /tftpboot/default.ipxe
                    

                    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

                    J 1 Reply Last reply May 18, 2017, 6:03 PM Reply Quote 0
                    • J
                      jaoyer @Tom Elliott
                      last edited by May 18, 2017, 6:03 PM

                      @Tom-Elliott

                      Option 66 is set to the new server
                      Option 67 I have set to either undionly.kpxe or undionly.kpxe.INTEL (I’ve tested both).

                      0_1495130576562_dhcp capture.JPG
                      Cat returns:

                      #!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://10.40.22.67/fog/service/ipxe/boot.php##params

                      T 1 Reply Last reply May 18, 2017, 6:04 PM Reply Quote 0
                      • T
                        Tom Elliott @jaoyer
                        last edited by May 18, 2017, 6:04 PM

                        @jaoyer So is that the global options for options 66/67? Is it possible your lan is using “scoped” options to point lans where to get their options 66/67?

                        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

                        J 1 Reply Last reply May 18, 2017, 6:24 PM Reply Quote 0
                        • J
                          jaoyer @Tom Elliott
                          last edited by May 18, 2017, 6:24 PM

                          @Tom-Elliott

                          I think that fixed it. I do have split scope dhcp setup on two servers, and only changed the options on one of them. I changed them in both and it seems to be working fine now.

                          Feel free to call me an idiot 😄

                          As far as the updating issue going from 1.30RC10 to 1.40 (detailed in my 2nd response), should I create new thread?

                          T W 2 Replies Last reply May 18, 2017, 7:02 PM Reply Quote 1
                          • T
                            Tom Elliott @jaoyer
                            last edited by May 18, 2017, 7:02 PM

                            @jaoyer Did you run the installer as sudo ./installfog.sh?

                            I might suggest rerunning the installer after gaining root first through sudo -i

                            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
                              Wayne Workman @jaoyer
                              last edited by May 19, 2017, 2:44 AM

                              @jaoyer said in IPXE Issues:

                              As far as the updating issue going from 1.30RC10 to 1.40 (detailed in my 2nd response), should I create new thread?

                              Yes.

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

                              137

                              Online

                              12.1k

                              Users

                              17.3k

                              Topics

                              155.3k

                              Posts
                              Copyright © 2012-2024 FOG Project