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

Fog Update 1.4.4

Scheduled Pinned Locked Moved
FOG Problems
3
6
620
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.
  • K
    Kamiii
    last edited by Oct 16, 2020, 6:50 PM

    Hello, I’m running old version of FOG 1.4.4 with a node also on 1.4.4.
    Both of these run on proxmox 6.2.9 debian strech containers.

    I’d like to update to a newer version of fog, which one is the most stable at the moment?
    I also have around 30 Images, should I keep a copy of my config and just reinstall a newer version of fog on top of it ?

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Oct 16, 2020, 7:51 PM

      How many workstations running the FOG client do you have?

      There may be more value in spinning up a new server than an in place upgrade. As for what OS, any of the big three. I’m going to list them in my preferred order, but I’m a rhel guy. Centos 8, Debian 10, or Ubuntu 20.04.

      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!

      K 1 Reply Last reply Oct 17, 2020, 6:53 PM Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by Oct 17, 2020, 2:21 PM

        @Kamiii said in Fog Update 1.4.4:

        Both of these run on proxmox 6.2.9 debian strech containers

        That means you want to update to Debian Buster (10) as well? While we try to cover a lot of the changes between dist-upgrades I can’t promise you this will go without glitch. You definitely want to use FOG 1.5.9 (latest official release) and not one of the earlier ones that had more issues with dist-upgrades.

        As George said you might be way faster setting up new containers and importing the database, copying image files than doing the update.

        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

        1 Reply Last reply Reply Quote 0
        • K
          Kamiii @george1421
          last edited by Oct 17, 2020, 6:53 PM

          @george1421
          Hello, at the moment none of the workstation run FOG client, I just took over the IT position and the previous IT guy never updated FOG…
          As for the images, how do I copy them over to a new fog node?

          G 1 Reply Last reply Oct 17, 2020, 10:43 PM Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Oct 17, 2020, 7:13 PM

            @Kamiii said:

            As for the images, how do I copy them over to a new fog node?

            Take a full copy of everything in /images/ (preserving access rights). You might want to check in /opt/fog/.fogsettings to see if the default location /images/ has actually been used.

            Other than that you want to read through this as well: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

            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

            1 Reply Last reply Reply Quote 0
            • G
              george1421 Moderator @Kamiii
              last edited by Oct 17, 2020, 10:43 PM

              @Kamiii said in Fog Update 1.4.4:

              As for the images, how do I copy them over to a new fog node?

              When you setup a new FOG server make sure you place the /images on its own partition. If you use Centos to install the default will be to place the root partition on 50GB and then give /home the remainder of the disk. For FOG I would select custom configuration and then select auto create partitions. Then rename /home to /images sections and then set that configuration. This will keep you from accidentally filling up the partition with imaging and killing your OS and database. The other option if creating in a VM pick the minimum size of disk required by your OS and then install the OS. Once the OS is installed create a second disk for your images and then mount that new disk over the /images mount point, THEN install FOG. This will then keep your disk images on a different disk and away from your OS disk.

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

              158

              Online

              12.1k

              Users

              17.3k

              Topics

              155.3k

              Posts
              Copyright © 2012-2024 FOG Project