Snapin Hash
-
I recently migrated my fog installation to a new server and I am getting allot of snapin hash doesn’t match.
Is there a way to get the hash to match through the shell? Currently, I have been just re-importing them one by one through the GUI.Thanks!
-
@greg-plamondon If you blank that column in the database, the snapin hash service thingy (very technical, I know) will fill them back in with correct ones. Do you know the sql to empty a column?
-
@wayne-workman
Thanks I will truncate the snapins.sHash table.UPDATE snapins SET sHash=NULL;
-
How long should this take? I see a few hashes in the database but there are allot that is still null.
-
@greg-plamondon I would think in most people’s cases it should happen in minutes or less. How big are your snapins? How many snapins do you have? Any apache error logs related to this? How about the snapin hash log in
/opt/fog/log
? -
There is a service called “FOGSnapinHash” that does these checks.
Maybe check the logs for this?
The time it takes to get the hash varies quite terribly on the the size of the file to be hashed. For example a 1.5 GB file will take a very long time to get the hash compared to a file the size of 1KB.
-
==> fogsnapinhash.log <== [03-15-18 4:48:28 pm] * Trying Snapin hash for: Synergize Client v13.1, ID: 116 [03-15-18 4:48:28 pm] * Getting snapin hash and size for: Synergize Client v13.1. [03-15-18 4:48:28 pm] | Hash: 46ddfd39e74b31fc97f78ce17c6208a5619884e2b75d2c10a53ab5ae842a1fb634230126de53cf11d1305dab04fdcca95c5b50886d453c2fc5f33c46740feb26 [03-15-18 4:48:28 pm] * Trying Snapin hash for: Synergize Indexing v13.1, ID: 115 [03-15-18 4:48:28 pm] * Getting snapin hash and size for: Synergize Indexing v13.1. [03-15-18 4:48:29 pm] | Hash: 1749c4c8bd5dc664796a0c56305ee2204a26bbc1166e7c263ec51a8f02b70f4a253803f4af141d2da5d4462b3aa599ff88d062fa3313aadf06ae58255b5b0c4f [03-15-18 4:48:29 pm] * Trying Snapin hash for: UAG Components, ID: 56 [03-15-18 4:48:29 pm] * Getting snapin hash and size for: UAG Components. [03-15-18 4:48:29 pm] | Hash: d78f69a8ebe78a44e338fb53c6bb287577e24895ded8d233559c74c3c5b063af1cae5fdb2e8637053a4e201da87e16347fa735e11d258788351956b7d9c6db83 [03-15-18 4:48:29 pm] * Completed. [root@10fogserver fog]#
It says completed but there are allot more snapins that need hashes.
I did notice that when setting the primary storage group for a snapin it doesn’t stay checked.
Also when adding or making changes to snapin groups it doesn’t refresh the screen. you have to do it manually by pressing F5 or the browser refresh button. -
@greg-plamondon said in Snapin Hash:
I did notice that when setting the primary storage group for a snapin it doesn’t stay checked.
How many storage groups do you have? I’ve noticed this too but on a system with only one storage group.
-
@wayne-workman
I only have 2 storage groups.
I looked this morning and the snapin hash was still empty on the majority of the snapins.
the one thing I did notice is that the permissions were set to fog:apache on the snapins without hashes and when I upload a snapin through the web interface the permissions are fog:fog. -
@greg-plamondon said in Snapin Hash:
the one thing I did notice is that the permissions were set to fog:apache on the snapins without hashes and when I upload a snapin through the web interface the permissions are fog:fog.
Can you correlate which ones have what permissions, and if they have a hash or not?
-
I figured it out!
I took a look at the snapinGroupAssoc table and notice that there were some very odd numbers in the sgaStorageID column varying from 1, 4 and even 22.
I then ran this query to empty the entire snapinGroupAssoc table:SET FOREIGN_KEY_CHECKS = 0; TRUNCATE snapinGroupAssoc;
I then clicked on the “List All Snapins” from the web interface and the snapinGroupAssoc table was repopulated with the Default storage ID for all Snapins, from there I went to each Snapin and assigned the second storage group and the checkmark for primary works!
the snapin hash service wasn’t working for the majority of my snapins because the storage group didn’t match any of my actual storage ID’s in the database.
-
You can mark this as solved.