RC10 Broken Items on upgrade
-
@Wayne-Workman no it’s not. Client updating is not a fog tasking.
-
@Wayne-Workman The snapins I am trying to use exist at all locations.
-
@Wayne-Workman running Date give me:
Fri Sep 16 07:44:34 EDT 2016
which is MAYBE 1-2 seconds off from my machine.
-
@adukes40 the wget command, can you run that on all your nodes and try again?
-
@Tom-Elliott Still just sit in Queued, and Snapin hash still remains blank. also running at the master site and a node site.
-
@adukes40 are you semi familiar with git?
-
@Tom-Elliott not really, but Wayne gave me some instructions way back in the thread.
But I will do what ever is needed.
-
@adukes40 Please run:
git clone https://github.com/fogproject/fogproject.git
cd fogproject
git checkout working-RC-11
cd bin
installfog.sh -y
I don’t want everybody doing this, just @adukes40 please.
Please do this for all your nodes? Replication is not the issue with the load and that was corrected for with disabling auto update which should remain as it currently is. I’m trying to see if something is corrected in the working branch which is making my debugging that much harder.
-
@Tom-Elliott OK, all sites are updated, FOG GUI is showing
Also see this, not sure if concerning or not:
-
@adukes40 the version message is fine.
What is concerning is the tasks, but you have setup all hosts to do all snapins, or all hosts do one snapin, or one host does all snapins?
-
@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.
-
@adukes40 to clean up bad tasks then just run mysql command like:
update tasks set taskStateID=5 where taskStateID < 4; Truncate table snapinJobs; Truncate table snapinTasks;
Then the dashboard should look better I hope.
-
@adukes40 yes one machine all snapins would be best.
-
@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
-
@adukes40 Can you change the < 4 to =3?
-
@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.
-
@adukes40 So back to this client updating thing - I want you to try something.
Remote into an affected computer. Sync the time on that computer with an NTP server - so it’s as accurate as it can be. Enable client updating on the server, and on the host, open services and restart the FOGService. See if it updates or not. If it’s a failure with the same error, go ahead and turn off client updating on the server again - and post the log from that host please so we can see if there was anything different.
-
@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.
-
@adukes40 Ok then, we can put it off till later. But - it may be fair to say that with the latest client you may not have snapin issues.
-
@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.