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

Upgrading from Trunk to 1.4.0.

Scheduled Pinned Locked Moved
General
3
6
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.
  • A
    Avaryan
    last edited by Avaryan May 18, 2017, 7:50 PM May 19, 2017, 1:48 AM

    I’ve finally gotten approval to upgrade our live server from revision 5837 (dev branch that came out just before 1.3 RC’s).

    Are there any expected or known issues that might arise?

    I’ve disabled the client updater and a snapshot of the server will be taken prior to update, just in case. Wasn’t sure how FOG would like it if the hosts received the new client, but the server ended up getting rolled back.

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by May 19, 2017, 2:10 AM

      I’m not sure how the client would like it, though I think it’s relatively safe to allow the clients to be ahead of the version of fog you’re running. There may be some features, however, that could make the client puke all over itself.

      The biggest thing I’m seeing is Ubuntu SUCKS. (Sorry I am just sick of ubuntu’s problems now).

      Some features like, the fog client expecting Power Management, but the version you installed didn’t have that feature available.

      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

      1 Reply Last reply Reply Quote 0
      • A
        Avaryan
        last edited by May 19, 2017, 2:20 AM

        We don’t use the Power Management feature, so no issue there.

        The live server is on Ubuntu 14.04.4. Would you recommend staying on 14 or maybe moving to 16?

        T 1 Reply Last reply May 19, 2017, 2:22 AM Reply Quote 0
        • T
          Tom Elliott @Avaryan
          last edited by May 19, 2017, 2:22 AM

          @Avaryan I’d say stay on 14.04, I think it’s still in it’s support cycle.

          Moving to 16 wouldn’t hurt, but it could potentially cause problems though I couldn’t tell you what and/or why. It is still very “random” (albeit it quite often lately) to have issues.

          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

          1 Reply Last reply Reply Quote 0
          • A
            Avaryan
            last edited by Avaryan May 18, 2017, 8:26 PM May 19, 2017, 2:25 AM

            Ok. We’ll stay at 14. I imagine the network admin wouldn’t like it if I updated the whole OS while still retaining the trunk snapshot (because it saves the changes to be able to revert.)

            Just noticed the the directory that fog is in is /root/fogproject_trunk. Will there be any issues if I rename the directory to /root/fogproject/. Want to keep installation as inline with stock settings as possible.

            edit: So, noticed that git isn’t installed on the trunk server. Not sure what he used when he set this up. I’ve always used git.

            Q 1 Reply Last reply May 19, 2017, 9:32 AM Reply Quote 0
            • Q
              Quazz Moderator @Avaryan
              last edited by Quazz May 19, 2017, 3:34 AM May 19, 2017, 9:32 AM

              @Avaryan SVN or a package download most likely.

              You can safely delete that directory and intialize git in /root where it will create the folders as needed. These are only the installation folders (as in everything needed to install FOG, not where everything is installed), they don’t contain any settings or the like.

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              1 / 1
              • First post
                3/6
                Last post

              155

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project