cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
The AppDynamics Community is Migrating this Friday, February 28th.


At 6pm PST, the AppDynamics Community will go into read-only mode and after migration is complete, you will be redirected to community.splunk.com.
Read more here


Anonymous
Not applicable

Symptoms

The following error message can be found in the SSL-enabled debug logs for the EUM processor, while the processor is running and listening on port 7002:

 

javax.net.ssl.SSLHandshakeException: no cipher suites in common

 

The following error message appears on the <eum-server-host>:<eum-server-https-port>/eumaggregator/get-version page.

 

 

 

EUM_SSL.JPG

Diagnosis

This root cause of this issue is a wrong entry type field value in the custom keystore for the EUM processor alias.

 

Example:

Alias name: 'eum-processor'
Creation date: 14 Mar, 2017
Entry type: trustedCertEntry

 

Solution

  1. Regenerate the keystore and copy into <eum installation directory>\eum-processor\bin 
  2. Make sure that the entry type value is not trustedCertEntry for the alias 'eum-processor' and it should be as "Entry type: PrivateKeyEntry".
  3. Restart the EUM Server. In your computer terminal, from the EUM processor directory use the following commands:
    1. bin/eum.sh stop
      bin/eum.sh start
  4. Verify the new SSL server cert works by opening the following page in a browser: https://<hostname>:7002/eumcollector/get-version
  5. Confirm a successful response.

 

Related Links:

Version history
Last update:
‎09-05-2018 04:03 PM
Updated by:
Ask the Experts Session: Hybrid Application Monitoring Deployment

Join us on Feb 26 to explore Splunk AppDynamics deployment strategies, SaaS models, agent rollout plans, and expert best practices.


Register Now

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here
Contributors