The minimum disk space limit for each of Host Monitor and Service Monitor is 10 Gb. If you are at this size or below, a cleanup does not make much sense as the disk space will be re-acquired over time.   The correct solution is to make sufficient disk space available for the /var/lib mountpoint.   If there is no other option then a short term help is to    stop the Service Monitor role instance empty the data directory /var/lib/cloudera-service-monitor/ start the Service Monitor role instance Similar for the Host Monitor. Be aware this means all historical data showing up in the charts in CM will be lost with this method. Only monitoring data gathered after this procedure will be showing up. ... View more

Can you kinit using this principal and then run hdfs commands like "hdfs dfs -l /"? Does this work? ... View more

The upgrade wizard will block the upgrade if the number of nodes that will be in the CDH 6 cluster exceeds 100. You may want to reach out to your Cloudera sales representative to clarify the status and implications for your clusters upfront. ... View more

To review the state please   Get the affected directory path from CM > Configuration > Scope: YARN (MR2 included) > NodeManager Log Directory. The default is /var/log/hadoop-yarn Verify the available disk space for this path: # df -h /var/log/hadoop-yarn Look up what are the biggest disk space consumers on this mount point Clean up where possible   If no clean up is possible and there is sufficient disk space available then you can in decrease the alarm threshold in the CM > YARN > Configuration > Scope: Node Manager > Category: Monitoring > Log Directory Free Space Monitoring Percentage Thresholds configuration property. ... View more

The kerberos ticket is valid but the DN complains about Wrong principal in request Please review your application configuration or proxy software for correct kerberos principal configured. As you upgraded your proxy server host, may it be that some settings changed like hostname or krb5.conf?   Another possibility is that there is a mismatch of encryption types, see this KB article ... View more

Happy to hear the issue is resolved! Just for completeness, did you delete /var/lib/cloudera-scm-agent/cm_guid on the cluster nodes? ... View more

Instructions for changing hostnames are provided in the Changing Hostnames documentation chapter. For CM server the hostname change should be trivial and working fine afterwards.   Is your CM TLS enabled? Do you get any error message when connecting to the CM web UI?   The CM server logs as asked by @manuroman will reveal if there is an issue. ... View more

Frequent pauses in the JVM by the Garbage Collector indicate the heap memory settings are too low.   Please increase the CM -> Cloudera Management Service -> Configuration -> Scope: Service Monitor -> Category: Resource Management -> Java Heap Size of Service Monitor in Bytes and Java Heap Size of Service Monitor in Bytes configuration property values accordingly.   The Service Monitor Requirements documentation chapter has guidance for the values to choose. ... View more

Please make the verifier.pem file contain only the root CA certificate. Then list contents with  # openssl x509 -text -in /opt/cloudera/security/pki/verifier.pem And repeat the connection test with this exact command # openssl s_client -connect cmhost.antuit.internal:7182 -CAfile /opt/cloudera/security/pki/verifier.pem ... View more