@san_t_o  Can you please check few things: 1). Please verify what is the value set for "" property in the NodeManager option? (If it starts even for few seconds) # ps -ef | grep NodeManager Things to look for: 2). If above does not start due to the "" error then please check the permissions set for this directory: Example: # ls -ld /var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir drwxrwxrwt. 8 hdfs hadoop 4096 Feb 25 07:23 /var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir # ls -ld /var/lib/ambari-agent/tmp/ drwxrwxrwt. 12 ambari hadoop 4096 Mar 4 01:48 /var/lib/ambari-agent/tmp/ Why we wanted to check permissions on "/var/lib/ambari-agent/tmp/" and "/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir" directory because the "" is usually set to this directory so the yarn user should have proper read/write access on the directory listed here. Example: # grep 'JAVA_LIBRARY_PATH' /etc/hadoop/conf/yarn-env.sh export JAVA_LIBRARY_PATH="${JAVA_LIBRARY_PATH}:/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir" 3). Also please check if you see any "" related files here. Ideally those should be owned by "yarn" user like "yarn:hadoop" (hadoop is group). This directory and it's content should be writable be yarn user. Example: # ls -lart /var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir/libleveldbjni* -rwxr-xr-x. 1 yarn hadoop 752803 Dec 2 06:33 /var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir/libleveldbjni-64-1-2529926063314066012.8     Possible Cause: So if by mistake if you would have ever restarted YARN NodeManager /RM with "root" user then the permissions on those directories/files might have changed and it might not be writable by Yarn user. So please check the directory permissions if they are writable or not?   ... View more

@mike_bronson7  Looks like you have asked a very similar query on the other thread : https://community.cloudera.com/t5/Support-Questions/amari-rest-API-how-to-stop-service-on-specific-host/m-p/290651 ... View more

@mike_bronson7  I think the only change you will need to make is the "KAFKA" service in Uppercase because "kafka" in lowercase will not exist as a service. Following is the example which i tested in my cluster and it works pretty fine. # export service=kafka (INCORRECT) # export service=KAFKA # curl -iLv -u "admin:admin" -i -H 'X-Requested-By: ambari' -X PUT -d '{"RequestInfo":{"context":"_PARSE_.STOP.$service","operation_level":{"level":"SERVICE","cluster_name":"$CLUSTER_NAME","service_name":"$service"}},"Body":{"ServiceInfo":{"state":"INSTALLED"}}}' http://$HOST:8080/api/v1/clusters/$CLUSTER_NAME/services/$service   In order to start KAFKA service. # curl -iLv -u "admin:admin" -i -H 'X-Requested-By: ambari' -X PUT -d '{"RequestInfo":{"context":"_PARSE_.START.$service","operation_level":{"level":"SERVICE","cluster_name":"$CLUSTER_NAME","service_name":"$service"}},"Body":{"ServiceInfo":{"state":"STARTED"}}}' http://$HOST:8080/api/v1/clusters/$CLUSTER_NAME/services/$service   .   ... View more

@Prabhu_Muppala  As we see that the netstat command shows no oracle port 1521 opened.     (no output means Oracle is not running on default listerer port  1521. [cloudera@quickstart ~]$ sudo netstat -tnlpa | grep 1521 . Also the following error indicates that your Oracle Database is not successfully running on "localhost:1521" Caused by: oracle.net.ns.NetException: The Network Adapter could not establish the connection at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:470) So please verify why the oracle DB is not running and configured to use 1521 listener port? Please try to restart Oracle and then recheck if the port 1521 is opened? Or if you have configured to run Oracle on some other port? # netstat -tnlpa | grep $ORACLE_PROCESS_ID   .   ... View more