@theWizard Did you recently update this snapin and re upload it to the master? It sounds like you made a change to the snapin (the uploaded file) which changed the hash on the master side. I assume you are trying to run this snapin at a remote node which still has the old hash value. Seems like the new version just hasn’t replicated out to the remote node yet.

Posts made by adukes40
-
RE: Hash does not match
-
RE: Snapins removed from Previously registered hosts
@Tom-Elliott Which would I choose
-
RE: Snapins removed from Previously registered hosts
@Tom-Elliott Correct, all the associations have been blown out. How would I restore them from the backup?
Also I did not get around to updating the nodes until the weekend, so the nodes are on version 39, but master on 33. Would that cause it?
-
RE: Gui not responsive
We were having this issue to. However, I haven’t had the time to dive into why the clients were failing to updated. But Wayne stated that the clients kept downloading from the server, which with a couple thousand hosts, this was flooding the pipe, and basically making the GUI unusable because the NIC was pegged. Once I unchecked those boxes things have been great. Maybe one day I will get that magical thing called time to dive into it with someone.
-
Snapins removed from Previously registered hosts
Since the snapin hash issue of last week. I noticed that all the hosts we have registered, have lost the assigned snapins they used to have. Is there a way to get those settings back from a backup? or do we need to reassigned snapins to 3000 hosts?
-
RE: RC10 Broken Items on upgrade
OK, in the other snapin hash thread, he checked on the hash value of the snapin on different nodes. I just tried the same. Running the sha512sum command on the snapin on the master returns a value. However, on the node the ps1 file no longer exists. I deleted this snapin all together from FOG. I re-added it. So what happened was, it removed it from the master and all nodes, but is not replicating out the newly made one. I checked on two nodes, not there. Restarted the FOGSnapinReplicator on the Master, and still do not see it on the nodes.
Hope this helps some
Also the individual node snapin replicator log, shows up with looks like replicated snapins, but on the node I am part of just shows a bunch of code.
set ftp:sync-mode/sunsolve.sun.com on
set net:max-retries 10
set net:timeout 30
set xfer:max-redirections 10
set xfer:verify-command /usr/share/lftp/verify-file
set cmd:prompt "lftp \S\? \u\@\h:\w> "
set cmd:term-status/rxvt “\e[11;0]\e]2;\T\007\e[11]”
set cmd:term-status/screen \e_\T\e\
set cmd:term-status/xterm “\e[11;0]\e]2;\T\007\e[11]”
set dns:order “inet6 inet”
set file:charset ANSI_X3.4-1968
set ftp:auto-sync-mode “icrosoft FTP Service|MadGoat|MikroTik”
set ftp:list-options -a
set ftp:sync-mode/ftp.idsoftware.com on
set ftp:sync-mode/ftp.microsoft.com on
set ftp:sync-mode/sunsolve.sun.com on
set net:max-retries 10
set net:timeout 30
set xfer:max-redirections 10
set xfer:verify-command /usr/share/lftp/verify-file -
RE: RC10 Broken Items on upgrade
@Tom-Elliott What is this setting:
FOG_SNAPIN_LOCATION_SEND_ENABLED It is not checked on my end
also the snapin replicator says
[09-16-16 9:20:44 am] | I am the only member
-
RE: RC10 Broken Items on upgrade
@Wayne-Workman The Master image still has 11.2 on it, I have tried manually installing 11.5 on the machines as well. doesn’t seem to matter. just complains about the hash not existing. and of course it does not in the snapin mgmt. I have tried imaging and having it auto run, deploying it as a single snapin, or assigning all snapins to it and telling it to deploy.
And the machines I’m testing with, is within a second of the server time. All machine near me all say 11:14 as does the server. OO and just noticed the file size in snapin mgmt shows 0.00, as someone in another thread mentioned.
-
RE: RC10 Broken Items on upgrade
@Wayne-Workman My only concern with that is, I go to turn on the auto updating, and the NIC get hammered like last time. there is no getting back in to turn it off, until 6pm, when the student machines shutdown and takes the strain off the NIC and lets the GUI load. Then I would have to shut the NIC off. I wanted to leave that on to work on this Hashing issue with snapins. Later I can work on the client stuff.
-
RE: RC10 Broken Items on upgrade
@Tom-Elliott mysql> update tasks set taskStateID=5 where taskStateID=3;
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0Still same.
-
RE: RC10 Broken Items on upgrade
@Tom-Elliott mysql> update tasks set taskStateID=5 where taskStateID < 4;
Query OK, 0 rows affected (0.00 sec)
Rows matched: 0 Changed: 0 Warnings: 0mysql> Truncate table snapinJobs;
Query OK, 0 rows affected (0.04 sec)mysql> Truncate table snapinTasks;
Query OK, 0 rows affected (0.08 sec)But still shows 476 on dashboard
-
RE: RC10 Broken Items on upgrade
@Tom-Elliott I have no tasks currently. I cant do all machine, but I can take a machine and push all snapins to it, or at least attempt to.
-
RE: RC10 Broken Items on upgrade
@Tom-Elliott OK, all sites are updated, FOG GUI is showing
Also see this, not sure if concerning or not:
-
RE: RC10 Broken Items on upgrade
@Tom-Elliott not really, but Wayne gave me some instructions way back in the thread.
But I will do what ever is needed.
-
RE: RC10 Broken Items on upgrade
@Tom-Elliott Still just sit in Queued, and Snapin hash still remains blank. also running at the master site and a node site.
-
RE: RC10 Broken Items on upgrade
@Wayne-Workman running Date give me:
Fri Sep 16 07:44:34 EDT 2016
which is MAYBE 1-2 seconds off from my machine.
-
RE: RC10 Broken Items on upgrade
@Wayne-Workman The snapins I am trying to use exist at all locations.
-
RE: RC10 Broken Items on upgrade
@Tom-Elliott
---------------------------------SnapinClient---------------------------------
9/15/2016 8:42 PM Client-Info Client Version: 0.11.5
9/15/2016 8:42 PM Client-Info Client OS: Windows
9/15/2016 8:42 PM Client-Info Server Version: 1.3.0-RC-10
9/15/2016 8:42 PM Middleware::Response Success
9/15/2016 8:42 PM SnapinClient Snapin Found:
9/15/2016 8:42 PM SnapinClient ID: 11116
9/15/2016 8:42 PM SnapinClient Name: 1-TS-SHOP
9/15/2016 8:42 PM SnapinClient Created: 2016-09-15 20:41:58
9/15/2016 8:42 PM SnapinClient Action:
9/15/2016 8:42 PM SnapinClient Pack: False
9/15/2016 8:42 PM SnapinClient Hide: False
9/15/2016 8:42 PM SnapinClient Server:
9/15/2016 8:42 PM SnapinClient TimeOut: 0
9/15/2016 8:42 PM SnapinClient RunWith: powershell.exe
9/15/2016 8:42 PM SnapinClient RunWithArgs: -ExecutionPolicy Bypass -NoProfile -File
9/15/2016 8:42 PM SnapinClient Args:
9/15/2016 8:42 PM SnapinClient File: TSSHOP.ps1
9/15/2016 8:42 PM SnapinClient ERROR: Snapin hash does not exist -
RE: RC10 Broken Items on upgrade
@Tom-Elliott All nodes are running RC-10 and powered on. and Enabled. The services should still be stopped from before.