I corrected this in the parcels page in admin tab.My local repository has all parcels and my internal remote repo has also correct parcels.All permissions are correct.I do not see any errors in the cloudera-scm-server.log.Cloudera-scm-server.out is empty.   Here is the last line from the logs;   2014-03-20 17:35:12,930 INFO [NodeConfiguratorThread-0-2:node.NodeConfiguratorProgress@477] xx.yy.01.net: New state is a backward state. Storing failed state 2014-03-20 17:35:12,931 INFO [NodeConfiguratorThread-0-2:node.NodeConfiguratorProgress@512] xx.yy.02.net: Transitioning from PACKAGE_INSTALL jdk (PT30.011S) to WAITING_FOR_ROLLBACK 2014-03-20 17:35:13,992 INFO [NodeConfiguratorThread-0-3:node.NodeConfiguratorProgress@477] xx.yy.02.net: New state is a backward state. Storing failed state 2014-03-20 17:35:13,993 INFO [NodeConfiguratorThread-0-3:node.NodeConfiguratorProgress@512] xx.yy.zz.net: Transitioning from PACKAGE_INSTALL jdk (PT31.013S) to WAITING_FOR_ROLLBACK 2014-03-20 17:35:14,021 INFO [NodeConfiguratorThread-0-1:node.NodeConfiguratorProgress@477] xx.yy.zz.net: New state is a backward state. Storing failed state 2014-03-20 17:35:14,021 INFO [NodeConfiguratorThread-0-1:node.NodeConfiguratorProgress@512] xx.yy.04.net: Transitioning from PACKAGE_INSTALL jdk (PT31.009S) to WAITING_FOR_ROLLBACK 2014-03-20 17:35:14,031 INFO [NodeConfiguratorThread-0-4:node.NodeConfiguratorProgress@477] xx.yy.05.net: New state is a backward state. Storing failed state 2014-03-20 17:35:14,032 INFO [NodeConfiguratorThread-0-4:node.NodeConfiguratorProgress@512] xx.yy.zz.net: Transitioning from PACKAGE_INSTALL jdk (PT31.009S) to WAITING_FOR_ROLLBACK 2014-03-20 17:35:14,036 INFO [NodeConfiguratorThread-0-0:node.NodeConfiguratorProgress@477] xx.yy.zz.net: New state is a backward state. Storing failed state 2014-03-20 17:35:14,036 INFO [NodeConfiguratorThread-0-0:node.NodeConfiguratorProgress@512] xx.yy.zz.net: Transitioning from PACKAGE_INSTALL jdk (PT31.010S) to WAITING_FOR_ROLLBACK 2014-03-20 17:35:55,720 INFO [Parcel Update Service:parcel.ParcelUpdateService@59] Updating parcel state based on local filesystem state and remote repos 2014-03-20 17:35:55,725 INFO [Parcel Update Service:components.LocalParcelManagerImpl@105] Found files CDH-4.6.0-1.cdh4.6.0.p0.26-el6.parcel,SOLR-1.2.0-1.cdh4.5.0.p0.4-el6.parcel under /opt/cloudera/parcel-repo   ... View more

I found an exceptiion and I think I know the problem. I have entered an invalid url  in the add parecel repository section.How can i overwrite this.I tried adding the correct location but it is not getting reflected.Is there some fiel which I can modify.   Error while attempting to retrieve repository info for repo kkl java.net.MalformedURLException: no protocol: kkl/ at java.net.URL.<init>(URL.java:585) at java.net.URL.<init>(URL.java:482) at java.net.URL.<init>(URL.java:431) at com.cloudera.parcel.components.ParcelDownloaderImpl.urljoin(ParcelDownloaderImpl.java:390) at com.cloudera.parcel.components.ParcelDownloaderImpl.getRepositoryInfoFuture(ParcelDownloaderImpl.java:443) at com.cloudera.parcel.components.ParcelDownloaderImpl.getRepositoryInfo(ParcelDownloaderImpl.java:404) at com.cloudera.parcel.components.ParcelDownloaderImpl.syncRemoteRepos(ParcelDownloaderImpl.java:303) at com.cloudera.parcel.components.ParcelManagerImpl.syncRemoteRepo(ParcelManagerImpl.java:585) at com.cloudera.parcel.components.ParcelManagerImpl.access$300(ParcelManagerImpl.java:62) at com.cloudera.parcel.components.ParcelManagerImpl$3.run(ParcelManagerImpl.java:596) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) ... View more

In other words is it the same yum repository for cloudera manager that I  have configured/ ... View more

The db.properties had an old tns name.I changed that to the correct one and it works now.Thank you Clint and Darren. ... View more

Hi Darren, Here is the info from the files. I do not see any errors in cloudera-scm-server.log.It does not have any information of my attempt to start .All that log has is the earlier installation details(2 days back). The .out file could not find a log4j.properties.This is the only entry in .out file :ERROR Could not read configuration file from URL [file:/etc/cloudera-scm-server/log4j.properties]. java.io.FileNotFoundException: /etc/cloudera-scm-server/log4j.properties (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:146) at java.io.FileInputStream.<init>(FileInputStream.java:101) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:524) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:483) at org.apache.log4j.LogManager.<clinit>(LogManager.java:127) at org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:73) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:242) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) at com.cloudera.server.cmf.Main.<clinit>(Main.java:134) log4j:ERROR Ignoring configuration file [file:/etc/cloudera-scm-server/log4j.properties]. log4j:WARN No appenders could be found for logger (org.springframework.context.support.ClassPathXmlApplicationContext). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. ... View more

The db.properties file has the correct oracle db information and teh database preparation step went well. Yes .There is no error in those files.In fact the latest records in those files are from two days ago when I  successfully did an installation. ... View more