Posts made by benjamind

@Sebastian-Roth

It seems to be better :

root@fog-dev:~# openssl x509 -noout -modulus -in /var/www/fog/management/other/ssl/srvpublic.crt | openssl md5
(stdin)= 240adcef143c7ba2a2b4551282f476f9
root@fog-dev:~# openssl rsa -noout -modulus -in /opt/fog/snapins/ssl/.srvprivate.key | openssl md5
(stdin)= 240adcef143c7ba2a2b4551282f476f9

I have started a new deployment i’ll keep you update.

Thank you.

@Sebastian-Roth

root@fog-dev:~# openssl x509 -noout -modulus -in /var/www/fog/management/other/ssl/srvpublic.crt | openssl md5
(stdin)= 6bf7b33e8a206b266560c17350102ffa
root@fog-dev:~# openssl rsa -noout -modulus -in /opt/fog/snapins/ssl/.srvprivate.key | openssl md5
(stdin)= 240adcef143c7ba2a2b4551282f476f9

@Sebastian-Roth We have the same error message on other clients. Here is the fog.log fog.log of an other client.

Here is the pcap file.

Thnak you for your help.

Hi @Sebastian-Roth,

Is the result of the command indicative ?

@Sebastian-Roth

MariaDB [fog]> SELECT hostID,hostName,hostSecToken FROM hosts WHERE hostName LIKE ‘%PC2409M%’;

+------------+-------------------+-------------------------+
| hostID     | hostName          | hostSecToken            |
+------------+-------------------+-------------------------+
| 61         | PC2409M           |                         |
+------------+-------------------+-------------------------+

@Sebastian-Roth What do you want to verify precisely on the database ?

@Sebastian-Roth Here is is the commands i used to update our server :
cd /root/fogproject/
git pull
cd bin/
./installfog.sh

@Sebastian-Roth Sorry, i give you the return on the commands form an other FOG server. Here is the return form the concerned server :

root@fog-dev:~# openssl x509 -dates -noout -in /var/www/fog/management/other/ssl/srvpublic.crt
notBefore=Mar 14 07:16:32 2019 GMT
notAfter=Mar 11 07:16:32 2029 GMT
root@fog-dev:~# openssl x509 -dates -noout -in /var/www/fog/management/other/ca.cert.pem
notBefore=Apr 5 13:49:36 2018 GMT
notAfter=Apr 2 13:49:36 2028 GMT

The srvprublic.crt date corresponds to our last FOG update from 1.5.0 to 1.5.5 and the ca.cert.pem should corresponds to the first installation of the server.

Is it a normal behaviour ?

@Sebastian-Roth I have restarted the FOG service.

root@fog:~# openssl x509 -dates -noout -in /var/www/fog/management/other/ssl/srvpublic.crt
notBefore=Sep  3 09:07:28 2018 GMT
notAfter=Aug 31 09:07:28 2028 GMT
root@fog:~# openssl x509 -dates -noout -in /var/www/fog/management/other/ca.cert.pem
notBefore=Nov 24 09:57:37 2016 GMT
notAfter=Nov 22 09:57:37 2026 GMT

@Sebastian-Roth Here is the fog.log starting from when i renamed the token.dat.

@Sebastian-Roth Thanks for your return.

What error are you talking about exactly?

All our machines can’t join the domain automatically after a deployment by Fog. Do you talk about a specific error message from the fog.log ?

I’m doing a deployment again now and I’ll check if I have the file when it will be finished. I’ll keep you update.

Hi,

Does anyone , please, got an idea to solve my problem ?

Thanks.

@Sebastian-Roth I have edited the image to erase the MAC address but it is configured.

@Sebastian-Roth I can’t find the “Reset encryption data” button :

Hi @Sebastian-Roth,

Thank you for yous answer. Sorry, i have forgotten the attachment : fog.log

Hi everybody,

I’m using fog to deploy images n many PCs and it works fine.

However, i got a problem with the automatic domain join functionality.

I attach the log of my last try to this post.

Thank you for your help.