CLM 4.0.1 upgrade - SSLPeerUnverifiedException happening in logs
Hello, I am setting up a staging environment for my CLM 4.0.1 upgrade (upgrading from 3.0.1.4). Following the IBM upgrade steps, I'm now at the point where I upgrade my licenses. They upgraded fine, but now when I look at my jts.log, I receive errors.
"The license keys contributed by Applications could not be discovered. Some licenses contributed by installed Appllications might not be available."
......
"caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated"
I tried upgrading RRC, but it failed. Now when I try, it says that I already failed to upgrade it once, please consult the documentation.
Can anyone make sense of that SSLPeerUnverifiedException I'm getting?
"The license keys contributed by Applications could not be discovered. Some licenses contributed by installed Appllications might not be available."
......
"caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated"
I tried upgrading RRC, but it failed. Now when I try, it says that I already failed to upgrade it once, please consult the documentation.
Can anyone make sense of that SSLPeerUnverifiedException I'm getting?
Accepted answer
Are you using proxy? Could you check to see if any error in the proxy server log?
Other than the error in jts.log, do you see any problem when trying to access any of the CLM applications?
Other than the error in jts.log, do you see any problem when trying to access any of the CLM applications?
Comments
We are using a reverse proxy with IHS. What log file contains proxy logs?
Also, I will install the admin application tomorrow and will then update on my findings and I there are continuing problems.
Thanks a million
http_plugin.log in IHS_install_dir/logs
We had the same error during our last upgrade and we found the error entry in the http_plugin.log pointing to the wrong location of cert files.
I took a look at http_plugin.log, and I see some errors for sure. Specifically,
ERROR: lib_security: logSSLError: str_security (gsk error 408): GSK_ERROR_BAD_KEYFILE_PASSWORD
ERROR: lib_security: initializeSecurity: Failed to initialize GSK environment
...
..
...
Any thoughts?
Hi Chris,
This indicates that the password of the key database may have expired or that the stashfile which stores the password is not accessible anymore.
There is a technote that describes the situation and a way to fix it:
Let me know if this helps!
-Christian
Technical Support Engineer
IBM Rational Client Support Europe
Comments
Kevin Ramer
Apr 11 '13, 9:54 a.m.Also make sure the SSL method "matches"
See:
https://jazz.net/forum/questions/96722/why-are-data-warehouse-jobs-failing-with-peer-not-authenticated