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

    v5746 svn Downloading inits, kernels, and the fog client Failed!

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    6
    1.8k
    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.
    • F
      FlareImp
      last edited by

      I upgraded one of my fog servers a week ago and everything was working and setup great. Now I am trying to upgrade the two storage nodes that were connected to that fog server and I am getting the error above. I have even tried copying the install folder that worked from the Fog server to the two storage nodes with no luck. One node I just tried upgrading by running the installer and the other node was a fresh install of Ubuntu 14 then running the installer. Both installs failed when it got to the inits, kernels, and fog client install.

      Thanks,

      1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott
        last edited by

        Aren’t you behind a proxy?

        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
        • F
          FlareImp
          last edited by

          Yes but the VLAN that our servers are on are wide open. I already spoke to our ISP.

          Wayne WorkmanW 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator
            last edited by george1421

            Lets check a few things. You say you were able to install a SVN trunk the other day correct?

            Do you still have the environment variable set to point to your proxy server? Can you confirm you still have them set?

            While this is an old URL, can you run the following command from the console of your FOG server.

            wget http://downloads.sourceforge.net/project/freeghost/FOG/fog_1.2.0/fog_1.2.0.tar.gz

            I’m interested to see if the download starts vs the file actually being downloaded.

            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
            • Wayne WorkmanW
              Wayne Workman @FlareImp
              last edited by Wayne Workman

              @FlareImp Can you remove the output redirection on that line so we can see the error?

              Look in .../trunk/lib/common/functions.sh at line number 1174 through 1201, remove >/dev/null 2>&1 where you see it there. This will allow whatever the error is to show in the output. I’d especially look at lines 1175 through 1177.

              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
              • F
                FlareImp
                last edited by

                Never mind, apparently the guy that was told to make the changes only did it for one of our sites and not all seven. sorry for wasting your guys’ time.

                This issue is resolved now.

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

                156

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project