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

    connection issues/slow menu load, missing graphics, boot menu will not work.

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    5
    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.
    • C
      cokewithvanilla
      last edited by

      Hello, I am having some odd FOG issues. When I boot to PXE, it is extremely slow when getting to the boot menu. Sometimes, the boot menu fails to load the graphics. 9 out of 10 tries to load something from the menu results in connection timing out. I have tried multiple systems and multiple cables, all have the same issue. It seems like the data is just coming across really slow, and sometimes it gets there in time and sometimes not. What could be causing this? It times out at “bzimage…”… once or twice i got it to work flawlessly.

      I am running Ubuntu x64 14.04 w/ latest FOG from trunk. I need the quick image option, and 1.2.0 fails with ipxe, and I have to workaround that with the old pxelinux.

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

        Look very, very hard for an IP conflict… because I think that’s your problem. BUT, it might not be a conflict - however I want you to try to rule that out first and then come back.

        Also - Look closely at iperf. https://iperf.fr/ You can use this tool to test available bandwidth. Obviously, if you have an IP conflict, the results from this will be extremely inaccurate, so again, please check for IP conflicts first.

        Turn your fog server off, and ping the IP… Check your documentation for static IPs, etc.

        Also - Is FOG installed on bare-metal or is it virtualized?

        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
        • C
          cokewithvanilla
          last edited by

          It is virtualized. I just restarted all my switches and whatnot and the problem is gone. Interesting.

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

            @cokewithvanilla Make note of it… sounds like a switch somewhere is having problems…

            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
            • Cire3C
              Cire3
              last edited by

              I have seen brown out’s freak out switches and routers… Messes up nvram in some cases, I would have to reprogram routers even when settings look fine. And yes, full clear and setup.

              If the switch did that again I would think about ditching it. Bad switches do crazy things.

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

              163

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project