Private key failed

[Tom Elliott]

@Raymond-Bell No, you’re not.

THe indicator?

Your client version is on 0.9.11. It’s about about a week or so that 0.9.12 has been out.

[Raymond Bell]

@Tom-Elliott so i need to upload the new client to all 900 computers?

[Tom Elliott]

@Raymond-Bell You shouldn’t need to do anything because the client’s auto update.

[Raymond Bell]

@Tom-Elliott said:

@Raymond-Bell You shouldn’t need to do anything because the client’s auto update.

Ok i will just sit back and give it time and see what happens
Thanks

[Tom Elliott]

Does the /opt/fog/snapins/ssl/.srvprivate.key exist on the 10.24.28.18 server?

[Raymond Bell]

@Tom-Elliott said:

Does the /opt/fog/snapins/ssl/.srvprivate.key exist on the 10.24.28.18 server?

Yes sir

[Raymond Bell]

@Tom-Elliott Client is updated on all computers
This was on a test computer i just had put a image on and the image has the old 9.11
Did not give it time to update

MY MISTAKE!!!

[Tom Elliott]

@Raymond-Bell So you’re good to go now?

[Raymond Bell]

@Tom-Elliott said:

@Raymond-Bell So you’re good to go now?

Just re-imaged going to let it sit and update the client and see what happens. but i checked random computers i imaged from last week with same image and they are doing fine. So i am guessing i did not give it time to update after i imaged it. Going to check it and make sure after lunch. Will let you know…

[Raymond Bell]

@Tom-Elliott
It still has not up to 9.12
How long does it take? it has been about 1 1/2 hour
Is there a way to force this update to a client

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/28/2016 10:23 PM Client-Info Version: 0.9.11
 3/28/2016 10:23 PM Middleware::Communication URL: http://10.24.28.18/fog/management/other/ssl/srvpublic.crt
 3/28/2016 10:23 PM Data::RSA FOG Server CA cert found
 3/28/2016 10:23 PM Middleware::Authentication Cert OK
 3/28/2016 10:23 PM Middleware::Communication POST URL: http://10.24.28.18/fog/management/index.php?sub=authorize
 3/28/2016 10:23 PM Middleware::Communication Unknown Response: Private key not found
 3/28/2016 10:23 PM Service Sleeping for 120 seconds

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/28/2016 10:25 PM Client-Info Version: 0.9.11
 3/28/2016 10:25 PM Middleware::Communication URL: http://10.24.28.18/fog/management/other/ssl/srvpublic.crt
 3/28/2016 10:25 PM Data::RSA FOG Server CA cert found
 3/28/2016 10:25 PM Middleware::Authentication Cert OK
 3/28/2016 10:25 PM Middleware::Communication POST URL: http://10.24.28.18/fog/management/index.php?sub=authorize
 3/28/2016 10:26 PM Middleware::Communication Unknown Response: Private key not found
 3/28/2016 10:26 PM Service Sleeping for 120 seconds```

[Joe Schmitt]

@Raymond-Bell said:

How long does it take

The client will only update if it can authenticate. You have to get the private key not found error fixed before the client will function. If this error was not present, the client would auto update within a minute.

[Raymond Bell]

@Jbob
Thats what i was thinking so it has to be something with the new trunk

[Joe Schmitt]

@Raymond-Bell for the record I too had this issue but upgrading to the latest revision in trunk fixed it.

[Raymond Bell]

@Jbob Updating now to r5136 and will see what happens

[Raymond Bell]

@Tom-Elliott @Jbob Update trunk to r5136 and still getting same error

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/29/2016 7:45 AM Client-Info Version: 0.9.11
 3/29/2016 7:45 AM Middleware::Communication URL: http://10.24.28.18/fog/management/other/ssl/srvpublic.crt
 3/29/2016 7:45 AM Data::RSA FOG Server CA cert found
 3/29/2016 7:45 AM Middleware::Authentication Cert OK
 3/29/2016 7:45 AM Middleware::Communication POST URL: http://10.24.28.18/fog/management/index.php?sub=authorize
 3/29/2016 7:47 AM Bus Became bus server
 3/29/2016 7:47 AM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 3/29/2016 7:47 AM Bus Emmiting message on channel: Status

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/29/2016 7:47 AM Client-Info Version: 0.9.11
 3/29/2016 7:47 AM Middleware::Communication URL: http://10.24.28.18/fog/management/other/ssl/srvpublic.crt
 3/29/2016 7:47 AM Data::RSA FOG Server CA cert found
 3/29/2016 7:47 AM Middleware::Authentication Cert OK
 3/29/2016 7:47 AM Middleware::Communication POST URL: http://10.24.28.18/fog/management/index.php?sub=authorize
 3/29/2016 7:48 AM Middleware::Communication Unknown Response: Private key not found
 3/29/2016 7:48 AM Service Sleeping for 120 seconds

And the key is there

fog@fog-virtual-machine14:/opt/fog/snapins/ssl$ ls
CA  fog.csr
fog@fog-virtual-machine14:/opt/fog/snapins/ssl$ ls .?*
.srvprivate.key

..:
ssl
fog@fog-virtual-machine14:/opt/fog/snapins/ssl$

[Wayne Workman]

@Raymond-Bell These are the files you should have. Check the permissions too.

[Raymond Bell]

@Wayne-Workman

[Wayne Workman]

@Raymond-Bell Have you tried resetting the encryption on this particular host? It’s done in the web UI under the host’s general area.

[Raymond Bell]

@Wayne-Workman
Yes, But i had to add it to a group by its self first to get the Reset Option

[Wayne Workman]

@Raymond-Bell There is a manual method for resetting the encryption on all hosts here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client

This method would also work on an individual host but you’d need to modify the SQL appropriately with a WHERE clause.