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

Kernel for Ubuntu 64 bit

Scheduled Pinned Locked Moved Solved
FOG Problems
6
78
50.3k
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.
  • W
    Wayne Workman @Tom
    last edited by Feb 10, 2016, 3:07 PM

    @Tom said:

    I have 2 domain controllers in one subnet providing DHCP to workstations (70/30 rule)

    that rule will cause clients to sometimes not get an IP.

    70/30 means 70% of your available range is given out by one server, 30% by the other.

    However, the load is 50/50. Both DHCP servers hear all DHCP Discoveries, both attempt to hand out an address. Whichever one is first wins normally unless you have one set as authoritative (which nobody does it seems).

    When the one that has 30% of the range assigned to it runs out of available addresses, it’ll respond to clients that no addresses are available and the client will then auto-configure with APIPA.

    Anything other than 50/50 is almost always not a good idea - and is easy to mess up and break.

    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/

    T 1 Reply Last reply Feb 10, 2016, 3:24 PM Reply Quote 0
    • M
      MRCUR Testers @Tom
      last edited by MRCUR Feb 10, 2016, 9:13 AM Feb 10, 2016, 3:11 PM

      @Tom If you’re going to run multiple DHCP servers (I assume you’re trying to get some HA out of it), then you really should be using the built in DHCP Failover setup that Windows provides. It’s far easier to manage than what you’ve got now.

      I’ll also note that you should really consider moving DHCP services off of a DC.

      1 Reply Last reply Reply Quote 2
      • T
        Tom @Wayne Workman
        last edited by Feb 10, 2016, 3:24 PM

        @Wayne-Workman as much as I agree with you, that decision was made above me. Also, I have never encountered any issue with this setup.
        In terms od fog, I never had any issue while running 0.31.

        W 1 Reply Last reply Feb 10, 2016, 3:37 PM Reply Quote 0
        • W
          Wayne Workman @Tom
          last edited by Feb 10, 2016, 3:37 PM

          @Tom Well I mean, if the lease time is short enough or if you have a large enough pool of addresses on the 30% range DHCP Server - or a mixture of those two things - then you might never have problems.

          But I say what I say because the potential is there. It’s happened here where I work.

          We have a DHCP server that serves 100% of a range, and we had an old mac server - we used it for OpenDirectory for our Macs and for Deploy studio. It was configured to run DHCP for a very small subset of our range, and at the very end of our range - and we always kept that turned off unless we were using Deploy Studio. Well one day it was turned on somehow accidentally (not by me) and because the range was so small (256), it ran out of IPs quickly, and then our entire building suddenly started not getting addresses and auto-configuring with APIPA. Keep in mind that thousands and thousands of addresses were still available from our actual DHCP server - and it was even responding to requests, it’s just that the old mac server was beating it and serving addresses faster… or in this case, serving “no more addresses available” messages faster.

          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
          • W
            Wayne Workman @Tom
            last edited by Feb 10, 2016, 3:43 PM

            @Tom said:

            Installed tftp on my windows station, tried to do tfpt -I x.x.x.x get undioly.kpxe and received the following error:

            try tftp –i x.x.x.x get undionly.kpxe

            you have typos in your above command. tftpt and the -i should be lower case.

            If it still doesn’t work, sounds like a network thing or firewall thing. Can you ping the fog server from this windows box? ssh into 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!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            T 1 Reply Last reply Feb 10, 2016, 6:55 PM Reply Quote 0
            • T
              Tom @Wayne Workman
              last edited by Feb 10, 2016, 6:55 PM

              @Wayne-Workman So, disabled the firewall on my win 10 machine. Ran tftp -i x.x.x.x get undionly.kpxe successfully.
              I’m not sure why target machine cannot boot to pxe.

              Thanks,

              Tom

              W 1 Reply Last reply Feb 10, 2016, 7:10 PM Reply Quote 0
              • W
                Wayne Workman @Tom
                last edited by Feb 10, 2016, 7:10 PM

                @Tom On all the DHCP servers, please set options 066 and 067. 66 should be the FOG server IP, 67 should (generally) be undionly.kkpxe

                If you need help doing that - or have questions, please PM me so we can work much faster.

                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/

                T 1 Reply Last reply Feb 10, 2016, 8:34 PM Reply Quote 0
                • G
                  george1421 Moderator
                  last edited by george1421 Feb 10, 2016, 1:12 PM Feb 10, 2016, 7:11 PM

                  I think we are at the point where we are going to need to see a packet capture of what is really going down the wire with these dhcp servers. Your current setup is not standard, for sure. What we will need for you to do is setup wireshark (or other tool to collect a pcap file) on a mirrored port. Select the source of the mirror the port where the target computer you are trying to boot is connected. Set the filters on wireshark to “bootp || tftp”. Once you have wireshark collecting data boot the target computer until it fails then stop wireshark. Make the time between starting wireshark capture and booting the target computer as short as possible.

                  Post the pcap file here. There are several people in the forums that can decode it, even without a magic decoder ring. Also please note the ip address of the dhcp server(s)

                  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
                  • W
                    Wayne Workman
                    last edited by Wayne Workman Feb 10, 2016, 1:26 PM Feb 10, 2016, 7:23 PM

                    A mirrored port is not necessary. You can do a capture directly on your FOG server like this: https://wiki.fogproject.org/wiki/index.php?title=TCPDump

                    Also, just to collect DHCP data, you don’t need to do anything but just run a capture in Wireshark on a computer that’s on the same network as the computer’s you’re trying to fog. DHCP Discoveries and replies are broadcast messages - they go throughout the entire broadcast domain.

                    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/

                    G 1 Reply Last reply Feb 10, 2016, 7:33 PM Reply Quote 0
                    • G
                      george1421 Moderator @Wayne Workman
                      last edited by Feb 10, 2016, 7:33 PM

                      @Wayne-Workman The mirrored port suggestion was to also capture the unicast tftp requests from the point of view what the target is specifically seeing.

                      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
                      • T
                        Tom @Wayne Workman
                        last edited by Feb 10, 2016, 8:34 PM

                        @Wayne-Workman WOW, I don’t know what change, but it’s working now. I was able to register the OptiPlex 990 and the Latitude E7240.
                        Now I have to figure out the new interface, since it’s very different from 0.31.

                        THANK YOU ALL FOR YOUR HELP, I WOULD NOT BE ABLE TO DO IT WITHOUT YOU.

                        Tom

                        W G T 3 Replies Last reply Feb 10, 2016, 9:12 PM Reply Quote 0
                        • W
                          Wayne Workman @Tom
                          last edited by Feb 10, 2016, 9:12 PM

                          @Tom But does it work 5 times in a row…

                          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/

                          T 1 Reply Last reply Feb 10, 2016, 9:38 PM Reply Quote 2
                          • G
                            george1421 Moderator @Tom
                            last edited by george1421 Feb 10, 2016, 3:31 PM Feb 10, 2016, 9:30 PM

                            @Tom I want to be wrong here, but my intuition is telling me you are in the 30% category right now, where its working.

                            I hope for your sake you have fixed it so you can move on to greater things. If not, capture a pcap file when it fails and post back here. For now I’ll mark the thread as solved. We can change it back if we find out otherwise.

                            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
                            • T
                              Tom @Wayne Workman
                              last edited by Feb 10, 2016, 9:38 PM

                              @Wayne-Workman Tested it 3 times, I hope it will working properly.

                              Thanks for all your help.

                              Tom

                              1 Reply Last reply Reply Quote 0
                              • T
                                Tom Elliott @Tom
                                last edited by Feb 10, 2016, 9:44 PM

                                @Tom So what, exactly, did you have to do? After the problems that were shown by changing out all the dhcp servers to use undionly, nothing was working.

                                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

                                T 1 Reply Last reply Feb 10, 2016, 10:08 PM Reply Quote 0
                                • T
                                  Tom @Tom Elliott
                                  last edited by Feb 10, 2016, 10:08 PM

                                  @Tom-Elliott I’m not sure what exactly happened.
                                  I turned off the firewall on my workstation and made sure tftp answers. Then I changed option 67 from kpxe to kkpxe as Wayne suggested and it worked.
                                  I did not work before.
                                  I’ll if it’s continue to work properly over time.
                                  Maybe when tftp answered, it kicked something in Ubuntu 🙂
                                  Sorry I cannot be more helpful.
                                  I hope I did not create to much headache.

                                  Thanks for all your help.
                                  Tom

                                  Tom

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    Sebastian Roth Moderator
                                    last edited by Sebastian Roth Feb 11, 2016, 3:39 AM Feb 11, 2016, 9:37 AM

                                    I am wondering if we’ll ever find out what caused the kernel panic?? This is my major concern as we have seen those kernel panics caused by very different issues lately. From what I am getting between the lines the change from pxelinux.0 or undionly.kpxe to undionly.kkpxe made hugh difference. I don’t count the TFTP hickups as kernel bootup is way past that.

                                    Do we have a wiki article on kernel panics and debugging yet? I feel like we have made some progress on that in the last weeks. Checksum in the installer is a major step but as well earlyprintk in the kernel and efi_wrap in iPXE if it gets really ugly. Not sure if this is way to complex to document in the wiki?! Not to forget trying different iPXE binaries (kkpxe)… although I am still wondering why this has helped here as George has booted the same model without an issue.

                                    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

                                    T 1 Reply Last reply Feb 11, 2016, 1:18 PM Reply Quote 0
                                    • T
                                      Tom @Sebastian Roth
                                      last edited by Feb 11, 2016, 1:18 PM

                                      @Sebastian-Roth I don’t have deep understanding of FOG internal works, but I can say that when option 67 was set to prelinux.0 the kernel panicked.

                                      1 Reply Last reply Reply Quote 0
                                      • 1
                                      • 2
                                      • 3
                                      • 4
                                      • 4 / 4
                                      4 / 4
                                      • First post
                                        67/78
                                        Last post

                                      192

                                      Online

                                      12.0k

                                      Users

                                      17.3k

                                      Topics

                                      155.2k

                                      Posts
                                      Copyright © 2012-2024 FOG Project