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

    New storage node - sync not working

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    2
    5
    1.6k
    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.
    • T
      Tony Ayre
      last edited by

      Server
      • FOG Version: 1.3.4
      • OS: Ubuntu 16.04.1LTS
      Description

      I have installed a storage node following the instructions on the wiki. All looks fine as far as I can see, but no sync is happening. I am receiving the following error in both the Image Replicator and Snapin Replicator logs:

      [02-07-17 10:49:37 am] * Type: 8, File: /var/www/html/fog/lib/fog/fogbase.class.php, Line: 841, Message: Undefined index: storagegroupID, Host: 10.5.147.249, Username: fog

      I have double checked the storage node settings on the master server, including ensuring the password is correct. What am I missing?

      1 Reply Last reply Reply Quote 0
      • T
        Tony Ayre
        last edited by

        Ah, figured it out. It was a routing issue between the 2 servers.

        It may be worth providing a user friendly error in the log if the master can’t connect with the storage node.

        Jaymes DriverJ 1 Reply Last reply Reply Quote 1
        • Jaymes DriverJ
          Jaymes Driver Developer @Tony Ayre
          last edited by

          @Tony-Ayre Would you mind elaborating on the issue, so if others have this issue, they will have a resolution?

          WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

          T 1 Reply Last reply Reply Quote 0
          • T
            Tony Ayre @Jaymes Driver
            last edited by Tony Ayre

            @Jaymes-Driver

            Absolutely. Our 2 servers are in different schools, with an IPSec VPN in between. I am currently building a new network consisting of a single domain across all schools, but have to maintain the existing multi-domain setup.

            On my firewall, I hadn’t allowed each side to use the other side from my new IP address range. Allowing this on the firewall resolved the issue.

            Simply put - the 2 servers were unable to route to each other - there was no route between them.

            I would say a good solution might be for the replication services to give an error stating that the server can’t be contacted though.

            Jaymes DriverJ 1 Reply Last reply Reply Quote 0
            • Jaymes DriverJ
              Jaymes Driver Developer @Tony Ayre
              last edited by

              @Tony-Ayre

              Thank you very much, This may help someone in the future with a similar issue 😉

              I appreciate you taking the time to explain your issue and your resolution!

              WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

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

              208

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project