Snapin Hash does not exist


  • Testers

    I just migrated to a new FOG server and am having issues with snapins. It could be something I missed but I can’t seem to figure out what I missed.

    I am running Ubuntu 14.04 fully updated
    FOG Trunk 7945, which is up to data as of this writing
    Win 7 with 0.10.6 client

    I used the .fogsettings from my old server (which was also on 7945)to install FOG. I moved my /opt folder and my /images to the new server.

    The client will image and join to AD, user tracker seems to work also. When it goes to run snapins I get the following log

    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     5/31/2016 4:44 PM Client-Info Client Version: 0.10.6
     5/31/2016 4:44 PM Client-Info Client OS:      Windows
     5/31/2016 4:44 PM Client-Info Server Version: 7945
     5/31/2016 4:44 PM Middleware::Response Success
     5/31/2016 4:44 PM SnapinClient Snapin Found:
     5/31/2016 4:44 PM SnapinClient     ID: -1
     5/31/2016 4:44 PM SnapinClient     RunWith: 
     5/31/2016 4:44 PM SnapinClient     RunWithArgs: 
     5/31/2016 4:44 PM SnapinClient     Name: 
     5/31/2016 4:44 PM SnapinClient     File: 
     5/31/2016 4:44 PM SnapinClient     Created: -1
     5/31/2016 4:44 PM SnapinClient     Args: 
     5/31/2016 4:44 PM SnapinClient     Action: 
     5/31/2016 4:44 PM SnapinClient ERROR: Snapin hash does not exist
    ------------------------------------------------------------------------------
    

    When I check 10.1.90.2/fog/status/getsnapinhash.php?filepath=/opt/fog/snapins/win7rollup.msu
    it returns:
    cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e|0

    So it appears that it can find the file and hash it, but doesn’t find the hash where ever the client is looking for it.

    I find it odd that the ID is reporting -1 in the log.

    Anyone have any suggestions?


  • Testers

    So after all kinds of testing and complete confusion I finally figured out what was causing the issue with this. But not sure what happened to cause it. It was caused by my increasing the max size for snapins. I had a snapin the was approx 500mb so I changed the php settings in the old server to accept 3000m (3gb) and it seemed to work. But when I went to the new server and changed the settings to allow for it, it wouldn’t work. When I deleted that snapin completely from the server, everything started to work. Still not sure why when I would delete the snapin tasks from the host and deployed any other snapin it didn’t work. But everything seems to be running smoothly now that I don’t have any large snapins. I think I am going to go back to using scripts for large snapin tasks.


  • Testers

    I was too focused on the small problem that I missed the big issue there.
    When I am troubleshooting an issue, if a new problem comes up it can be easy to over look the obvious issue at first, not sure why the PC time was so far off.


  • Testers

    @Tom-Elliott Sorry, yes I just caught that too. I fixed the time on the machine and now it no longer gives the validity error. But it still is giving the original error from OP.


  • Senior Developer

    @ITSolutions validity period is almost always related to time on the client machine. Either it is ahead or behind and is not matching within the certificates expiry time.


  • Testers

    So I am still trying to figure this out and have new things happening.

    First I have found it looks like this is only occurring on new deployments or new installations on systems that don’t have the FOG client already.
    It appears that all of the machines that have been previously imaged and/or previously had the FOG client appear to be working.

    I tried to remove the FOG client completely from a freshly imaged machine and re-install and get the following error

    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     5/24/2016 4:28 PM Client-Info Version: 0.10.6
     5/24/2016 4:28 PM Client-Info OS:      Windows
     5/24/2016 4:28 PM Middleware::Authentication Waiting for authentication timeout to pass
     5/24/2016 4:30 PM Middleware::Communication Download: http://10.1.90.2/fog/management/other/ssl/srvpublic.crt
     5/24/2016 4:30 PM Data::RSA FOG Server CA cert found
     5/24/2016 4:30 PM Data::RSA ERROR: Certificate validation failed
     5/24/2016 4:30 PM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (NotTimeValid)
     5/24/2016 4:30 PM Middleware::Authentication ERROR: Could not authenticate
     5/24/2016 4:30 PM Middleware::Authentication ERROR: Certificate is not from FOG CA
    
    
     5/24/2016 4:30 PM Bus Registering ParseBus in channel Power
     5/24/2016 4:30 PM Middleware::Communication URL: http://10.1.90.2/fog/management/index.php?sub=requestClientInfo&mac=34:64:A9:30:E2:F2||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
     5/24/2016 4:30 PM Middleware::Authentication Waiting for authentication timeout to pass
     5/24/2016 4:32 PM Middleware::Communication Download: http://10.1.90.2/fog/management/other/ssl/srvpublic.crt
     5/24/2016 4:32 PM Data::RSA FOG Server CA cert found
     5/24/2016 4:32 PM Data::RSA ERROR: Certificate validation failed
     5/24/2016 4:32 PM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (NotTimeValid)
     5/24/2016 4:32 PM Middleware::Authentication ERROR: Could not authenticate
     5/24/2016 4:32 PM Middleware::Authentication ERROR: Certificate is not from FOG CA
     5/24/2016 4:32 PM Middleware::Response Success
     5/24/2016 4:32 PM Middleware::Communication URL: http://10.1.90.2/fog/service/getversion.php?clientver&newService&json
     5/24/2016 4:32 PM Middleware::Communication URL: http://10.1.90.2/fog/service/getversion.php?newService&json
    
     5/24/2016 4:32 PM Service Creating user agent cache
     5/24/2016 4:32 PM Middleware::Response ERROR: Unable to get subsection
     5/24/2016 4:32 PM Middleware::Response ERROR: Object reference not set to an instance of an object.
     5/24/2016 4:32 PM Middleware::Response ERROR: Unable to get subsection
     5/24/2016 4:32 PM Middleware::Response ERROR: Object reference not set to an instance of an object.
    

    This is on 2 different images, multiple machines and one computer that hasn’t been imaged since I have been here and so it is a completely different setup and model.

    But it appears that all of the machines running the FOG client before the rebuild are communicating with the server just fine. I had a scheduled snapin that runs every Thursday that deployed to all of those machines just fine.

    I am attaching the FOG.log file from one of the misbehaving machines to hopefully shed some light on what is happening.

    0_1464983650439_fog.log


  • Senior Developer

    This is not an issue with the client. I have tested snapins on r7961 with 0.10.6 and all worked perfectly. It sounds like something in your database is off. @Tom-Elliott.

    As for v0.9.12 not working, anything before 0.10.0 is incompatible with the latest revisions (except legacy client which is still compatible).

    I have also confirmed that “Disable auto updating” functions properly on v0.10.6.


  • Testers

    OK so I did some more testing and found a few issues.

    First is that it appears the 0.10.x line of the client seems to ignore the update client settings. Even with the client updater globally disabled it will update to the latest. Not sure if @Developers are aware of this. So I cannot test an older version of the client as it just auto updates to 0.10.6

    Second is that I modified the DB so that one of my snapins had an ID of -1 just for testing. When I tried deploying to the client it thinks there is something to do in the HostnameChanger module. Once I logged out to let it complete the “Host name task” it cleared the snapin task from the que, but does not run the snapin, and everything reports fine.

    I tried the 0.9.12 client as it won’t update, as I have the update feature disabled, and it gives the following error for all modules.

    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     6/1/2016 4:54 PM Client-Info Version: 0.9.12
     6/1/2016 4:54 PM SnapinClient Running...
     6/1/2016 4:54 PM Middleware::Communication URL: http://10.1.90.2/fog/service/servicemodule-active.php?moduleid=snapinclient&mac=F4:B7:E2:1D:29:3D|B8:CA:3A:C9:5E:9A||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
     6/1/2016 4:54 PM Middleware::Communication Unknown Response: Not Allowed Here
    ------------------------------------------------------------------------------
    

  • Testers

    Another update, I tried creating a new snapin on the new FOG server and deploying it to the client, I still get the same error.
    I have also reset the encryption data on the client.
    I have uninstalled and re-installed the client also.

    I am truly at a loss on this one.


  • Testers

    I just checked the DB and the the snapin ID’s for the snapins deploying to the client are correct. Another add thing is that if I have multiple snapins in the que it will show that the client has checked in for all of them.

    There are quite a few errors in the apache log, so I am posting it if it might help.
    0_1464802312693_error.log


  • Testers

    @Tom-Elliott There is no -1 in the database. This happens for all snapins, no matter what is pushed tot he client. I can do a full image, push all snapins, or just one it always gives the same in the log.

    I just updated to the latest this morning 7961 and still having the same issue.

    Not sure if moving servers may have caused this, this is the first time I have moved servers with the Trunk and the new client. But I am pretty certain I moved everything correctly.


  • Senior Developer

    Can you check the database for snapins associated with FOG? I’m willing to guess that -1 might actually exist as a snapin in your system.


Log in to reply
 

473
Online

39.4k
Users

11.1k
Topics

105.3k
Posts

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