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

    Fog 3396 FOGImageReplicator startup failed

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    7
    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.
    • M
      Mark Buteyn
      last edited by

      I just updated from .32 to 3389 (I think that was the version, it’s also the port number for RDP, so I may be wrong)
      I use Debian 7.8 currently. After the update the FOGImageReplicator wouldn’t start on the DefaultMember or any storage nodes. Updated to 3396 after via git on all machines and re-ran ./installfog.sh. The Defaultmember now runs FOGImageReplicator but none of the storage nodes do. The helpful error message after running “service FOGImageReplicator start” is “failed!”. I can’t find why in the logs I’ve been looking in. Any hints?

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

        .32 to 3389 is a huge jump…

        I’d strongly suggest going from .32 to 1.2.0 first, and then to 3389 if you’re willing.

        Double Check your credentials for your storage nodes.

        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
        • JunkhackerJ
          Junkhacker Developer
          last edited by

          are your fog server and storage nodes running the same versions of fog?

          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
          • M
            Mark Buteyn
            last edited by

            Thanks for your help.

            Wayne: Would you recommend I blow away the storage nodes and start with 1.2.0 then go to 3396? I’m assuming you mean the storage node passwords, not the mysql passwords. I didn’t change any passwords, but maybe the huge jumps caused issues with the password

            Junkhacker: They are all on 3396, all debian 7.8. The DefaultMember and primary Storage Node are VMs. my replicated storage nodes are physical machines. None of the storage nodes start the script successfully only the DefaultMember.

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

              If you’re doing a bone-cold fresh installation (OS and all), it’s perfectly fine to go straight to the latest revision.

              I’ll assume the secondary storage nodes have worked in the past? No network changes?

              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
              • M
                Mark Buteyn
                last edited by

                OK, thanks.

                Yes they have worked in the past. And I can still pull images from them, it’s just that replication isn’t working.

                1 Reply Last reply Reply Quote 0
                • M
                  Mark Buteyn
                  last edited by

                  I just decided to make the one that is working the master. The other two will still accept images and deploy them.

                  I’m not good at debugging init scripts. It seems that the init script claims a PID, but the PID never shows up in top on the ones that aren’t working. This is also evidenced when I do a stop of the FOGImageReplicator script, I get an error that says can’t kill PID 3325 (or whatever the PID is). If I do a stop again it says OK. So something isn’t firing right, but it’s not that big of a deal to me since one is working.

                  Thanks for all your work on this. Much improved over the last 6th months.

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

                  236

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project