@ivten,   The error you are getting is regarding "kadmin" which is an MIT Kerberos client command for the MIT KDC. However, you mention "cloudera-scm user can access the AD and recreate kerberos principals."   If you are using Active Directory for a KDC, that means that you seem to have a misconfiguration where your Kerberos KDC is set to "MIT"   In Cloudera Manager, go to "Administration --> Settings" and click "Kerberos" on the left under the CATEGORY section. On the right, make sure you have "KDC Type" set to "Active Directory" if you are using Active Directory for your KDC. Save your change and try importing credentials and generating missing credentials.     ... View more

@Abhiravilla,   The log you show does not indicate any problems that would prevent parcel distribution.   The following exception only indicates that the agent could not connect to the Host Monitor (which is expected if it is not running): [04/Oct/2017 20:57:20 +0000] 5147 MonitorDaemon-Reporter throttling_logger ERROR    (10 skipped) Error sending messages to firehose: mgmt-HOSTMONITOR-58d97c64d44220f47b91dc6ed632f373 Traceback (most recent call last):   File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.1-py2.7.egg/cmf/monitor/firehose.py", line 116, in _send     self._port)   File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/avro-1.6.3-py2.7.egg/avro/ipc.py", line 469, in __init__     self.conn.connect()   File "/usr/lib/python2.7/httplib.py", line 836, in connect     self.timeout, self.source_address)   File "/usr/lib/python2.7/socket.py", line 575, in create_connection     raise err error: [Errno 111] Connection refused   How do you know there are heartbeat problems? Also:   - what is your server_host value in /etc/cloudera-scm-agent/config.ini - what is the output of "hostname -f"     ... View more

@ebeb,   Good news finding the space issue!   It sounds as if your browser session has gotten into a bad state. At this stage, I'd recommend starting over with the new cluster wizard.  You can log out of Cloudera Manager and come back in.  That should present you with the first page of the Add New Cluster Wizard. If not, you can log out, restart Cloudera Manager, and then try again.   If it still fails on the one host, check the agent log on that host and paste information that is relevant.   Ben  ... View more

@ebeb,   Based on the agent log, it appears that agent showed a successful download of the parcel file: Finished download [ url: http://ip-172-31-42-243.us-east-2.compute.internal:7180/cmf/parcel/download/CDH-5.12.1-1.cdh5.12.1.p..., state: exception, total_bytes: 1741165383, downloaded_bytes: 1741165383, start_time: 2017-10-04 15:07:23, download_end_time: 2017-10-04 15:07:23, end_time: 2017-10-04 15:07:23, code   However, even on the fastest of machines, I would expect download of "1741165383" bytes to take longer than under 1 second.  So I am suspicious something didn't go right.   Further more, when an attempt is made by the agent to unpack the parcel, the parcel file does not exist:   Src file /opt/cloudera/parcels/.flood/CDH-5.12.1-1.cdh5.12.1.p0.3-xenial.parcel/CDH-5.12.1-1.cdh5.12.1.p0.3-xenial.parcel does not exist, path: /opt/cloudera/parcels/.flood/CDH-5.12.1-1.cdh5.12.1.p0.3-xenial.parcel/CDH-5.12.1-1.cdh5.12.1.p0.3-xenial.parcel       Recommendation:   Verify that the file exists.  As a root / sudo user:   ls -l /opt/cloudera/parcels/.flood/CDH-5.12.1-1.cdh5.12.1.p0.3-xenial.parcel/CDH-5.12.1-1.cdh5.12.1.p0.3-xenial.parcel   If it does not exist, that indicates a problem being able to write to the .flood directory. I suspect permissions may be at play.  Check to make sure that the /opt/cloudera/parcels directory is owned by the Cloudera Manager user (typically cloudera-scm)   Let us know what you find.   ... View more

@snm1523,   Cloudera recommends the following:   https://www.cloudera.com/documentation/enterprise/latest/topics/cdh_admin_performance.html#cdh_performance__section_xpq_sdf_jq   Essentially, we don't want swapping to occur. ... View more

@Abhiravilla,   As long the localhost can be resolved, you should be able to search for and find your host. If you choose that host in the add new cluster wizard, you can select to install all services on that one host. If you are having trouble, try posting a couple screen shots to help explain the problem.   -Ben ... View more

@Telematics,     In Cloudera Manager, edit Proxy User Configuration  What did you enter in the field? It should look like this, for example: joe=alice,bob;hue=*;admin=*   See the Description of Proxy User Configuration in Cloudera Manager (click the question mark next to the property)   -Ben ... View more

Hi @VFTR,   Since the issue you are having is that the services cannot access the truststore specified that the Management Service roles use to trust the signer of Cloudera Manager's certificate, Make sure you are changing the right password.   Cloudera Manager --> Clusters --> Cloudera Management Service --> Configuration Search for Cloudera Manager Server TLS/SSL Certificate Trust Store Password   If you can't figure out the password, it is also OK to leave the password field blank.  If the password is specified, it is required to be correct, but the services don't need to know the password to get what they need from the file.   Click the blue arrow next to Cloudera Manager Server TLS/SSL Certificate Trust Store Password to revert to the default 'null' value.  Save and restart the Management Service.   -Ben ... View more