Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
on 10-03-2018 09:39 AM
What should I do if my EUM Server is unable to start because of below error?
Error Starting EUM Processor Server
| com.google.inject.CreationException: Unable to create injector, see the following errors:
Error in custom provider, com.singularity.ee.util.security.credentialstore. exception. CryptoOperationFailureExceptio n: Failed to decrypt: Illegal key size or default parameters
Error in custom provider, com.singularity.ee.util.security.credentialstore.exception.CryptoOperationFailureException:
Failed to decrypt: Input length must be multiple of 16 when decrypting with padded cipher.....
eum.properties
are incorrect. In order to fix this, edit your eum.properties
file with the properties below and restart your EUM serveronprem. useEncryptedCredentials=true
to false --> onprem. useEncryptedCredentials=false
onprem.dbPassword=<<plaintext passowrd>>
onprem.credentialKey=<<plaintext passowrd>>
<eum_server_home>/ eum-processor/bin/liquidbase. properties
for the password
property. eum.properties
file and restart the EUM Server. The database password may not be decipherable using the key in use. You can follow the steps below to complete this for this process:bin/eum-credential-key.sh generate_ks -storepass <store_password>
bin/eum-credential-key.sh obfuscate -plaintext <store_password>
bin/eum-credential-key.sh encrypt -storepass <store_password> -plaintext <DB_password>
eum.properties
file as:onprem.dbPassword=<<output of 3 above>>
onprem.credentialKey=<<output of 2 above>>
onprem.useEncryptedCredentials=true
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form