SnapinReplicator Service stopped working



  • I haven’t relied on FOG to deploy many snapins recently, but had a need for it yesterday only to find out that the replication service is not working in our FOG 1.5.8 deployment.

    The Log reported the date as sometime in Februrary since the last entry. I restarted the service and it never updated. ALL other logs do update. I started the service manually as sudo and finally received a new log:

    [07-13-20 5:52:51 pm] Interface Ready with IP Address: x.x.x.x
    [07-13-20 5:52:51 pm] Interface Ready with IP Address: 127.0.0.1
    [07-13-20 5:52:51 pm] Interface Ready with IP Address: 127.0.1.1
    [07-13-20 5:52:51 pm] Interface Ready with IP Address: FOG.banditlites.local
    [07-13-20 5:52:51 pm] * Starting SnapinReplicator Service
    [07-13-20 5:52:51 pm] * Checking for new items every 600 seconds
    [07-13-20 5:52:51 pm] * Starting service loop
    [07-13-20 5:52:51 pm] * Starting Snapin Replication.
    [07-13-20 5:52:51 pm] * We are group ID: 1. We are group name: default
    [07-13-20 5:52:51 pm] * We are node ID: 1. We are node name: 11-MAIN
    [07-13-20 5:52:51 pm] * Attempting to perform Group -> Group snapin replication.
    [07-13-20 5:52:51 pm] | Replicating ssl less private key
    [07-13-20 5:52:51 pm] * Found Snapin to transfer to 3 nodes
    [07-13-20 5:52:51 pm] | File Name: ssl/fog.csr
    [07-13-20 5:52:54 pm] * Type: 2, File: /var/www/fog/lib/fog/fogftp.class.php, Line: 464, Message: ftp_login(): Login incorrect., Host: x.x.x.x, Username: fogproject

    It stopped there. I did test the login using the FTP login info from the .fogsettings config file in /opt/fog and logged in successfully.

    Also, I unchecked the “Replicate” option on the snapin, thinking that would force the clients to download from the main server. I can deploy the snapin to anyone local to the main server without issue, but anyone outside of this location receives a HASH error on the fog client:
    7/14/2020 9:08:25 AM SnapinClient ERROR: Hash does not match
    7/14/2020 9:08:25 AM SnapinClient ERROR: --> Ideal: 66496D1D5FA6B6D7606BFF718E1BEFE195BC71BC0628B2764AFDD5C9ED0B53E0E6B3486650D217EE8D42F5C6FA188300BF8D4DEC6882EC2BAC01A5459080FF85
    7/14/2020 9:08:25 AM SnapinClient ERROR: --> Actual: BFBA49E97B70CC6E124CAD15C3775245230B9BCEE4E7641566AC88B812D2822C39C58A3797A2FDE9B5E4721D24DF20A9D66490236688FBD39E7DCE154C51C365

    Help would be appreciated.
    Thank you!


  • Senior Developer

    @D-Bandit Please check the state of the service by running systemctl status FOGSnapinReplicator. So you see any errors there?



  • @Sebastian-Roth

    Sorry it has taken so long to reply.

    Yes. The Master is 1.5.8 and all 3 nodes are 1.5.8.


  • Senior Developer

    @D-Bandit Are all your nodes on FOG version 1.5.8??



  • @Sebastian-Roth Thank you for replying. All help is appreciated!

    Did as requested, configured the Storage Node UI with the password from the .fogsettings and were confirmed correct with an ftp client.

    Restarted the FOGSnapinReplicator service. The log is still not updating, I believe this to be just a symptom to the issue and including it as such. This is what is currently displayed after restarting the service just now and is the last log generated after running the service with ‘sudo FOGSnapinReplicator’ yesterday:

    [07-14-20 10:36:24 am] * Type: 2, File: /var/www/fog/lib/fog/fogftp.class.php, Line: 464, Message: ftp_login(): Login incorrect., Host: x.x.x.x, Username: fogproject
    [07-14-20 10:36:21 am] | File Name: ssl/fog.csr
    [07-14-20 10:36:21 am] * Found Snapin to transfer to 3 nodes
    [07-14-20 10:36:21 am] | Replicating ssl less private key
    [07-14-20 10:36:21 am] * Attempting to perform Group -> Group snapin replication.
    [07-14-20 10:36:21 am] * We are node ID: 1. We are node name: 11-MAIN
    [07-14-20 10:36:21 am] * We are group ID: 1. We are group name: default
    [07-14-20 10:36:21 am] * Starting Snapin Replication.
    [07-14-20 10:36:21 am] * Starting service loop
    [07-14-20 10:36:21 am] * Checking for new items every 600 seconds
    [07-14-20 10:36:21 am] * Starting SnapinReplicator Service
    [07-14-20 10:36:21 am] Interface Ready with IP Address: FOG.local
    [07-14-20 10:36:21 am] Interface Ready with IP Address: 127.0.1.1
    [07-14-20 10:36:21 am] Interface Ready with IP Address: 127.0.0.1
    [07-14-20 10:36:21 am] Interface Ready with IP Address: x.x.x.x
    
    
    ==================================
    == Released under GPL Version 3 ==
    ==================================
    = https://fogproject.org/Credits =
    ============ Credits =============
    ==================================
    ===== Free Opensource Ghost ======
    ==================================
    === ========== ===== ====
    === ========= == === == ===
    === ======== ==== == ==== ===
    === ======== ==== == === ===
    === ==== ==== == =========
    === ======== ==== == =========
    === ======== ==== == ==== ===
    === ========= == === == ===
    === ==== ===== ====
    ==================================
    [07-14-20 10:36:21 am]
    


  • This post is deleted!

  • Senior Developer

    @D-Bandit While .fogsettings is the base information used when you run the FOG installer/updater script, the replication service should actually use the credentials stored in the database to connect to your storage node. So please open the web UI and make sure you reset the FTP password for this particular storage node to what you have tested as correct.



  • Thank you for replying.

    I found some issues, one Node had the wrong IP because I did not update it after changing the IP scheme there. Another had the wrong subnet mask all-together, but all of the passwords check out.

    I restarted the service and the log is still not updating.

    I have to manually sudo run the service:

    ’ sudo ./FOGSnapinReplicator’

    And then the log updates, but with the exact same message.


  • Moderator

    One comment, the replicator connects to the remote FOG server using the fogproject user ID (as you know) but the password is dependent on the password found in the .fogsettings file on the remote storage node. You probably should run through and review the .fogsettings on the remote storage node and then from a windows computer attempt to connect to the remote storage node using ftp, with the user id of fogproject and the password found in the remote storage node’s .fogsettings file. If the ftp works, then confirm that the storage node configuration (via the master node’s web ui) is using the proper credentials and password to access the remote storage node.


Log in to reply
 

296
Online

7.4k
Users

14.5k
Topics

136.5k
Posts