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

    Help! DHCP suddenly gone haywire!

    Scheduled Pinned Locked Moved
    Linux Problems
    3
    4
    1.7k
    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.
    • G
      gwhitfield
      last edited by

      Yikes!! All of a sudden this morning I have at least 7 different FOG servers screwing up DHCP booting for machines at their respective locations. All of them are Ubuntu 14.0.4, TRUNK version 7695 or later. ALl have been working fine for months if not years. I have had to shut them down so DHCP will work (eventually). I can’t even troubleshoot them without messing with users. All I got was a glimpse of a boot screen saying chainloading failed and then screen would cycle through boot again and never get to the client’s HD to boot.

      The only think I can think of that would cause so many servers to go wrong at the same time is an Ubuntu update, Maybe it was a mistake to configure the server during install to automatically update security patches but now I’m hoping someone has an idea of what I can do to correct this situation quickly??? I’m no Ubuntu expert but I figure this is the best place to go for the time being to see if anyone can assist?

      1 Reply Last reply Reply Quote 0
      • JunkhackerJ
        Junkhacker Developer
        last edited by

        if an ubuntu update broke it, reinstalling/upgrading fog would probably fix it

        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 Quazz

          I believe there was a chainloading issue earlier which got fixed, so try updating to the latest.

          Although, in your situation that seems unlikely given how this didn’t happen because of a FOG update.

          What Junkhacker suggests could work, if it doesn’t I’d have to guess that something in your network was altered to cause this.

          G 1 Reply Last reply Reply Quote 1
          • G
            gwhitfield @Quazz
            last edited by

            @Junkhacker @Quazz Thank you both ! I did try re-installing FOG on one server and it worked. Then I tried just restarting another server and that worked too. I then restarted ALL the affected servers and they all worked. Don’t know why the problem occurred, never seen that happen in 10 years so I guess I learned something today and I can sleep well tonight 🙂

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

            224

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project