RC10 Broken Items on upgrade
-
And the hash for that is blank?
-
-
@adukes40 All nodes are on the same level and running?
-
And assigned all of them like you said
-
@Tom-Elliott All nodes are running RC-10 and powered on. and Enabled. The services should still be stopped from before.
-
Mind running:
wget -O /var/www/fog/lib/client/snapinclient.class.php https://raw.githubusercontent.com/FOGProject/fogproject/working-RC-11/packages/web/lib/client/snapinclient.class.php
Then redeploy a snapin again?
-
@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 -
@adukes40 said in RC10 Broken Items on upgrade:
(also weird it says created today at 7:29, this script has been made since May/June, unless this is by design)
pretty sure that refers to the task’s creation date/time. Like when it was deployed.
-
@adukes40 I notice in your screenshots you’re using the location plugin. Newer FOG RC enforces location settings for snapins if the location stuff is setup. If the snapin doesn’t exist at the location server assigned to the host, it will say snapin doesn’t exist and file not found and other similar stuff.
-
I think this is why the client updating is broke:
https://forums.fogproject.org/topic/8586/scheduling-snapins-always-says-date-is-in-the-past -
@adukes40 Run this command on your server and let us know what it says:
date
and also provide the exact date and time there when you run it too.Pay attention to the day of the month in the output. If it’s off, correct it. Then re-run the fog installer, and again check the
date
command and see what it says. If it’s set inaccurately - we can disable this line of code in the installer so your manual corrections work.This may help you on the journey:
http://www.cyberciti.biz/faq/howto-install-ntp-to-synchronize-server-clock/If we can get this correct for the installer, you won’t need to manually push out the client as you were asking in chat - the fog server would be able to do it.
-
@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: