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

    How to update an isolated FogServer from 1.5.7 to 1.5.9

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    7
    666
    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.
    • O
      otpyke
      last edited by

      Hello everyone,

      FOG inside VMWare ESXI 6.7 isolated cluster, installed in Debian 10.2

      I use Fog every day to deploy images, we got news computers with NVMe instead of HDD, so i have to update my FOG from 1.5.7 to 1.5.9 version.

      I tried in 1st place with a pratice VM to be sure everything is working fine with thoses news PC and it worked properly. The 1.5.9 version detected, captured and deployed images without trouble.

      The problem is, my FOG server is in isolated LAN, and it haves no acces to internet (impossible to apt-get or git the update for example) and it’s impossible to update it without internet acces.

      I don’t have any control acces to my FW or DHCP, i cannot create exceptions.

      Do you have any suggestions?

      Sincerly, a poor IT support.

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @otpyke
        last edited by

        @otpyke Is there any chance to build a new fog server outside of your secure environment then transport it into the secure environment via an OVA file? You will need to fix some ip address settings but you can at least get a working vm outside.

        If you can build a FOG server outside the secure environment, switch to the dev-branch so you are running FOG 1.5.9.110 or later, install the FOS linux kernel 5.15.x and you should be set for the latest hardware.

        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!

        O 1 Reply Last reply Reply Quote 0
        • O
          otpyke
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • O
            otpyke @george1421
            last edited by

            Hello @george1421 ,

            Thank you for your anwser. As you said i created the VM outisde and added the .OVA file into my ESXI. Tranfert worked and VM is running good, but unfortunately i cannot acces to the FOG Web interface with the new IP address i added in my DHCP, or the old address as well.

            I’ll update if i found a solution or not.

            george1421G 1 Reply Last reply Reply Quote 0
            • george1421G
              george1421 Moderator @otpyke
              last edited by

              @otpyke On the migrated VM inside your secure zone.

              Run the commands on the FOG server console.
              ip a s

              That should list the IP address of the FOG server. Make sure the IP address the fog server is now at is correct.

              Make sure apache is running and listening on port 80 (http)
              netstat -an | grep :80 that should give you a line like 0.0.0.0:80

              Once you can get to the web interface there is a process to fix the change in IP address from install time.

              1. Edit /opt/fog/.fogsettings fix IP address there
              2. Edit /tftpboot/defaut.ipxe edit the IP address there
              3. In the web ui FOG Configuration -> FOG Settings -> Expand All (button) search for the old IP address and change to new ip address.
              4. In the Storage Management section update the IP address in the default storage node.
              5. Now reboot the FOG server.
              6. Done

              That should take care of changing the IP address after FOG was installed.

              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!

              O 1 Reply Last reply Reply Quote 0
              • O
                otpyke @george1421
                last edited by

                @george1421 Hello again,

                I finally managed to configure my fog 1.5.9. The VM can now communicate with others machines in the network.
                But the web interface isn’t working, i compared it with my old fog 1.5.7 and everything looks good.

                i did as you told me but i cannot acces the the web interface…

                Any suggestions?

                george1421G 1 Reply Last reply Reply Quote 0
                • george1421G
                  george1421 Moderator @otpyke
                  last edited by george1421

                  @otpyke If your web interface is not reachable make sure that apache server is running. It sounds like maybe no. The apache server should start independent of IP address used.

                  netstat -an | grep :80 should show you if your apache server is listening on the http port. The command ip a s should show you the ip address your fog server is at now.

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

                  215

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project