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

Adding new node error

Scheduled Pinned Locked Moved Solved
FOG Problems
2
6
1.2k
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
    msi Testers
    last edited by msi Aug 31, 2017, 5:49 PM Aug 31, 2017, 11:48 PM

    hi,
    getting below error after adding a new node. How we can solve it?

    [08-31-17 11:46:58 pm] * Starting Image Replication.
    [08-31-17 11:46:58 pm] * We are group ID: 1. We are group name: default
    [08-31-17 11:46:58 pm] * We are node ID: 1. We are node name: DefaultMember
    [08-31-17 11:46:58 pm] * Attempting to perform Group -> Group image replication.
    [08-31-17 11:46:58 pm] | Replicating postdownloadscripts
    [08-31-17 11:46:58 pm] * Found Image to transfer to 1 node
    [08-31-17 11:46:58 pm] | File Name: postdownloadscripts
    [08-31-17 11:47:01 pm] * Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 463, Message: ftp_login(): Login incorrect., Ho
    st: 192.168.1.200, Username: fog

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator @msi
      last edited by george1421 Aug 31, 2017, 5:59 PM Aug 31, 2017, 11:59 PM

      @msi
      Inspect the /opt/fog/.fogsettings file on the remote storage node. Then back on the master node, check the web management gui for that storage node definition. Ensure the management user ID is fog and the managment password matches the password field in the .fogsettings on the remote storage node. If they are in allignment then I have to ask you, did you muck about with the linux user fog on the remote storage node?

      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!

      M 1 Reply Last reply Sep 1, 2017, 12:11 AM Reply Quote 0
      • G
        george1421 Moderator
        last edited by Aug 31, 2017, 11:56 PM

        @msi said in Adding new node error:

        192.168.1.200

        Is 192.168.1.200 a remote storage node?

        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!

        M 1 Reply Last reply Aug 31, 2017, 11:58 PM Reply Quote 0
        • M
          msi Testers @george1421
          last edited by Aug 31, 2017, 11:58 PM

          @george1421 yes

          G 1 Reply Last reply Aug 31, 2017, 11:59 PM Reply Quote 0
          • G
            george1421 Moderator @msi
            last edited by george1421 Aug 31, 2017, 5:59 PM Aug 31, 2017, 11:59 PM

            @msi
            Inspect the /opt/fog/.fogsettings file on the remote storage node. Then back on the master node, check the web management gui for that storage node definition. Ensure the management user ID is fog and the managment password matches the password field in the .fogsettings on the remote storage node. If they are in allignment then I have to ask you, did you muck about with the linux user fog on the remote storage node?

            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!

            M 1 Reply Last reply Sep 1, 2017, 12:11 AM Reply Quote 0
            • M
              msi Testers @george1421
              last edited by Sep 1, 2017, 12:11 AM

              @george1421 I think its working now… what happen, I updated the node while updating the node IP. The password field was changed to just password (not encrypted one). Below is the latest, please let me know if this is what I should see:

              Every 2.0s: tail fogreplicator.log

              [09-01-17 12:07:04 am] | 8431531 0 /images/Win10-2.1/d1p3.img
              [09-01-17 12:07:04 am] | Files do not match.
              [09-01-17 12:07:04 am] * Deleting remote file:
              [09-01-17 12:07:04 am] | 14474904492 0 /images/Win10-2.1/d1p4.img
              [09-01-17 12:07:04 am] | Files do not match.
              [09-01-17 12:07:04 am] * Deleting remote file:
              [09-01-17 12:07:04 am] * Starting Sync Actions
              [09-01-17 12:07:04 am] | CMD:
              lftp -e ‘set xfer:log 1; set xfer:log-file “/opt/fog/log/fogreplicator.Win10-2.1.transfer.njedclient.log”;set ftp:
              list-options -a;set net:max-retries 10;set net:timeout 30; mirror -c -r -R --ignore-time -vvv --exclude “.srvprivate” “/images/Win10-2.1”
              “/images/Win10-2.1”; exit’ -u fog,[Protected] 10.135.200.230
              [09-01-17 12:07:04 am] * Started sync for Image Win10-2.1

              G 1 Reply Last reply Sep 1, 2017, 12:18 AM Reply Quote 0
              • G
                george1421 Moderator @msi
                last edited by Sep 1, 2017, 12:18 AM

                @msi Yep looks good now.

                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
                • 1 / 1
                1 / 1
                • First post
                  1/6
                  Last post

                187

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project