RC10 Broken Items on upgrade

[Wayne Workman]

@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.

[Wayne Workman]

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

[Wayne Workman]

@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.

[Tom Elliott]

@Wayne-Workman no it’s not. Client updating is not a fog tasking.

[adukes40]

@Wayne-Workman The snapins I am trying to use exist at all locations.

[adukes40]

@Wayne-Workman running Date give me:

Fri Sep 16 07:44:34 EDT 2016

which is MAYBE 1-2 seconds off from my machine.

[Tom Elliott]

@adukes40 the wget command, can you run that on all your nodes and try again?

[adukes40]

@Tom-Elliott Still just sit in Queued, and Snapin hash still remains blank. also running at the master site and a node site.

[Tom Elliott]

@adukes40 are you semi familiar with git?

[adukes40]

@Tom-Elliott not really, but Wayne gave me some instructions way back in the thread.

But I will do what ever is needed.

[Tom Elliott]

@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.

[adukes40]

@Tom-Elliott OK, all sites are updated, FOG GUI is showing

Also see this, not sure if concerning or not:

[Tom Elliott]

@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?

[adukes40]

@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.

[Tom Elliott]

@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.

[Tom Elliott]

@adukes40 yes one machine all snapins would be best.

[adukes40]

@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: 0

mysql> 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

[Tom Elliott]

@adukes40 Can you change the < 4 to =3?

[adukes40]

@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: 0

Still same.

[Wayne Workman]

@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.