Cloudera Manager Agent Fails to Start on an Edge Node with "SSLError: bad decrypt" After Setting Up a CA Signed Certificate
(Doc ID 2505429.1)
Last updated on JULY 20, 2024
Applies to:
Big Data Appliance Integrated Software - Version 4.5.0 and laterLinux x86-64
Symptoms
After setting up a Certificate Authority (CA) signed certificate on a non-BDA edge which is part of a cluster the Cloudera Manager agent on the edge node fails to start.
The associated: /var/log/cloudera-scm-agent/cloudera-scm-agent.log shows a traceback like:
...
File "/usr/lib64/cmf/agent/build/env/lib/python2.6/site-packages/M2Crypto-0.21.1-py2.6-linux-x86_64.egg/M2Crypto/SSL/Context.py", line 101, in load_cert_chain m2.ssl_ctx_use_privkey(self.ctx, keyfile)
SSLError: bad decrypt
File "/usr/lib64/cmf/agent/build/env/lib/python2.6/site-packages/M2Crypto-0.21.1-py2.6-linux-x86_64.egg/M2Crypto/SSL/Context.py", line 101, in load_cert_chain m2.ssl_ctx_use_privkey(self.ctx, keyfile)
SSLError: bad decrypt
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |