Hash does not match



  • Server
    • Version: rc10
    • OS: ubuntu
    Client
    • Version: 11.5
    • OS: win7
    Description

    After upgrading to the latest svn i seem to be getting a hash error when trying to deploy snapins, this is using location plugin and setting host to use another group other than the one with the main server in. If i drop the storage nodes back to the group which includes the main server and leave host group blank all works ok.

    Checking the hash in the browser returns the correct hash
    b6d43eb287c067f12f8cccea9fbb90987f2feb58f5c9add196670875025ef7fe44aa180c1c385738617960e7df3856b1f301b55b9590dfad5cb7d2f823c98783|210944

    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     20/09/2016 14:29 Client-Info Client Version: 0.11.5
     20/09/2016 14:29 Client-Info Client OS:      Windows
     20/09/2016 14:29 Client-Info Server Version: 1.3.0-RC-10
     20/09/2016 14:29 Middleware::Response Success
     20/09/2016 14:29 SnapinClient Snapin Found:
     20/09/2016 14:29 SnapinClient     ID: 5985
     20/09/2016 14:29 SnapinClient     Name: 2 Default Snapins
     20/09/2016 14:29 SnapinClient     Created: 2016-09-20 14:32:21
     20/09/2016 14:29 SnapinClient     Action: 
     20/09/2016 14:29 SnapinClient     Pack: False
     20/09/2016 14:29 SnapinClient     Hide: False
     20/09/2016 14:29 SnapinClient     Server: 
     20/09/2016 14:29 SnapinClient     TimeOut: 0
     20/09/2016 14:29 SnapinClient     RunWith: 
     20/09/2016 14:29 SnapinClient     RunWithArgs: 
     20/09/2016 14:29 SnapinClient     Args: 
     20/09/2016 14:29 SnapinClient     File: DefaultSnapinsGO2.exe
     20/09/2016 14:29 Middleware::Communication Download: http://135.100.5.9/fog/service/snapins.file.php?mac=E4:A4:71:1F:1D:1E|E4:A4:71:1F:1D:22|28:F1:0E:15:32:50||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=5985
     20/09/2016 14:29 SnapinClient C:\Program Files (x86)\FOG\tmp\DefaultSnapinsGO2.exe
     20/09/2016 14:29 SnapinClient ERROR: Hash does not match
     20/09/2016 14:29 SnapinClient ERROR: --> Ideal: B6D43EB287C067F12F8CCCEA9FBB90987F2FEB58F5C9ADD196670875025EF7FE44AA180C1C385738617960E7DF3856B1F301B55B9590DFAD5CB7D2F823C98783
     20/09/2016 14:29 SnapinClient ERROR: --> Actual: 9BD839F86499FBE4EA10EDE44BDBB1EC80EE2FD8256EB1FB782031A0C8BE1FED198C5B482C16CFD7B60A0C0E9E17DC68535E7DFF1AE7CCD4968F536F5B1F3BD3
     20/09/2016 14:29 Middleware::Communication URL: http://135.100.5.9/fog/service/snapins.checkin.php?taskid=5985&exitcode=-1&mac=E4:A4:71:1F:1D:1E|E4:A4:71:1F:1D:22|28:F1:0E:15:32:50||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
    ------------------------------------------------------------------------------```


  • @Tom-Elliott Ok thanks look forward to it your doing lots of great work.


  • Senior Developer

    @adukes40 no they cannot, buy RC 11 will at least be more informative of this.



  • @theWizard I am uncertain of that, that would be a Wayne/Tom question. Sorry :(



  • @adukes40
    Ah ok that kinda sucks i guess there is no timeframe for rc11 either ? Can the snapins and images replicate to a group that does not contain a master node ?



  • @theWizard Now it says doesn’t exist, which is a known issue in RC-10. Tom has fixed this in RC-11. Not sure how he wants you to handle this from here though. He bumped me up to a dev version to see if it fixed the issue, but I don’t think he wants everyone doing that. I will leave this up to him.



  • I double checked snapins are replicated all up to date but still get a message now hash does not exist.

    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     20/09/2016 16:18 Client-Info Client Version: 0.11.5
     20/09/2016 16:18 Client-Info Client OS:      Windows
     20/09/2016 16:18 Client-Info Server Version: 1.3.0-RC-10
     20/09/2016 16:18 Middleware::Response Success
     20/09/2016 16:18 SnapinClient Snapin Found:
     20/09/2016 16:18 SnapinClient     ID: 5989
     20/09/2016 16:18 SnapinClient     Name: 2 Default Snapins
     20/09/2016 16:18 SnapinClient     Created: 2016-09-20 15:59:59
     20/09/2016 16:18 SnapinClient     Action: 
     20/09/2016 16:18 SnapinClient     Pack: False
     20/09/2016 16:18 SnapinClient     Hide: False
     20/09/2016 16:18 SnapinClient     Server: 
     20/09/2016 16:18 SnapinClient     TimeOut: 0
     20/09/2016 16:18 SnapinClient     RunWith: 
     20/09/2016 16:18 SnapinClient     RunWithArgs: 
     20/09/2016 16:18 SnapinClient     Args: 
     20/09/2016 16:18 SnapinClient     File: DefaultSnapinsGO2.exe
     20/09/2016 16:18 SnapinClient ERROR: Snapin hash does not exist```


  • @Tom-Elliott O I recall :p This one where the values don’t match, I saw just the other day, and it was because the snapin on the master was slightly different than the one on the remote node. Once I placed the same copy on the remote node, it didn’t complain about the hashes not matching


  • Senior Developer

    @adukes40 mind you replication and hash issues are known about for rc-10 and more or less fixed for rc-11.



  • Snapin was the same until i had this problem then i removed and re uploaded the snapin to rule the old one out but still had the same issue, i will check on the remote nodes though and see if they are up to date.



  • @theWizard Did you recently update this snapin and re upload it to the master? It sounds like you made a change to the snapin (the uploaded file) which changed the hash on the master side. I assume you are trying to run this snapin at a remote node which still has the old hash value. Seems like the new version just hasn’t replicated out to the remote node yet.


Log in to reply
 

351
Online

39.3k
Users

11.0k
Topics

104.4k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.