Closed samkos closed 11 years ago
It seems that the certificate loaded in the SSL trust store on TMS (set through sslCa=logiciels/vishnu/.vishnu/3.1/ca-3.1.pem) doesn't match the certificate loaded on the server (set through the key serverSslCertificate).
Could you check that and tell us ?
Yes I've just checked and they match. it cause no problem at all when BGQ's TMS tries to connect with the exact same certificate
What about permissions on the file /logiciels/vishnu/.vishnu/3.1/ca-3.1.pem ? Does the user running TMS can access it?
Permission is OK, the user can access and read the file without any problem
weird problem, since all work fine on BGQ. I was trying to take a look at the problem on the machine, but I have a message indicating that the machine has been put offline for maintenance duties.
OK thanks, keep me posted!
Fixed by Kevin
Hi
since a week or so, vishnu encounters problems of connection for the TMS daemon running on the front node of ivanoe.
Here are the traces I got
[INFO] Expecting ciphered database
Would you have any hints on what goes wrong?
SK