snapin hash does not match on storage node (1.5.7.55)

[Greg Plamondon]

@EduardoTSeoane I can execute the file manually and it installs fine. The file size is a match.

[Greg Plamondon]

@Sebastian-Roth said in snapin hash does not match on storage node (1.5.7.55):

@Greg-Plamondon When did you upload/update that snapin last? Possibly the FOGSnapinHash service just didn’t update the hash sum in the database yet.

Are alll your nodes using the same FOG version?

the nodes that are working are on Version: 1.5.7.4

[Sebastian Roth]

@Greg-Plamondon This is a really strange issue. We see the hashes match perfectly fine on the nodes and replication log. But the file being transfered to the Windows client has a different checksum.

Can you please try this: Use WinSCP to copy the file from one of the storage nodes to your Windows client and run Get-FileHash ... again.

As well, can you please use the mentioned CertUtil too?

[Greg Plamondon]

@Greg-Plamondon said in snapin hash does not match on storage node (1.5.7.55):

@Sebastian-Roth said in snapin hash does not match on storage node (1.5.7.55):

@Greg-Plamondon When did you upload/update that snapin last? Possibly the FOGSnapinHash service just didn’t update the hash sum in the database yet.

Are alll your nodes using the same FOG version?

the nodes that are working are on Version: 1.5.7.4

Sorry I was wrong on the storage nodes that were not upgraded to 1.5.7.5 working correctly. They all seem to be having the same issue.

If I set the location of the host to the Fogserver instead of the storage node it works as it should. But this is not acceptable as the files are being pulled across the wan.

[Greg Plamondon]

@Sebastian-Roth said in snapin hash does not match on storage node (1.5.7.55):

Get-FileHash

I did as you asked and used Winscp to download the file from the storage node and ran Get-FileHash and CertUtil

[Greg Plamondon]

@EduardoTSeoane said in snapin hash does not match on storage node (1.5.7.55):

@Greg-Plamondon
Have you try to execute the file manually?
Have you compared the size?
Maybe the download is not correct.

After doing some more investigating I found that the file sizes are indeed not the same. I was getting the information 2nd hand. I checked the "C:\Program Files(x86)\FOG\tmp folder for the snapin and it is only 1kb in size.

Sorry for the confusion.


[Greg Plamondon]

Here is the access_log:

10.13.100.144 - - [02/Dec/2019:16:38:13 -0500] "GET /fog/management/other/ssl/srvpublic.crt HTTP/1.1" 200 1749 "-" "-"
10.13.100.144 - - [02/Dec/2019:16:38:13 -0500] "POST /fog/management/index.php?sub=requestClientInfo&authorize&newService HTTP/1.1" 200 326 "-" "-"
10.13.100.144 - - [02/Dec/2019:16:38:14 -0500] "GET /fog/management/index.php?sub=requestClientInfo&configure&newService&json HTTP/1.1" 200 322 "-" "-"
10.13.100.144 - - [02/Dec/2019:16:38:14 -0500] "GET /fog/management/index.php?sub=requestClientInfo&mac=00:0C:29:62:EB:A0&newService&json HTTP/1.1" 200 10697 "-" "-"
10.13.100.144 - - [02/Dec/2019:16:38:14 -0500] "GET /fog/service/getversion.php?clientver&newService&json HTTP/1.1" 200 7 "-" "-"
10.13.100.144 - - [02/Dec/2019:16:38:15 -0500] "GET /fog/service/getversion.php?newService&json HTTP/1.1" 200 8 "-" "-"
10.13.100.144 - - [02/Dec/2019:16:38:16 -0500] "GET /fog/service/snapins.checkin.php?taskid=9546&exitcode=-1&mac=00:0C:29:62:EB:A0&newService&json HTTP/1.1" 200 73 "-" "-"
10.13.100.144 - - [02/Dec/2019:16:38:16 -0500] "GET /fog/service/usertracking.report.php?action=login&user=13WIN10-IT%5Cgp1001&mac=00:0C:29:62:EB:A0&newService&json HTTP/1.1" 200 105 "-" "-"```

[Sebastian Roth]

@Greg-Plamondon said in snapin hash does not match on storage node (1.5.7.55):

After doing some more investigating I found that the file sizes are indeed not the same. I was getting the information 2nd hand. I checked the "C:\Program Files(x86)\FOG\tmp folder for the snapin and it is only 1kb in size.

Please see if you can open that file (e.g. using Notepad++ or some other good editor) to see what the file looks like. Possibly this might give us a clue what’s going on here.

[Greg Plamondon]

@Sebastian-Roth
the contents of the file read:

"A valid database connection could not be made"

[Greg Plamondon]

I noticed that the fog version after the upgrade was not showing:

After I manually changed the fogstorage password in MySQL the versions started populating for the storage nodes that were upgraded but not for the storage nodes that were not upgraded.
is it possible that the upgrade corrupted the fogstorage MySQL password in the database on upgade or was it the mysql dump that was generated by Configuration Save> Export Database in the fog gui?

The more I think about it it would have to be the MySQL dump… I installed fog on a new Centos 8 build and imported the database after installing fog.

snapins are now downloading with the correct file sizes.

Thank you everyone for helping me with this issue!