Communication ERROR: operation timed out, could not authenticate, obj error
-
@kverkiss can you update and try again?
-
@Tom-Elliott Different errors this time:
21-4-2016 17:04 Client-Info Version: 0.9.12 21-4-2016 17:04 Middleware::Communication URL: http://10.10.2.250/fog/management/other/ssl/srvpublic.crt 21-4-2016 17:04 Data::RSA FOG Server CA cert found 21-4-2016 17:04 Data::RSA ERROR: Certificate validation failed 21-4-2016 17:04 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: Kan de handtekening van het certificaat niet controleren. (NotSignatureValid) 21-4-2016 17:04 Middleware::Authentication ERROR: Could not authenticate 21-4-2016 17:04 Middleware::Authentication ERROR: Certificate is not from FOG CA 21-4-2016 17:04 Service Sleeping for 120 seconds 21-4-2016 17:05 Bus Registering ParseBus in channel Power 21-4-2016 17:05 Bus Became bus client 21-4-2016 17:05 Bus Registering OnNotification in channel Notification 21-4-2016 17:05 Bus Registering OnUpdate in channel Update```
-
Found a rather nasty (unknown bug), can you update again?
-
@Tom-Elliott Rev 7252:
21-4-2016 17:13 Client-Info Version: 0.9.12 21-4-2016 17:13 Middleware::Communication URL: http://10.10.2.250/fog/management/other/ssl/srvpublic.crt 21-4-2016 17:13 Data::RSA FOG Server CA cert found 21-4-2016 17:13 Data::RSA ERROR: Certificate validation failed 21-4-2016 17:13 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: Kan de handtekening van het certificaat niet controleren. (NotSignatureValid) 21-4-2016 17:13 Middleware::Authentication ERROR: Could not authenticate 21-4-2016 17:13 Middleware::Authentication ERROR: Certificate is not from FOG CA 21-4-2016 17:13 Service Sleeping for 120 seconds 21-4-2016 17:14 Bus Registering ParseBus in channel Power 21-4-2016 17:14 Bus Became bus client 21-4-2016 17:14 Bus Registering OnNotification in channel Notification 21-4-2016 17:14 Bus Registering OnUpdate in channel Update
-
@kverkiss that means your ca changed. Fog doesn’t do that automatically. Do you have the original servers CA information somewhere?
-
@Tom-Elliott I could do a rollback to an older version. I did update the certificate because this server had an IP change.
-
@kverkiss updating keys would’ve been fine but from the looks of things it also recreated the ca information. Rolling back would not solve the problem unless you have a snapshot from before the ip changed or before you updated the ca information.
-
@Tom-Elliott Hi Tom,
I just did a rollback over VMware to our server backup from last night. It is working fine now. Now I have updated the the most recent revison and no errors show up. I am currently monitoring if the problem reappears. -
@kverkiss The
--recreate-keys
option for the installer re-configures the certificates to your new IP, but--recreate-CA
resets the identity. This will “block” all clients from communicating with the server. -
@Jbob Thanks for the information!
-
@kverkiss said in Communication ERROR: operation timed out, could not authenticate, obj error:
@Jbob Thanks for the information!
The problem has been resolved. Thanks for all help.