snapin hash does not match on storage node (1.5.7.55)


  • Testers

    I installed a new storage node with Centos 8, disabled the firewall and Selinux.
    I then copied the snapins from the old storage node to the new storage node because it’s on the same subnet and would be faster than letting the snapins replicate.
    I then installed fog as a storage node. everything looks and acts as it should. I then Imaged a PC using the storage node and it imaged correctly and joined the domain, the snapins however will not install because of a snapin hash mismatch.
    I then deleted all of the snapins in the /opt/fog/snapins folder on the storage node and let it replicate. I am still getting a hash mismatch error in the logs.

    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     11/26/2019 4:14 PM Client-Info Client Version: 0.11.16
     11/26/2019 4:14 PM Client-Info Client OS:      Windows
     11/26/2019 4:14 PM Client-Info Server Version: 1.5.7.55
     11/26/2019 4:14 PM Middleware::Response Success
     11/26/2019 4:14 PM SnapinClient Running snapin 01 - MTS-TeamViewer
     11/26/2019 4:14 PM Middleware::Communication Download: http://10.13.40.39//fog/service/snapins.file.php?mac=44:85:00:3E:01:52|44:85:00:3E:01:53|46:85:00:3E:01:52|00:23:24:AA:FA:05|44:85:00:3E:01:56&taskid=9461
     11/26/2019 4:14 PM SnapinClient C:\Program Files (x86)\FOG\tmp\TeamViewer-AllSites.sfx.exe
     11/26/2019 4:14 PM SnapinClient ERROR: Hash does not match
     11/26/2019 4:14 PM SnapinClient ERROR: --> Ideal: 8DE8056083825BD98A731EDE61073F59F8D472B957E20E4BCBCE103ABD05C9D722D37C26C633C2E831E9628FB4FDECA998E719FFD9B16DD0F3C4DD63DF2AB0AF
     11/26/2019 4:14 PM SnapinClient ERROR: --> Actual: 4629994E3A40C689A4F178F68E37A944EC8202717F20555CB8C0E1E6A31F11E2258CDD27EA3450F53D0BE1B9461D04C437637C58C1599A71EFEA2B20AF1D8A13
     11/26/2019 4:14 PM Middleware::Communication URL: http://10fogserver/fog/service/snapins.checkin.php?taskid=9461&exitcode=-1&mac=44:85:00:3E:01:52|44:85:00:3E:01:53|46:85:00:3E:01:52|00:23:24:AA:FA:05|44:85:00:3E:01:56&newService&json
    ------------------------------------------------------------------------------
    

  • Testers

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

    alt text

    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!


  • Testers

    @Sebastian-Roth
    the contents of the file read:

    "A valid database connection could not be made"
    

  • Developer

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


  • Testers

    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 "-" "-"```

  • Testers

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

    ![alt text](a9baab26-c6b7-4a25-b67b-fad3dfda9121-image.png image url)


  • Testers

    @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

    alt text


  • Testers

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


  • Developer

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


  • Testers

    @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


  • Testers

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



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


  • Testers

    @EduardoTSeoane It is replicated. I even deleted it and waited for it to replicate again.


  • Testers

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

    Get-FileHash C:\Program Files (x86)\FOG\tmp\TeamViewer-AllSites.sfx.exe

    fogsnapinhash.log
    [11-26-19 4:43:20 pm]  * Trying Snapin hash for: 01 - MTS-TeamViewer, ID: 129
    [11-26-19 4:43:20 pm]  * Getting snapin hash and size for: 01 - MTS-TeamViewer.
    [11-26-19 4:43:20 pm]  | Hash: 8de8056083825bd98a731ede61073f59f8d472b957e20e4bcbce103abd05c9d722d37c26c633c2e831e9628fb4fdeca998e719ffd9b16dd0f3c4dd63df2ab0af
    
    [root@10fogserver ~]# sha512sum /opt/fog/snapins/TeamViewer-AllSites.sfx.exe
    8de8056083825bd98a731ede61073f59f8d472b957e20e4bcbce103abd05c9d722d37c26c633c2e831e9628fb4fdeca998e719ffd9b16dd0f3c4dd63df2ab0af  /opt/fog/snapins/TeamViewer-AllSites.sfx.exe
    [root@10fogserver ~]#
    
    [root@13Storage ~]# sha512sum /opt/fog/snapins/TeamViewer-AllSites.sfx.exe
    8de8056083825bd98a731ede61073f59f8d472b957e20e4bcbce103abd05c9d722d37c26c633c2e831e9628fb4fdeca998e719ffd9b16dd0f3c4dd63df2ab0af  /opt/fog/snapins/TeamViewer-AllSites.sfx.exe
    [root@13Storage ~]#
    

    alt text



  • Try to verify than the snapin is replicated on the StorageNode.

    I have that problem on my 1.5.6 and my solution was the snapin replication.


  • Developer

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

    Let’s start by looking at the hashes. Run sha512sum /opt/fog/snapins/TeamViewer-AllSites.sfx.exe on your main FOG server, the old storage node and the new storage node. Do they all match?

    Then try the same on your Windows machine by running CertUtil -hashfile C:\Program Files (x86)\FOG\tmp\TeamViewer-AllSites.sfx.exe SHA512 (certutil.exe is supposed to be installed on Windows systems) - or install Powershell v4 and run Get-FileHash C:\Program Files (x86)\FOG\tmp\TeamViewer-AllSites.sfx.exe -Algorithm SHA512 | Format-List (https://docs.microsoft.com/en-us/powershell/module/Microsoft.PowerShell.Utility/Get-FileHash?view=powershell-5.1)


  • Moderator

    You probably just need to move the ssl certificate from the old fog server to the new fog server. It is in /opt/fog/snapins/ssl directory I believe.

    Edit: I would hold off on that after looking at the error message again. I’m not sure which hash its having a problem with. The crc hash it created when the snapin is uploaded or the communication hash between the fog client and the fog server.


Log in to reply
 

461
Online

6.4k
Users

13.8k
Topics

130.0k
Posts