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

    Fog 1.2 replicating issue on master node

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    6
    1.9k
    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.
    • D
      dustindizzle11
      last edited by

      This might be a simple one, but I haven’t been able to figure it out yet so I thought I would ask.

      I upgraded to Fog 1.2 a while back, but noticed yesterday that the master node wasn’t replicating the new image I had just uploaded (I updated an image from partimage to make it partclone). When I look in the replicator log, I see this message. (The partclone image is Windows7x64BASE). I have tried changing permissions and I still get the error.

      [09-04-15 10:57:08 am] * [09-04-15 10:57:08 am] SubProcess -> Making directory `Windows7x64BASE’

      [09-04-15 10:57:08 am] * [09-04-15 10:57:08 am] SubProcess -> ln: Fatal error: 500 Unknown SITE command.

      [09-04-15 10:57:08 am] * [09-04-15 10:57:08 am] SubProcess -> Mirroring directory `Windows7x86-b’

      [09-04-15 10:57:09 am] * [09-04-15 10:57:09 am] SubProcess -> mirror: Access failed: 550 Failed to change directory. (/images/Windows7x64BASE)

      I appreciate any ideas that can help me fix the issue. Thanks!

      Dustin

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

        @dustindizzle11 Have you updated all of your storage nodes to 1.2.0 ?

        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/

        D 1 Reply Last reply Reply Quote 0
        • D
          dustindizzle11 @Wayne Workman
          last edited by

          @Wayne-Workman I haven’t updated them. If that is supposed to happen, that could be the problem. Is there a wiki for this or a guide for updating a storage node? Or is it pretty straight forward (run the installer and images will not be wiped out?)

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

            It’s straight forward. FOG may make updates to the Web files (even obliterating any customizations you’ve done) but it does not destroy the images. It doesn’t destroy the database, directly, either. So all definitions that you have (beyond simple modifications of things) will remain as well.

            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

            D 1 Reply Last reply Reply Quote 0
            • D
              dustindizzle11 @Tom Elliott
              last edited by dustindizzle11

              @Tom-Elliott Thanks Tom.

              I upgraded all the nodes. What cleared the error is below.

              The issue was that this was a “part-image” type of image that I updated and re-uploaded which converted it into a partclone image. The master node overwrote the old file when I uploaded the image. The other nodes though, which get the image updated from the master still had the old image on them which was a file, not a directory which partclone seems to use. Once I deleted the old image from the nodes, it replicated to the others without the error.

              1 Reply Last reply Reply Quote 1
              • JunkhackerJ
                Junkhacker Developer
                last edited by

                if you’re still having issues with the “vista” setting, your best bet would be to upgrade to a trunk version of fog where it’s already fixed.

                signature:
                Junkhacker
                We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

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

                234

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project