Certificate is not from FOG CA
Seeing this in the logs meant that you are probably using a different CA certificate on your FOG server. Is this correct? Did you manually install certificates?
Being a member of FOG Hangouts will allow you to stay updated about the latest FOG Hangout; the when, the where, and the details. Membership in this group is automatic membership in a mailing list.
@sourcaffeine You’re not at all having the same issue.
The old client isn’t really supported any more. Please understand that the messages you’re seeing in the fog.log file are totally different and give an overall picture.
Basically, the messages are saying the CA you’re using are not the CA that was generated for the FOG Server.
You can retry this with:
./installfog.sh --recreateCA -y
I can’t be sure what spawned the issue to begin with though. It also means after you recreate the CA certificates, you will need to reinstall the client to get the client to repin the updated CA chain information.
@processor Please post the contents of the text files
d1.minimum.partitions from that image.
still saying a 500GB hd is too small whereas there is only 80GB of data
Maybe I have missed that in the earlier discussion. Has it always been this exact error?? Can you please post a picture of that error on screen??
@pdit Maybe our link detection is failing on this particular NIC. But I kind of doubt this as we simply use standard Linux tools and information from the kernel to figure this out. Really sounds like a spanning tree issue. Different NICs might behave in different ways here.