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

    MAC format invalid & other MAC issues

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    mac
    4
    19
    6.4k
    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
      AustinR
      last edited by

      Hi, The error log is pretty short, I verified that Bootfile in DHCP was set to undionly.klpxe. This had not changed. I had a function FOG server setup for over a year however the VM it was hosted on died. I found out later that we had no backup. live and learn i supose…
      [Sun Sep 20 03:21:01.991263 2015] [auth_digest:notice] [pid 837] AH01757: generating secret for digest authentication …
      [Sun Sep 20 03:21:01.992304 2015] [lbmethod_heartbeat:notice] [pid 837] AH02282: No slotmem from mod_heartmonitor
      [Sun Sep 20 03:21:01.992342 2015] [ssl:warn] [pid 837] AH01882: Init: this version of mod_ssl was compiled against a newer library (OpenSSL 1.0.1k 8 Jan 2015, version currently loaded is OpenSSL 1.0.1j-fips 15 Oct 2014) - may result in undefined or erroneous behavior
      [Sun Sep 20 03:21:02.085664 2015] [mpm_prefork:notice] [pid 837] AH00163: Apache/2.4.16 (Fedora) OpenSSL/1.0.1j-fips PHP/5.6.13 configured – resuming normal operations
      [Sun Sep 20 03:21:02.085754 2015] [core:notice] [pid 837] AH00094: Command line: ‘/usr/sbin/httpd -D FOREGROUND’
      [Sun Sep 20 03:21:02.097933 2015] [:error] [pid 15812] avahi_entry_group_add_service_strlst(“10.1.9.9”) failed: Invalid host name
      [Sun Sep 20 03:21:02.100265 2015] [:error] [pid 15812] avahi_entry_group_add_service_strlst(“10.1.9.9”) failed: Invalid host name

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

        Good morning, It would seem that the fog server is in fact partially working. I by chance had an optiplex 7010 boot into the imaging selection menu. It would seem that the HP Z230 and the older dell inspiron with a yukon chipset still can not boot. They both timeout at tftp://10.1.9.9/defualt.kpxe. The DHCP server is still set to use undionly.kkpxe so i’m a bit confused as to why its trying to use the default.kpxe.

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

          @AustinR

          Can you run this command on the FOG server and provide the results?
          find / | grep default.kpxe

          Also look at this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP

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

            Here is the output, also i was able to successfully grab an image from the z230 i was working on It failed but at least the registration portion is working. The issues are now only with the inspiron laptops and a the surface pro’s we purchased. I’m not to concerned about the surface as i couldn’t get them to work properly in the prior version either.
            Wayne, sorry about not responding to the IM, somehow the avatar circle was placed under the new post button and i literally just realized it was there.

            /var/www/html/fog/service/ipxe/default.kpxe
            /opt/fog_trunk/packages/tftp/default.kpxe
            [root@Fogsrv01 ~]#
            [root@Fogsrv01 ~]# /var/www/html/fog/service/ipxe/default.kpxe
            -bash: /var/www/html/fog/service/ipxe/default.kpxe: Permission denied
            [root@Fogsrv01 ~]# /opt/fog_trunk/packages/tftp/default.kpxe
            -bash: /opt/fog_trunk/packages/tftp/default.kpxe: cannot execute binary file: Exec format error

            Wayne WorkmanW 2 Replies Last reply Reply Quote 0
            • Wayne WorkmanW
              Wayne Workman @AustinR
              last edited by

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • Wayne WorkmanW
                Wayne Workman @AustinR
                last edited by Wayne Workman

                @AustinR That’s interesting because I’m on FOG Trunk just as you are, but I cannot find any such file called default.kpxe on my FOG server.

                Look into “FOG Configuration” and tell us what kernel it says it’s using.

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

                  FOG Configuration
                  FOG Version Information
                  Version: 4704

                  Kernel Versions
                  DefaultMember
                  bzImage Version: 4.2.0
                  bzImage32 Version: 4.2.0

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

                    @AustinR

                    So… DHCP… and DHCP Scopes - and DHCP Global settings… somewhere or another you likely have default.kpxe set as option 067.

                    I’ve seen situations in organizations that have the correct settings set lower in the DHCP scope for a site, but a global setting simply overrides it. Please double check if this is the case.

                    Also - do you have dual DHCP servers or redundant DHCP servers? Are you sure DHCP is not running on the FOG server? Is dnsmasq or CrucibleWDS ProxyDHCP running anywhere? Do you have an active WDS Server on your network?

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      AustinR @Wayne Workman
                      last edited by

                      @Wayne-Workman , I just verified that the only scope using 66,67 is the 10.1.12.x that workstations get their IP’s from. Is there a log created during the pxe startup on the client machine ? i see something flash by but to fast to see what it says, its only these few machines now. The Optiplex 9020,7010 and the HP z230 are all booting and exiting properly now. honestly we don’t have very many of the others left. I think i’ll just move on. I appreciate all the help you provided.

                      Thank you.

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

                        @AustinR, there is no such file as default.kpxe presented to any of our underlying code. If you have edited the file to get default.kpxe, maybe this is the issue altogether?

                        If you mean default.ipxe which is stored it /tftpboot, all this file is is a text file that is telling the ipxe (undionly.kpxe) what to look for. What I’d recommend is changing from the bootfile undionly.kpxe to undionly.kkpxe.

                        Then I again I am still kind of lost on what this thread is about, so forgive my misunderstanding. If I understand it correctly, some systems are booting fine, while others are hanging or erroring out. My best guess is this is due to the bootfile and I’d start by trying the undionly.kkpxe. If this still doesn’t work, at least we know we’re heading somewhere.

                        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

                        A 1 Reply Last reply Reply Quote 1
                        • A
                          AustinR @Tom Elliott
                          last edited by

                          @Tom-Elliott looks like it is .ipxe that is showing up, I had to record a video and play it back to see it. Yes the thread has moved in the direction of some machines are booting and others aren’t. It was originally a thread about none of the machines being able to register due to a MAC issue.
                          I’ll change the boot file to .kkpxe and see if that works with the machines that won’t boot.

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

                          237

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project