Hi Tom,
We have added a column to the ‘location’ table in the fog database and we have given this column an ENUM ‘http’, ‘https’. The error message disappeared.
Should anyone run into the same problem, you can at least remove the error message from your logs.
We still have image-task problems but we’ll deal with those now.
Thanks.
Regards, sassonie
This problem is solved after reinstalling new keys.
Running ‘installfog.sh -K’ solved my problem.
Now all images can be used again and no matter what client is installed they all work fine.
Hi averyone,
I’ve been running fog_1.5.10 for a few weeks now, and this version is finally starting to satisfy a bit.
The new server was created using https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
The server is now doing fine but when joining our AD domain, it goes wrong.
As long as a client-mcahine uses client 0.11.16 there is no problem but once the client machine is updated to client 0.13.0 it goes wrong and message appears:
19-9-2023 09:27:15 Client-Info Version: 0.13.0
19-9-2023 09:27:15 Client-Info OS: Windows
19-9-2023 09:27:15 Middleware::Authentication Waiting for authentication timeout to pass
19-9-2023 09:27:15 Middleware::Communication Download: http://fogserver/fog/management/other/ssl/srvpublic.crt
19-9-2023 09:27:16 Data::RSA ERROR: Certificate validation failed
19-9-2023 09:27:16 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: Cannot verify the certificate signature. (NotSignatureValid)
19-9-2023 09:27:16 Middleware::Authentication ERROR: Could not authenticate
19-9-2023 09:27:16 Middleware::Authentication ERROR: Certificate is not from FOG CA
It could be that I should move/copy another certificate but there is nothing about that in the migrate_fog manual.
Could you tell me what I should do to get everything working with client 0.13.0?