SVN 6523 Snapin Replicator log errors
-
All of my nodes are now showing
[03-02-16 11:01:51 am] * | This is not the master node -
Notifying @Tom-Elliott and moved to bug reports
-
[03-03-16 7:59:02 pm] | Not syncing Snapin: Thin-Install [03-03-16 7:59:02 pm] | This is not the primary group [03-03-16 7:59:02 pm] | Not syncing Snapin: Thin-Update [03-03-16 7:59:02 pm] | This is not the primary group [03-03-16 7:59:02 pm] * Not syncing Snapin between node(s)snapins are not being replicated, although they are being deleted, only one node still has the snapins that were originally passed around to all. Out of the 4 nodes and one server (all of which are group master nodes), and all of the snapins are set with the Office/Server as the Primary group…which I assume is just where the “original” snapin/image is determined to be located in order to pass the appropriate snapin/image around…of the 5 total nodes the server and one node are the only machines with snapins in the /opt/fog/snapins folder.
SVN 6547
-
@Hanz Both snapins and images will only replicate across groups if they are associated to multiple groups.
-
@Tom-Elliott they are associated, with the server being the primary…you can only select one as primary, the process is beginning because deletion of the the snapins does happen, but not copying them over. Is this just my system doing this?
-
@Hanz As far as I can tell, it sounds like it. Can you update fog and try again? I have made many changes to the FTP scripts and last night I found another change had to happen as well. I suspect what you’re seeing is the snapins aren’t being seen as having the right size.
-
@Tom-Elliott I updated to 6547 last night, unfortunately I keep getting at least 1 storage node that fails.
* Getting checksum files for kernels and inits................OK * Downloading inits, kernels, and the fog client..............OK * Comparing checksums of kernels and inits....................Done * Enabling apache and fpm services on boot....................OK * Creating SSL Certificate....................................Failed! [bcs@VanElem bin]$I have to delete the /opt/fog and /var/www/html/fog folders along with deleting the fog user and reinstalling to get the installer to work correctly.
I think all of them have failed at least once now, there’s no rhyme or reason when it happens it seems.
-
[03-04-16 6:59:37 am] | We are group name: Wharton [03-04-16 6:59:37 am] * We have node ID: #3 [03-04-16 6:59:37 am] | We are node name: Wharton [03-04-16 6:59:37 am] | Not syncing Snapin: HP-SDM [03-04-16 6:59:37 am] | This is not the primary group [03-04-16 6:59:37 am] | Not syncing Snapin: Ninite_8-20-15 [03-04-16 6:59:37 am] | This is not the primary group [03-04-16 6:59:37 am] | Not syncing Snapin: Office2013_FullInstall [03-04-16 6:59:37 am] | This is not the primary group [03-04-16 6:59:37 am] | Not syncing Snapin: OfficeUninstall [03-04-16 6:59:37 am] | This is not the primary group [03-04-16 6:59:37 am] | Not syncing Snapin: Restart [03-04-16 6:59:37 am] | This is not the primary group [03-04-16 6:59:37 am] | Not syncing Snapin: Thin-Install [03-04-16 6:59:37 am] | This is not the primary group [03-04-16 6:59:37 am] | Not syncing Snapin: Thin-Update [03-04-16 6:59:37 am] | This is not the primary group [03-04-16 6:59:37 am] * Not syncing Snapin between node(s)This is from one of the nodes…like I said only 1 group can be primary…do I need to change that everytime I want to push from that node to a client ?
-
@Hanz What do you mean?
The Primary Group’s Master Node will replicate down to all the other groups master nodes (that the snapin/image is associated with).
From there the Master node of each group should pass the image down to the nodes within its own group.
-
@Tom-Elliott
0_1457094032740_snapins.docxsry don’t know how to post the pic itself
This is for the HP-SDM snapin as you can see it is assoc with all groups and office (Server) is primary group. All nodes are set as group masters
-
@Hanz The logs you’re copying here, are they from the Primary Group, or the other group’s masters?
-
@Tom-Elliott We figured out the first line (log) of this thread was due to service needing restarted…
The biggest log I posted is from the Wharton (is a master) storage node in GUI per the first line of the log. It is associated with the snapin, but isn’t the primary group, as I’ve stated before the primary group for ALL my snapins is the server /Office node.
-
@Hanz Right, can you get the log off THAT server?
-
03-04-16 7:27:25 am] Interface Ready with IP Address: 10.72.3.50 [03-04-16 7:27:25 am] Interface Ready with IP Address: 168.216.10.20 [03-04-16 7:27:25 am] Interface Ready with IP Address: adamstnel.s201.c33.k12.wv.us [03-04-16 7:27:25 am] Interface Ready with IP Address: fog-server [03-04-16 7:27:25 am] * Starting SnapinReplicator Service [03-04-16 7:27:25 am] * Checking for new items every 600 seconds [03-04-16 7:27:25 am] * Starting service loop [03-04-16 7:27:25 am] * Starting Snapin Replication. [03-04-16 7:27:25 am] * We are group ID: #1 [03-04-16 7:27:25 am] | We are group name: Office [03-04-16 7:27:25 am] * We have node ID: #1 [03-04-16 7:27:25 am] | We are node name: Fog-Server [03-04-16 7:27:25 am] * Found Snapin to transfer to 4 group(s) [03-04-16 7:27:25 am] | Snapin name: HP-SDM [03-04-16 7:27:26 am] | Local File: /opt/fog/snapins/HpSDM.bat [03-04-16 7:27:26 am] | Remote File: /opt/fog/snapins [03-04-16 7:27:26 am] | Local File size: 145 [03-04-16 7:27:26 am] | Remote File size: 4096 [03-04-16 7:27:26 am] | Files do not match [03-04-16 7:27:26 am] * Deleting remote file: /opt/fog/snapinsthat’s it
