can provide the output for following command $ stat /usr/java/jdk1.8.0_72/bin/java  ... View more

Hello,    The process is actually documented here http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ag_restore_server.html   What database is Cloudera Manager server is connected to?   michalis ... View more

Hi Romulus,   OS level dependencies causing the conflict, since you have Red Hat Enterprise Linux Server you should file a ticket with RHEL to troubleshoot the issue. At first glance it looks like your IUS repo is causing the conflict.   Hope this helps. ... View more

Is your cluster managed by Cloudera Manager server, or are you managing the Hadoop configurations using an editor? ... View more

Yes you can stop service and it's individual roles via CM API [1]    > Is there a specific table it stores relevant data for us to query and check?  Service status can be check directly from the CM API querying the relevant endpoint, specifically for the service you'd need to GET (open your browser) to the service endpoint [2] which will give you its state [3]     As a start point you could see the example [4a][4b]   [1] https://github.com/cloudera/cm_api/wiki/Start-Stop-Restart-JobTracker-Role [2] https://cloudera.github.io/cm_api/apidocs/v11/path__clusters_-clusterName-_services_-serviceName-.html#GET [3] https://cloudera.github.io/cm_api/apidocs/v11/ns0_apiServiceState.html [4a] https://github.com/cloudera/cm_api/tree/master/python/examples [4b] https://github.com/gdgt/cmapi ... View more

Can you summarise your end goal, so I can provide you with an appropriate information. ... View more

So far we confirmed that nothing is actually running on the nodes and attempting a simple workaround has not given you a positive outcome.    Let's do it the hard way 😉     per your description   1 host(s) have stale Kerberos client configuration but will not be updated because there is a process running. Consider stopping roles on these hosts to ensure that they are updated by this command:   can you check in your CM database under the _roles_ table and list all the _configured_status - we could set it to STOPPED and see if you can proceed withe deploying Kerberos client-config   ie: login to your cloudera manager database and execute the below SQL query; select name, configured_status from roles;   can you paste the output so I can check which role is RUNNING     ... View more

Can you attempt the following workaround;   Stop the cluster: Cloudera Manager > Cluster > Stop Stop Cloudera Management Service: Cloudera Manager > Management Service > Stop Deploy Kerberos Client Configuration: Cloudera Manager > Cluster > Deploy Kerberos Client Configuration Start Cloudera Management Service: Cloudera Manager > Management Service > Start Start the cluster: Cloudera Manager > Cluster > Start   let me know if this helps ... View more

> 1 host(s) have stale Kerberos client configuration but will not be updated because there is a process running. In the CM UI> Hosts> click (affected host)> click [Processes] tab to see what processes are running on that host. Alternative, on the affected host terminal. Check [1] the child CDH role/processes that supervisord is controlling;   Stop the relevant role/process from Cloudera Manager   Let me know if this helps, [1]  option 1. [bash]# for process in $(pgrep -P $(ps aux | grep [s]upervisord | awk '{print $2}')); do ps -p $process -o euser,pid,command | awk 'NR>1'; done option 2. ps auxwf   ... View more